HP_DECnet-Plus_for_OpenVMS__________________________ Installation and Configuration Part Number: BA406-90007 June 2006 This book explains how to install and configure the HP DECnet-Plus for OpenVMS software (including X.25 for OpenVMS VAX and the optional OSI applications software component). It also explains how to install the HP X.25 for OpenVMS software on OpenVMS I64 and OpenVMS Alpha systems. Revision/Update Information: This manual supersedes DECnet-Plus for OpenVMS Installation and Configuration (BA406- 90001) Operating Systems: OpenVMS I64 Version 8.3 OpenVMS Alpha Version 8.3 Software Version: HP DECnet-Plus for OpenVMS Version 8.3 Hewlett-Packard Company Palo Alto, California © Copyright 2006 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Intel and Itanium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. UNIX is a registered trademark of The Open Group. Printed in the US _________________________________________________________________ Contents Preface................................................... xiii Part I Installing DECnet-Plus for OpenVMS 1 Preparing to Install DECnet-Plus for OpenVMS 1.1 Locating the Distribution Kit................. 1-1 1.2 Accessing the Online Release Notes............ 1-3 1.3 Time Required for Installation and Configuration................................. 1-4 1.4 Required Hardware............................. 1-4 1.5 Prerequisite Software......................... 1-4 1.5.1 Checking the Operating System Version..... 1-5 1.5.2 DECnet and OSI Applications over TCP/IP... 1-5 1.6 License Requirements.......................... 1-5 1.6.1 Checking Licenses......................... 1-6 1.7 System Requirements........................... 1-7 1.7.1 Disk Space................................ 1-7 1.7.2 Required Memory........................... 1-8 1.7.3 Required System Parameters................ 1-9 1.7.3.1 SYSGEN Parameters for OpenVMS Cluster Members................................. 1-12 1.7.4 Required Privileges and Rights Identifiers............................... 1-12 1.8 Backing Up the System Disk.................... 1-13 1.9 Notifying Users............................... 1-13 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 on an OpenVMS I64 or OpenVMS Alpha System................... 3-3 3.1.2 Installing DECnet-Plus on an OpenVMS VAX System.................................... 3-6 3.2 PCSI Process Account Quotas................... 3-8 3.3 Installing DECnet-Plus Using the POLYCENTER Software Installation Utility................. 3-9 3.3.1 DECnet-Plus for OpenVMS I64 Installation Dialog.................................... 3-9 3.3.2 DECnet-Plus for OpenVMS Alpha Installation Dialog.................................... 3-11 3.3.3 DECnet-Plus for OpenVMS VAX Installation Dialog.................................... 3-13 3.4 Rights Identifiers Added to the System........ 3-15 3.5 Files Installed on the System................. 3-16 3.6 Rebooting the System.......................... 3-17 Part II Configuring DECnet-Plus for OpenVMS 4 Configuration Options 4.1 Choosing an Initial Configuration Option...... 4-2 4.2 How to Run NET$CONFIGURE ..................... 4-5 4.2.1 Local and Global Symbols.................. 4-6 4.2.2 Running the Procedure from Different Processes................................. 4-6 iv 5 Using the FAST Configuration Option 5.1 Invoking the FAST Configuration Option........ 5-1 5.2 Modifying a Current DECnet-Plus System Configuration................................. 5-5 6 Using the BASIC and ADVANCED Configuration Options 6.1 Invoking the Configuration Procedure.......... 6-1 6.2 Opening Messages.............................. 6-2 6.3 Specifying Phase IV Conversion Options........ 6-4 6.4 Configuring Node and Session Control Information................................... 6-5 6.4.1 Specifying Directory Name Services........ 6-6 6.4.1.1 The Local Namespace .................... 6-6 6.4.1.2 The HP DECnet-Plus Distributed Name Service (DECdns)........................ 6-7 6.4.1.3 The Domain Name System.................. 6-7 6.4.1.4 The Name Service Search Path............ 6-7 6.4.2 Specifying Node Full Names................ 6-9 6.4.3 Specifying the Node Synonym............... 6-10 6.4.4 Specifying the Naming Cache Timeout Value..................................... 6-11 6.4.5 Specifying the Session Control Address Update Interval........................... 6-12 6.4.6 Specifying the Naming Cache Checkpoint Interval.................................. 6-12 6.5 Configuring Routing Parameters................ 6-13 6.5.1 Specifying the Node Type.................. 6-13 6.5.2 Specifying Router Information............. 6-14 6.5.2.1 Routing Type............................ 6-14 6.5.2.2 Maximum Path Splits..................... 6-14 6.5.2.3 Phase IV Maximum Address and Maximum Area.................................... 6-15 6.5.3 Specifying a DECnet Phase IV Address...... 6-16 6.5.4 Specifying a Phase IV Prefix.............. 6-16 6.5.5 Specifying End Node Information........... 6-17 6.5.5.1 Network Addresses....................... 6-17 6.5.5.2 DNA Address Format...................... 6-20 6.5.5.3 Segregated Mode Routing and Integrated Mode Routing............................ 6-20 6.5.6 Specifying the Default ES Hello Timer..... 6-22 6.5.7 Specifying the ES Cache Size.............. 6-22 6.6 Configuring Devices........................... 6-22 v 6.6.1 Configuring WANDD Device Support.......... 6-23 6.6.1.1 WANDD Device Configuration on OpenVMS I64 and OpenVMS Alpha Systems........... 6-23 6.6.1.2 WANDD Device Configuration on OpenVMS VAX Systems............................. 6-24 6.6.2 The Configuration Procedure Device Scan... 6-25 6.6.3 Configuring Asynchronous Data Link Support (OpenVMS VAX Only)........................ 6-26 6.6.3.1 Static Data Links....................... 6-27 6.6.3.2 Dynamic Data Links...................... 6-28 6.6.3.3 Preparing the Terminal Lines for DECnet Use..................................... 6-30 6.6.4 Configuring Data Links and Routing Circuits.................................. 6-31 6.6.4.1 FDDI Large Packet Support............... 6-32 6.6.4.2 Circuit Cost and Routing Priority....... 6-32 6.6.4.3 Enabling Phase IV Addressing on Routing Circuits................................ 6-33 6.6.5 Configuring DECnet over X.25.............. 6-34 6.7 Configuring Transports........................ 6-39 6.7.1 Specifying the Network Service Protocol (NSP) Transport Configuration............. 6-40 6.7.1.1 Flow Control Policy..................... 6-41 6.7.2 Specifying the OSI Transport Configuration............................. 6-42 6.7.2.1 Enabling OSI Applications over TCP/IP and DECnet over TCP/IP.................. 6-43 6.7.3 Specifying Transport Congestion Avoidance................................. 6-45 6.7.4 Configuring Slow-Speed NSP Transport Connections............................... 6-46 6.7.5 Specifying the OSI Loopback Test Application Account....................... 6-47 6.7.6 Configuring OSI Templates................. 6-47 6.7.6.1 Common Template Parameters.............. 6-48 6.7.6.2 CLNS Network Service Template Parameters.............................. 6-52 6.7.6.3 CONS Network Service Template Parameters.............................. 6-53 6.7.6.4 RFC 1006 Network Service Template Parameters.............................. 6-54 6.8 Configuring Time Zone Differential Factors.... 6-54 6.9 Configuring the Event Dispatcher.............. 6-55 vi 6.9.1 Configuring Event Sinks................... 6-56 6.9.2 Outbound Streams.......................... 6-58 6.9.3 Phase IV Relay............................ 6-61 6.10 Configuring the Application Database.......... 6-62 6.11 Configuring the MOP Client.................... 6-65 6.12 Configuring the Cluster Alias................. 6-66 6.13 Summary Display............................... 6-68 6.14 Generating the NCL Scripts.................... 6-69 6.15 Starting the Network.......................... 6-70 6.16 Namespace Modification........................ 6-71 6.17 Modifying a Current DECnet-Plus System Configuration................................. 6-73 7 Modifying a Current Configuration 7.1 Choosing a Configuration Option............... 7-1 7.2 Invoking the Configuration Procedure.......... 7-3 7.3 Opening Messages.............................. 7-4 7.4 The Main Options Menu......................... 7-6 7.5 Changing an Entire Configuration.............. 7-7 7.6 Changing the Node Name/Namespace Name......... 7-8 7.6.1 Common Namespace Selection Processing..... 7-10 7.6.2 Modifying Node Information on Satellite Systems................................... 7-11 7.6.3 Changing a Node to Use DECdns as the Primary Namespace......................... 7-11 7.6.4 Configuring a DECdns Clerk System to Use a WAN DECdns Server......................... 7-15 7.6.5 Converting a DECdns Clerk System to a DECdns Server System...................... 7-17 7.6.6 Converting a DECdns Server to a DECdns Clerk System.............................. 7-26 7.6.7 Reverting a DECdns Clerk System Back to a DECdns Server System...................... 7-28 7.6.8 Using the DECdns Namespace as Secondary on a DECdns Server System.................... 7-32 7.6.9 Configuring a DECdns Server System into an Existing Namespace........................ 7-36 7.6.9.1 Configuring a DECdns Server in a DNS Version 1 Namespace..................... 7-37 7.7 Configuring Devices........................... 7-37 7.8 Configuring the NSP and OSI Transports........ 7-38 vii 7.9 Configuring the Time Zone Differential Factor (DECdts)...................................... 7-41 7.9.1 DECdts Overview........................... 7-41 7.9.2 Selecting the DECdts Configuration Option.................................... 7-43 7.9.3 Choosing a Time Zone Using Menus.......... 7-44 7.9.4 Using Universal Coordinated Time (UTC).... 7-47 7.9.5 Defining Your Own Time Zone Rule.......... 7-47 7.10 Configuring the Event Dispatcher.............. 7-47 7.11 Configuring the Application Database.......... 7-48 7.11.1 Deleting an Application................... 7-49 7.11.2 Adding an Application..................... 7-49 7.12 Configuring the MOP Client Database........... 7-55 7.12.1 Deleting a MOP Client..................... 7-56 7.12.2 Adding a MOP Client....................... 7-56 7.13 Configuring a Cluster Alias................... 7-58 7.13.1 Deleting an Alias......................... 7-58 7.13.2 Adding an Alias........................... 7-59 7.14 Replacing a MOP Client Configuration.......... 7-59 7.15 Configuring Satellite Nodes................... 7-61 7.15.1 Autoconfiguring Phase IV Cluster Nodes.... 7-63 7.15.2 Electing To Configure Cluster Node Scripts................................... 7-66 7.15.3 Electing to Configure the Local Node...... 7-68 7.15.4 Exiting the Satellite Options Menu........ 7-68 7.16 Configuring Cluster-Common Script Locations... 7-68 7.17 Summary Display............................... 7-74 7.18 Generating New NCL Startup Scripts............ 7-75 7.19 Starting the Network.......................... 7-76 7.20 Customizing the Network Configuration......... 7-77 7.20.1 Creating User-Defined Scripts............. 7-77 Part III Configuring X.25 Functionality on DECnet-Plus for OpenVMS VAX Systems viii 8 Configuring X.25 for OpenVMS VAX 8.1 Terminology................................... 8-1 8.2 Steps in Configuring X.25 for OpenVMS VAX..... 8-2 8.3 Planning the X.25 Configuration............... 8-2 8.3.1 Configuring Client, Direct Connect, and Connector Systems......................... 8-2 8.4 Using the Configuration Program............... 8-4 8.4.1 Invoking the Configuration Program........ 8-4 8.4.2 Common Operations......................... 8-4 8.4.2.1 Entering Information.................... 8-4 8.4.2.2 Moving Within a Section................. 8-5 8.4.3 Moving Between Sections................... 8-6 8.4.4 Keys Used in the Configuration Program.... 8-6 8.4.5 Accessing the Options Menu................ 8-8 8.4.6 Obtaining Help............................ 8-10 8.4.6.1 Obtaining Help on the Program........... 8-10 8.4.6.2 Obtaining General Help.................. 8-10 8.4.6.3 Obtaining Help on a Specific Field or Menu Choice............................. 8-10 8.4.7 Creating the Configuration File........... 8-10 8.4.8 Quitting from the Configuration Program... 8-11 8.4.9 Leaving the Program....................... 8-12 8.5 Configuration Sections........................ 8-12 8.6 Required Configuration Data................... 8-18 8.7 Verifying the Configuration................... 8-43 8.7.1 Preparing to Run the CTP.................. 8-43 8.7.2 Running the CTP........................... 8-45 8.7.2.1 Running the CTP Interactively........... 8-45 8.7.2.2 Running the CTP as a Network Object..... 8-45 8.8 Modifying the Configuration................... 8-45 8.9 Creating a New X.25 Configuration ............ 8-46 Part IV Installing X.25 for OpenVMS on OpenVMS I64 and OpenVMS Alpha Systems ix 9 Preparing to Install X.25 for OpenVMS 9.1 Product Description........................... 9-1 9.2 Locating the Distribution Kit................. 9-1 9.3 Accessing the Online Release Notes............ 9-3 9.4 Time Required for Installation and Configuration................................. 9-3 9.5 Required Hardware............................. 9-4 9.6 Prerequisite Software......................... 9-4 9.7 License Requirements.......................... 9-4 9.7.1 Checking Licenses......................... 9-5 9.8 System Requirements........................... 9-6 9.8.1 Disk Space................................ 9-6 9.8.2 Required System Parameters................ 9-7 9.8.3 Required Privileges and Rights Identifiers............................... 9-7 9.9 Backing Up the System Disk.................... 9-8 9.10 Notifying Users............................... 9-8 10 Installing X.25 for OpenVMS 10.1 Recommended Order for Installing Software..... 10-1 10.2 PCSI Process Account Quotas................... 10-2 10.3 Installing HP X.25 for OpenVMS Using PCSI..... 10-3 10.3.1 X.25 for OpenVMS I64 Installation Dialog.................................... 10-4 10.3.2 X.25 for OpenVMS Alpha Installation Dialog.................................... 10-7 10.3.3 X.25 for OpenVMS De-Installation Example................................... 10-10 10.4 Files Installed on Your System................ 10-11 11 X.25 Post-Installation and Configuration Tasks 11.1 Configuring X.25 for OpenVMS.................. 11-1 11.2 Restart DECnet-Plus........................... 11-2 11.3 Rebooting the System.......................... 11-3 11.4 De-installing X.25 for OpenVMS................ 11-3 x Part V Installing OSI Applications for OpenVMS Systems 12 Preparing to Install the OSI Applications 12.1 Product Descriptions.......................... 12-1 12.2 Locating the Distribution Kit................. 12-2 12.3 Accessing the Online Release Notes............ 12-3 12.4 Time Required for Installation and Configuration................................. 12-4 12.5 Required Hardware............................. 12-4 12.6 Prerequisite Software......................... 12-4 12.7 License Requirements.......................... 12-5 12.7.1 Checking Licenses......................... 12-5 12.8 System Requirements........................... 12-5 12.8.1 Disk Space................................ 12-5 12.8.2 Memory Requirements....................... 12-6 12.8.3 Required Privileges....................... 12-7 12.8.4 Process Quotas for OSAK$SERVER_V3 Account................................... 12-8 12.9 Backing Up the System Disk.................... 12-9 12.10 Notifying Users............................... 12-9 13 Installing the OSI Applications 13.1 PCSI Process Account Quotas................... 13-1 13.2 Starting Installation of the OSI Applications.................................. 13-2 13.3 Installing the OSI Applications............... 13-2 13.4 Starting Up and Shutting Down OSI Applications.................................. 13-6 13.5 The OSAK Installation Verification Procedure..................................... 13-6 13.6 Running the OSIF$CONFIGURE.COM Procedure...... 13-7 13.7 The FTAM Installation Verification Procedure..................................... 13-8 13.7.1 Preparing for the FTAM IVP................ 13-8 13.7.2 Running the FTAM IVP...................... 13-9 13.8 The VT Installation Verification Procedure.... 13-11 13.9 Files Installed on Your System................ 13-11 13.10 Sample OSI Application Installations.......... 13-12 13.10.1 Sample OSAK Installation.................. 13-12 13.10.2 Sample FTAM Installation.................. 13-13 13.10.3 Sample Virtual Terminal Installation...... 13-14 xi 13.11 De-installing OSI Applications................ 13-16 13.12 Sample OSI Application De-installations....... 13-16 13.12.1 Sample Virtual Terminal De-installation... 13-17 13.12.2 Sample FTAM De-installation............... 13-17 13.12.3 Sample OSAK De-installation............... 13-18 14 Configuring the OSI Applications 14.1 FTAM and Virtual Terminal Terminology......... 14-1 14.2 About the OSI Application Entity Database..... 14-1 14.3 Getting Started Configuring Initiating and Responding Entities........................... 14-2 14.3.1 Setting Up Responding Entities............ 14-2 14.3.2 Setting Up Initiating Entities............ 14-2 14.3.3 Example: Performing an FTAM File Copy..... 14-4 14.3.4 Example: Performing a Virtual Terminal Login..................................... 14-5 14.4 About Responding Entities..................... 14-7 14.5 Configuring Addresses for Remote FTAM and VT Applications.................................. 14-7 14.5.1 Adding Address Format Entries............. 14-12 14.5.2 Adding Distinguished Name Format Entries................................... 14-12 14.5.3 Adding Pattern Format Entries............. 14-12 14.6 Registering Responders in the X.500 Directory..................................... 14-13 Part VI Supplemental Reference Material A System Files Loaded During DECnet-Plus Installation B Name Services B.1 Modifying the Search Path Information......... B-1 B.1.1 Creating a Site-Specific Search Path NCL Script.................................... B-3 B.1.2 Using the Search Path to Ease Migration... B-4 B.1.3 Setting Up Naming Templates............... B-4 B.1.4 Domain Synonyms........................... B-5 B.1.4.1 Search Path Naming Template Support for Domain Synonyms......................... B-5 B.1.4.2 Local Aliases........................... B-6 xii B.2 Node Synonym Directories...................... B-6 B.2.1 Defining an Alternate Node Synonym Directory................................. B-7 B.2.2 When to Use the Logical Name.............. B-7 B.3 Using a DNS Version 1 Namespace with DECdns Version 2..................................... B-8 B.3.1 Preparing a DNS Version 1 Namespace for Use by DECdns Version 2................... B-8 B.3.2 Using the DNS Version 1 Namespace......... B-10 B.4 Registering a Node in the Namespace........... B-11 B.4.1 Export/Import File Format................. B-11 B.4.2 Problems Registering a Node............... B-11 C Configuring OSI Transport Over X.25 CONS C.1 OpenVMS I64 and Alpha Configuration of OSI Transport Over X.25 CONS...................... C-4 C.2 OpenVMS VAX Configuration of OSI Transport Over X.25 CONS................................ C-7 D Configuring Link State Routing Nodes Using the ISIS$CONFIGURE Procedure D.1 Prerequisites................................. D-1 D.2 Dialog Structure.............................. D-2 D.3 Outputs....................................... D-2 D.4 Dialog........................................ D-3 D.4.1 LAN and Synchronous Circuit Dialogs....... D-6 D.4.2 X.25 Routing Circuit Dialog............... D-8 D.4.3 Reachable Address Dialog.................. D-9 Index Tables 1 DECnet-Plus for OpenVMS Documentation..... xv 1-1 DECnet-Plus Disk Space Requirements....... 1-8 1-2 Minimum System Parameters Required - Base Software Installation..................... 1-9 1-3 ADD_ System Parameter Values.............. 1-10 2-1 Installation Planning Checklist........... 2-2 xiii 3-1 Process Quotas for the Installing Account................................... 3-8 3-2 Rights Identifiers........................ 3-15 4-1 Choosing an Initial Configuration Option.................................... 4-3 7-1 Choosing a Configuration Option to Modify a Current Configuration................... 7-1 7-2 Application End-User Specification Types..................................... 7-50 7-3 Application Numbers....................... 7-50 7-4 Satellite Configuration Options........... 7-62 8-1 X.25 Terminology.......................... 8-1 8-2 X.25 for OpenVMS VAX Configurations and License Requirements...................... 8-3 8-3 Available Keys Used by the X.25 Configuration Program..................... 8-7 8-4 Configuration Sections Applicable to Client, Direct Connect, and Connector Systems................................... 8-13 8-5 Configuration Information: Lines and DTEs (Direct Connect and Connector Systems Only)..................................... 8-18 8-6 Configuration Information: PVCs (Direct Connect and Connector Systems Only)....... 8-22 8-7 Configuration Information: Groups (Direct Connect and Connector Systems Only)....... 8-22 8-8 Configuration Information: LLC2 DTEs (Direct Connect and Connector Systems Only)..................................... 8-24 8-9 Configuration Information: Remote DTE Classes (Client Systems Only)............. 8-26 8-10 Configuration Information: X.29 and P.S.I. Mail Support (All Systems) ............... 8-26 8-11 Configuration Information: Server Client Nodes (Connector Systems Only)............ 8-27 8-12 Configuration Information: Applications (All Systems)............................. 8-28 8-13 Configuration Information: Declaring a Network Process (All Systems)............. 8-28 xiv 8-14 Configuration Information: Filters - for Applications and Network Processes (All Systems) and Server Clients (Connector Systems Only) ............................ 8-30 8-15 Configuration Information: Templates (All Systems) ................................. 8-32 8-16 Configuration Information: Incoming Security for Applications (All Systems)... 8-35 8-17 Configuration Information: Outgoing Security for Local Processes (All Systems).................................. 8-37 8-18 Configuration Information: Incoming Security for Network Processes (All Systems).................................. 8-39 8-19 Configuration Information: Incoming Security for Server Clients (Connector Systems Only) ............................ 8-40 8-20 Configuration Information: Outgoing Security for Client Systems (Connector Systems Only) ............................ 8-41 10-1 Process Quotas for the Installing Account................................... 10-2 12-1 Minimum Disk Space Requirements........... 12-6 12-2 Required Global Pages, Global Pagelets and Sections.................................. 12-6 12-3 OSAK$SERVER_V3 Process Account Quotas..... 12-8 12-4 Account Quotas for Processes that use OSAK Software.................................. 12-9 13-1 Process Quotas for the Installing Account................................... 13-1 14-1 Default Addresses......................... 14-7 14-2 X.500 Configuration Checklist............. 14-9 14-3 Address Format Worksheet.................. 14-11 C-1 Sample X.25 Configuration Information..... C-2 D-1 Routing Protocol Options.................. D-4 xv _________________________________________________________________ Preface This book describes how to install and configure HP DECnet- Plus for OpenVMS using the three available configuration options (FAST, BASIC, and ADVANCED). It also discusses how to use the configuration procedure to modify existing DECnet-Plus for OpenVMS configurations. The book also describes how to install and configure: o X.25 functionality on OpenVMS VAX systems (formally known as VAX P.S.I. software) o X.25 for OpenVMS on OpenVMS I64 and OpenVMS Alpha systems o The optional OSI layered applications software components: - OSI Applications Kernel (OSAK) - File Transfer, Access, and Management (FTAM) - Virtual Terminal (VT) ________________________ Note ________________________ DECnet-Plus for OpenVMS must be installed on your system before you can install X.25, FTAM, VT, or OSAK software. ______________________________________________________ xiii 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 prerequisite steps necessary to install the DECnet-Plus for OpenVMS software and the installation dialog used to install the software. Part II Provides help to determine which configuration option to use: FAST, BASIC or ADVANCED. It describes using each of the configuration options to configure a new DECnet-Plus node. It also discusses using the BASIC or ADVANCED configuration option to modify an existing configuration. Part IIIDescribes the steps necessary to configure X.25 functionality on DECnet-Plus for OpenVMS VAX systems. This functionality was previously a separate product known as VAX P.S.I. Part IV Describes the prerequisite steps necessary to install the X.25 for OpenVMS software on an OpenVMS I64 or OpenVMS Alpha system and the installation dialog used to install the software. It also serves as an introduction to the configuration tasks discussed in the HP X.25 for OpenVMS Configuration manual. Part V Describes the prerequisite steps necessary to install the optional OSI applications software components and the installation dialog used to install the software. It also describes how to configure the FTAM and VT applications. Part VI Reference appendixes useful to the installation and configuration process. xiv Terminology The following terms are used interchangeably in this book: o Transition and migration o DECnet Phase IV and Phase IV o End system and end node o Intermediate system and router o DECnet-Plus and Phase V Guide to Documentation DECnet-Plus for OpenVMS documentation is available in two sets: o Documentation set for DECnet-Plus for OpenVMS o Supplemental X.25 for OpenVMS documentation set Table 1 lists the documentation that supports this version of the DECnet-Plus for OpenVMS software. Table_1_DECnet-Plus_for_OpenVMS_Documentation______________ Document___________________Contents________________________ DECnet-Plus_for_OpenVMS_Documentation_Set__________________ DECnet-Plus for OpenVMS Describes the manuals in the Introduction and User's documentation sets, outlines Guide the DECnet-Plus for OpenVMS features and tools, explains how to use and manage an end system, and provides a comprehensive glossary of DECnet terminology. (continued on next page) xv Table_1_(Cont.)_DECnet-Plus_for_OpenVMS_Documentation______ Document___________________Contents________________________ DECnet-Plus_for_OpenVMS_Documentation_Set__________________ HP DECnet-Plus for Describes changes to the OpenVMS Release Notes software; installation, upgrade, and compatibility information; new and existing software problems and restrictions; and software and documentation corrections. Note: Print this file at the beginning of the installation procedure and read it before you install DECnet-Plus for OpenVMS. DECnet-Plus Planning Provides configuration and Guide planning guidelines, including namespace planning information, to help you transition a network from the DECnet Phase IV to DECnet Phase V architecture. (continued on next page) xvi Table_1_(Cont.)_DECnet-Plus_for_OpenVMS_Documentation______ Document___________________Contents________________________ DECnet-Plus_for_OpenVMS_Documentation_Set__________________ HP DECnet-Plus for Explains how to install and OpenVMS Installation configure the DECnet-Plus for and Configuration OpenVMS software using the three configuration options (FAST, BASIC, and ADVANCED). Also explains how to modify an existing configuration. Explains how to configure the X.25 functionality included with the DECnet-Plus for OpenVMS VAX software (formerly provided by the VAX P.S.I. Access and VAX P.S.I. products). Explains how to install the separate X.25 for OpenVMS software product available for OpenVMS I64 and OpenVMS Alpha systems. For configuration information, see the HP X.25 for OpenVMS Configuration manual. Explains how to install and configure the optional OSI applications software components (OSI Applications Kernel (OSAK), OSI File Transfer, Access, and Management (FTAM), and OSI Virtual Terminal (VT)). (continued on next page) xvii Table_1_(Cont.)_DECnet-Plus_for_OpenVMS_Documentation______ Document___________________Contents________________________ DECnet-Plus_for_OpenVMS_Documentation_Set__________________ HP DECnet-Plus for Provides in-depth information OpenVMS Network about how to monitor and manage Management DECnet-Plus for OpenVMS systems using various tools and Network Control Language (NCL) commands. Explains how to set up and use event dispatching and how to perform all day-to-day management tasks for the local DECnet-Plus for OpenVMS node, including setting up OpenVMS clusters, managing security, downline loading, and monitoring the network. DECnet-Plus for OpenVMS Provides quick-reference Network Management Quick information about the tools Reference Guide that help you manage and monitor a DECnet-Plus network. Use this guide with the HP DECnet-Plus for OpenVMS Network Management manual. HP DECnet-Plus for Outlines command descriptions OpenVMS Network Control and examples for all Network Language Reference Control Language (NCL) commands that you execute to manage, monitor, and troubleshoot the network. Begins with an orientation chapter that contains information about how to execute NCL commands, followed by a command chapter for each module in the DECnet Phase V layered model. (continued on next page) xviii Table_1_(Cont.)_DECnet-Plus_for_OpenVMS_Documentation______ Document___________________Contents________________________ DECnet-Plus_for_OpenVMS_Documentation_Set__________________ DECnet-Plus Problem Explains how to isolate and Solving solve DECnet problems in an OpenVMS environment that can occur while the network is in operation. Includes information about how to perform loopback tests and how to use the DTS/DTR utility to solve problems. HP DECnet-Plus for Explains HP DECnet-Plus OpenVMS DECdns Management Distributed Name Service (DECdns) concepts and how to manage a DECdns distributed namespace. Use this manual with the DECnet-Plus Planning Guide. HP DECnet-Plus for Introduces HP DECnet-Plus OpenVMS DECdts Management Distributed Time Service (DECdts) concepts and describes how to manage the software and system clocks. DECnet-Plus DECdts Contains DECdts time routine Programming reference information and describes the time-provider interface (TPI). DECnet-Plus OSAK Explains how to use the OSAK Programming (OSI Applications Kernel) interface to create OSI (Open Systems Interconnection) applications for any supported operating system. DECnet-Plus OSAK Provides reference information Programming Reference on using the OSAK interface to create OSI applications on any supported operating system. (continued on next page) xix Table_1_(Cont.)_DECnet-Plus_for_OpenVMS_Documentation______ Document___________________Contents________________________ DECnet-Plus_for_OpenVMS_Documentation_Set__________________ DECnet-Plus OSAK SPI Provides reference information Programming Reference about using the OSAK session programming interface (SPI) to create OSI applications on any supported operating system. DECnet-Plus FTAM and Explains how to use and manage Virtual Terminal Use and FTAM (File Transfer, Access, and Management Management) software for remote file transfer and management and VT (Virtual Terminal) for remote login to OSI-compliant systems. DECnet-Plus FTAM Explains how to access the Programming FTAM protocol through FTAM's API (application programming interface). DECnet-Plus for OpenVMS Contains information about Programming how to design and write an application that follows a client/server model and uses the OpenVMS Interprocess Communication ($IPC) system service and the transparent and nontransparent communication with the queue Input/Output ($QIO) system service. Explains how to write programs using the OpenVMS system services to communicate with OSI transport services. Provides information about the Common Management Information Service (CMISE) API. (continued on next page) xx Table_1_(Cont.)_DECnet-Plus_for_OpenVMS_Documentation______ Document___________________Contents________________________ DECnet-Plus_for_OpenVMS_Documentation_Set__________________ DECnet/OSI for VMS CTF Explains how use the Use Common Trace Facility (CTF) troubleshooting tool to collect and analyze protocol data from networking software. (continued on next page) xxi Table_1_(Cont.)_DECnet-Plus_for_OpenVMS_Documentation______ ___________________________________________________________ Supplemental_X.25_Documentation_Set________________________ HP X.25 for OpenVMS Discusses how to configure Configuration X.25 for OpenVMS on an OpenVMS I64 or OpenVMS Alpha system. For information about how to configure the X.25 functionality on OpenVMS VAX systems, see the HP DECnet-Plus for OpenVMS Installation and Configuration manual. HP X.25 for OpenVMS Explains how to manage and Management Guide monitor an X.25 system using network tools. HP X.25 for OpenVMS Explains the X.25 security model Security Guide and the tasks required to set up and manage X.25 security. HP X.25 for OpenVMS Provides guidance on how to Problem Solving solve problems that can occur while using an X.25 system. HP X.25 for OpenVMS Explains how to use and Utilities manage the X.25 Mail and X.29 communications utilities. HP X.25 for OpenVMS Explains how to use X.25 Accounting accounting to obtain performance records and information about how X.25 is being used. HP X.25 for OpenVMS Explains how to write X.25 and Programming X.29 programs to perform network operations. HP X.25 for OpenVMS Provides reference information Programming Reference for X.25 and X.29 programmers. DECnet/OSI for VMS VAX Provides information about using WANDD Programming the programming interface for ___________________________the_WANDD_devices.______________ The following OpenVMS manuals provide additional information: xxii o OpenVMS License Management Utility Manual o OpenVMS System Management Utilities Reference Manual Reader's Comments HP welcomes your comments on this manual or any of the DECnet-Plus documents. Please send comments to either of the following addresses: Internet openvmsdoc@hp.com Mail Hewlett-Packard Company OSSG Documentation Group, ZKO3-4/U08 110 Spit Brook Rd. Nashua, NH 03062-2698 How To Order Additional Documentation For information about how to order additional documentation and for online versions of most DECnet-Plus documentation, visit the following World Wide Web address: http://www.hp.com/go/openvms/doc/ 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. xxiii ___________________________________________________________ Convention_______Meaning___________________________________ 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.__________________________________ xxiv Part I _________________________________________________________________ Installing DECnet-Plus for OpenVMS Part I describes the prerequisite steps necessary to install the HP DECnet-Plus for OpenVMS software and the installation dialog used to install the software. It contains the following chapters: 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 HP DECnet-Plus for OpenVMS software. 1.1 Locating the Distribution Kit To obtain the directory location of the DECnet-Plus kit on the CD-ROM, refer to the OpenVMS Software Product Library CD-ROM User's Guide that accompanies the CD-ROM distribution kit. Alternatively, complete the following steps: 1. To obtain the kit directory location of the DECnet-Plus distribution files on the appropriate OpenVMS Software Product Library CD-ROM (media CD-ROM), do one of the following: o Use the CDMENU utility provided on the media CD-ROM. o View the CD-ROM master index file on the media CD- ROM. For information about using the CDMENU utility and the CD-ROM files on the media CD-ROM, see the Software Product Library CD-ROM User's Guide that accompanies the media CD-ROM distribution kit. The media CD-ROM user guide and CD-ROM master index file are provided as online files in the [README] directory on the first media CD-ROM. 2. To determine if the appropriate CD-ROM is already mounted on your system, enter the following command: Preparing to Install DECnet-Plus for OpenVMS 1-1 Preparing to Install DECnet-Plus for OpenVMS 1.1 Locating the Distribution Kit $ show device dka400: ________________________ Note ________________________ The device DKA400 is used in examples in this document as the device where the appropriate CD-ROM has been mounted. ______________________________________________________ 3. If the media CD-ROM containing the DECnet-Plus kit is not mounted, insert the appropriate CD-ROM (write down the volume label) into an available CD-ROM drive. Enter the appropriate mount command to mount the media CD-ROM (omit the /FOREIGN qualifier): $ mount dka400: label where label is the volume label of the media CD-ROM. 4. Define the logical name PCSI$SOURCE to reference the appropriate kit directory on the Software Product Library Compact Disk. For example, if the DECnet-Plus kit is located in the [DECNETPLUS083] directory on device DKA400, enter the following command: $ define pcsi$source dka400:[decnetplus083] 5. To verify the DECnet-Plus kit name, use a directory command specifying the PCSI$SOURCE logical name: $ directory pcsi$source:*.pcsi The distribution kit contains the following component kit files: o Base components software - DECnet-Plus for OpenVMS base kit o Optional software - OSI Applications Kernel kit (OSAK software) - OSI File Transfer, Access, and Management application kit (FTAM software) - OSI Virtual Terminal kit (VT software) 1-2 Preparing to Install DECnet-Plus for OpenVMS Preparing to Install DECnet-Plus for OpenVMS 1.1 Locating the Distribution Kit For a more detailed list, see Chapter 3. ________________________ Note ________________________ Before installing any of the software, read the DECnet-Plus Planning Guide. This guide contains installation planning information, including namespace planning instructions. ______________________________________________________ 1.2 Accessing the Online Release Notes You should review the release notes for a description of new features, differences between multiple versions of DECnet-Plus, and changes in the installation procedure. To access the release notes, issue the following command: $ product extract release_notes decnet_osi /file=filename In the above example, it is assumed that the logical name PCSI$SOURCE properly references the directory location of the DECnet-Plus kit. Details on how to determine the directory location of the DECnet-Plus kit are provided in Section 1.1. The product selected is displayed and you are prompted to continue with the extraction. To extract the release notes, type YES and press Return. The release notes are written to the specified file, which you can display or print. If you do not use the /FILE qualifier to define the required location of the extracted release notes, the release notes are extracted into the file default.pcsi$release_notes in the current directory. To cancel the extraction, type NO and press Return. ________________________ Note ________________________ After DECnet-Plus is installed, the release notes file is located in sys$help in the form decnet-plus- v*.release_notes. ______________________________________________________ Preparing to Install DECnet-Plus for OpenVMS 1-3 Preparing to Install DECnet-Plus for OpenVMS 1.3 Time Required for Installation and Configuration 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 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 Required Hardware The DECnet-Plus for OpenVMS installation process requires the following hardware: o A CD-ROM reader o A terminal You can use either a hardcopy or video terminal to communicate with the operating system and respond to prompts from the installation procedure. Refer to the OpenVMS Operating System for I64, Alpha and VAX Software Product Description (SPD 25.01.xx) for hardware requirements and processor support for the DECnet- Plus software. 1.5 Prerequisite Software Before you can install and configure the software, the system must have the required operating system software. In addition, if you intend to use any optional software supported by DECnet-Plus for OpenVMS, you must use the supported versions of these software products. For specific information about the required versions of prerequisite software, see the HP DECnet-Plus for OpenVMS Software Product Description. 1-4 Preparing to Install DECnet-Plus for OpenVMS Preparing to Install DECnet-Plus for OpenVMS 1.5 Prerequisite Software 1.5.1 Checking the Operating System Version To determine the OpenVMS operating system version number, enter the following DCL command: $ show system 1.5.2 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 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. For more information about required TCP/IP software, see the HP DECnet-Plus for OpenVMS Release Notes. ________________________ Note ________________________ For more information on using DECnet over TCP/IP or the OSI applications over TCP/IP, refer to the HP DECnet-Plus for OpenVMS Network Management guide. ______________________________________________________ 1.6 License Requirements DECnet-Plus for OpenVMS uses three licenses. The specific license required on your system is determined by the functions you want to use and your CPU type: o Basic function license (DVNETEND) - provides end system support. o Extended function license (DVNETEXT) for OpenVMS I64 and OpenVMS Alpha systems - provides end system support, host-based routing support, DECdns server, DECdts server, cluster alias, and OSI applications gateways. o Extended function license (DVNETRTG) for OpenVMS VAX systems - provides end system support, host-based routing support, DECdns server, DECdts server, cluster alias, and OSI applications gateways. __ License Requirements for OpenVMS for I64 Systems __ HP DECnet-Plus for OpenVMS Version 8.3 for I64 systems requires the Foundation Operating Environment (FOE) Preparing to Install DECnet-Plus for OpenVMS 1-5 Preparing to Install DECnet-Plus for OpenVMS 1.6 License Requirements license. This license includes the basic function license (DVNETEND). If you intend to configure your system as a DECdns server, you must obtain a separate DVNETEXT license. ______________________________________________________ At least one node of an OpenVMS Cluster system requires the appropriate extended function license (DVNETEXT or DVNETRTG) to use the cluster alias feature. If you install the DECnet-Plus software without the appropriate extended function license and then attempt to configure your system as a DECdns server, the DECdns server will fail and the configuration utility (net$configure.com) will exit. In addition to the three DECnet-Plus for OpenVMS licenses, you may need additional licenses to use certain features of DECnet-Plus. o In addition to the appropriate DECnet-Plus extended function license, the TELNET/VT gateway also requires an HP TCP/IP Services for OpenVMS license. o In addition to the DECnet-Plus base function license, certain X.25 wide area network features on OpenVMS Alpha and OpenVMS I64 systems require a separate X.25 for OpenVMS license. For more information, see Section 9.7. o In addition to the DECnet-Plus base function license, certain X.25 wide area network features on OpenVMS VAX systems require an X.25 license. For more information, see Section 8.3.1. 1.6.1 Checking Licenses To determine if a DECnet-Plus license is registered, enter the following DCL command: $ show license dvnet* If the system does not have the required licenses, 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-6 Preparing to Install DECnet-Plus for OpenVMS Preparing to Install DECnet-Plus for OpenVMS 1.7 System Requirements 1.7 System Requirements Before you install the DECnet-Plus for OpenVMS software, make sure that your system meets the requirements discussed in the following sections. 1.7.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 has already allocated most of the space that a subsequent installation needs. Table 1-1 shows the amount of disk space needed to install the DECnet-Plus software components. Make sure you have enough free space to install the required software and the optional software. Preparing to Install DECnet-Plus for OpenVMS 1-7 Preparing to Install DECnet-Plus for OpenVMS 1.7 System Requirements Table_1-1_DECnet-Plus_Disk_Space_Requirements______________ Blocks for Blocks for Component________I64___________Alpha_________Blocks_for_VAX Base components 160000 92000 77000 DECdts server 3500 1600 1800 DECdns 15000 15000 3000 server[1] WANDD 10000 5000 5500 X.25 for 20000 10000 10000 OpenVMS OSAK 12300 6600 6000 FTAM 42700 31800 12000 Virtual 9800 3300 2000 Terminal Totals 273300 165300 117300 [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.7.2 Required Memory The minimum amount of memory required is 512 MB for OpenVMS I64 systems, 64 MB for OpenVMS Alpha systems, and 24 MB for OpenVMS VAX systems. To check the amount of memory on your system, enter the following command: $ show memory/full 1-8 Preparing to Install DECnet-Plus for OpenVMS Preparing to Install DECnet-Plus for OpenVMS 1.7 System Requirements 1.7.3 Required System Parameters This section provides information about 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____________________________ Parameter___________Minimum_Value__________________________ For_OpenVMS_I64_Systems:___________________________________ ARB_SUPPORT 3 MIN_CLISYMTBL 750 MIN_GBLPAGES 100000 MIN_GBLPAGFIL 1024 MIN_GBLSECTIONS 512 MIN_KSTACKPAGES 2 ___________________________________________________________ For_OpenVMS_Alpha_Systems:_________________________________ ARB_SUPPORT 3 MIN_CLISYMTBL 750 MIN_GBLPAGES 100000 MIN_GBLPAGFIL 1024 MIN_GBLSECTIONS 512 MIN_KSTACKPAGES 2 MIN_NPAGEDYN 2100000 ___________________________________________________________ For_OpenVMS_VAX_Systems:___________________________________ MIN_CLISYMTBL 500 MIN_GBLPAGES 50000 MIN_GBLPAGFIL 4096 MIN_GBLSECTIONS 400 MIN_VIRTUALPAGECNT____35000________________________________ Preparing to Install DECnet-Plus for OpenVMS 1-9 Preparing to Install DECnet-Plus for OpenVMS 1.7 System Requirements In addition to the minimum system parameter values, DECnet- Plus also requires several ADD_ parameter values to ensure adequate resources are available. These values are listed in Table 1-3. Table_1-3_ADD__System_Parameter_Values_____________________ Parameter___________Value__________________________________ For_OpenVMS_I64_Systems:___________________________________ ADD_GBLPAGES 75000 ADD_GBLPAGFIL 512 ADD_GBLSECTIONS 200 ADD_GH_EXEC_CODE 256 ADD_NPAGEDYN 3800000 ___________________________________________________________ For_OpenVMS_Alpha_Systems:_________________________________ ADD_GBLPAGES 55000 ADD_GBLPAGFIL 256 ADD_GBLSECTIONS 100 ___________________________________________________________ For_OpenVMS_VAX_Systems:___________________________________ ADD_GBLPAGES 55000 ADD_GBLSECTIONS_________100________________________________ ______________________ Important ______________________ For most DECnet installations, it is not necessary for you to add the preceding system parameters to the modparams.dat file. These parameters are automatically taken into consideration when DECnet is installed or upgraded. If necessary, prior to installing this release of DECnet-Plus, you should edit modparams.dat and remove any entries that you may have made for previous DECnet-Plus installations. Use the preceding tables as a guide. Different versions of DECnet-Plus have had different parameter values; however, the parameter list has remained consistent for most recent releases. 1-10 Preparing to Install DECnet-Plus for OpenVMS Preparing to Install DECnet-Plus for OpenVMS 1.7 System Requirements See the "Server Tuning" and "Client Tuning" sections in the "DECdns Problem Solving" chapter of the HP DECnet-Plus for OpenVMS DECdns Management manual for examples of when it might still be necessary to make DECnet-related changes to modparams.dat. Note that any ADD_ values you place in modparams.dat are added to the standard ADD_ values in Table 1-3. DECnet and AUTOGEN use two files, newparams.dat and clu$params.dat, to support this automatic system parameter setting. The DECnet-Plus installation procedure creates a newparams.dat file to provide AUTOGEN with the DECnet-Plus system parameter requirements. When AUTOGEN is run, it first renames any existing clu$params.dat file to clu$params.old. Then it takes the values found in all existing newparams.dat files and creates a new clu$params.dat file containing the results of its newparams.dat scan. AUTOGEN then renames the newparams.dat files to newparams.done. During AUTOGEN, the parameters found in clu$params.dat are used in much the same fashion as parameters found in modparams.dat. ______________________________________________________ To check any system parameter, invoke the SYSGEN utility and enter the show command. For example, to view the current value for GBLSECTIONS, 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 2. Enter the values into the file in the following format: ADD_GBLSECTIONS=512 . . . ADD_GBLPAGFIL=1024 3. Exit from the editor. Preparing to Install DECnet-Plus for OpenVMS 1-11 Preparing to Install DECnet-Plus for OpenVMS 1.7 System Requirements 4. Run AUTOGEN by entering the following command: $ @sys$update:autogen getdata reboot _______________________ Warning _______________________ In the unlikely event that the required minimum system parameter requirements are no longer met by the current system parameter settings, the network startup will fail. If the network fails to start for this reason, the logical name NET$STARTUP_STATUS is set to OFF-AUTOGENREQ. If this occurs you must edit the modparams.dat file directly and set the parameters to the values shown in Table 1-2 and Table 1-3. ______________________________________________________ 1.7.3.1 SYSGEN Parameters for OpenVMS Cluster Members When installing DECnet-Plus for OpenVMS on an OpenVMS Cluster, make sure that you apply any custom SYSGEN parameter values you may have added to all cluster members. 1.7.4 Required Privileges and Rights Identifiers HP 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 o TMPMBX o OPER o SYSNAM o WORLD 1-12 Preparing to Install DECnet-Plus for OpenVMS Preparing to Install DECnet-Plus for OpenVMS 1.7 System Requirements ________________________ 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. ______________________________________________________ To determine the default privileges of the installing account, log in and enter the following DCL command: $ show process/privileges 1.8 Backing Up the System Disk Use the OpenVMS BACKUP utility to make a copy of the system disk. 1.9 Notifying Users Inform users on the system that you plan to install a product and that they must log out. First, prevent nonprivileged users from logging in to the system: $ set logins/interactive=0 Next, 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: $ reply/all "Installing DECnet-Plus 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-13 2 _________________________________________________________________ Pre-Installation Tasks Before installing the HP DECnet-Plus for OpenVMS 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.4.1 addresses from a DECdns and Section 6.4.2 name server? If yes, what is the system's DECdns node name (for example, ACME:.BOSTON)? ___________________________________________________________ Will the system store < > < > See Section 6.4.1 network addresses in a and Section 6.4.2 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.4.1 system? Will the system and Section 6.4.2 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.4.3 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.5.3 with Phase IV nodes? and Section 6.5.4 o Phase IV-compatible address (for example, 2.38) o Phase IV Prefix (the default is 49::) ___________________________________________________________ Will the system < > < > See Section 6.5.5.1 autoconfigure its network addresses? If not, you will need network entity ti- tles (for example, 47:24:02-01-0A-04:08-00-2B-93-ED-99:00). ___________________________________________________________ Do you want to install < > < > Refer to the DECnet- DECdns server software? Plus Planning Guide. ___________________________________________________________ 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 OpenVMS VAX only.) Do < > < > Refer to Part III. you want to install X.25 functionality and WANDD software for VAX? You must install this software if you want to use any of the following: - Non-LAN connections to the network - Routing over synchronous connections - X.25 software over synchronous lines - 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 (For OpenVMS I64 and < > < > Refer to Part IV. OpenVMS Alpha only.) Do you want to install X.25 for OpenVMS? You must install this software if you want to use any of the following: - X.25 communications via a connector system (Client system) - X.25 communications directly from the local system (Direct Connect system) - X.25 communications on behalf of other systems (Connector system) - LAN X.25 (LLC Class 2) - DECnet over X.25 ___________________________________________________________ Do you want to install < > < > Refer to Part V. DECnet-Plus for OpenVMS OSAK software? If you plan to use an OSI application such as FTAM or Virtual Terminal, you must install this software. ___________________________________________________________ (continued on next page) Pre-Installation Tasks 2-5 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 Part V. DECnet-Plus for OpenVMS FTAM software? If you plan to copy files to and from other OSI- compliant systems or manage such files, you must install this software. ___________________________________________________________ Do you want to install < > < > Refer to Part V. DECnet-Plus for OpenVMS Virtual Terminal (VT) software? If you plan to support remote logins and access to remote applications on OSI-compliant systems, you must_install_this_software.________________________________ 2-6 Pre-Installation Tasks 3 _________________________________________________________________ Installing DECnet-Plus for OpenVMS The HP DECnet-Plus for OpenVMS distribution software is provided on compact disc (CD-ROM). The software consists of the following components: Components for OpenVMS I64 and OpenVMS Alpha Systems o Base Components - DECnet-Plus for OpenVMS base kit - DECdns server - DECdts server o X.25 for OpenVMS (separate kit; requires a separate license) - Wide Area Network Device Drivers (WANDD) for OpenVMS I64 and OpenVMS Alpha o Optional OSI applications software components (included with the base kit but must be installed separately) - OSI Applications Kernel (OSAK) - OSI File Transfer, Access, and Management (FTAM) - OSI Virtual Terminal (VT) Components for OpenVMS VAX Systems o Base Components - DECnet-Plus for OpenVMS base kit - X.25 functionality for OpenVMS VAX (formerly VAX P.S.I.) - WANDD for OpenVMS VAX - DECdns server - DECdts server Installing DECnet-Plus for OpenVMS 3-1 Installing DECnet-Plus for OpenVMS o Optional OSI applications software components (included with the base kit but must be installed separately) - OSAK - FTAM - VT 3-2 Installing DECnet-Plus for OpenVMS Installing DECnet-Plus for OpenVMS ________________________ Note ________________________ The DECnet-Plus base components, OSAK, FTAM, and VT, are all packaged as separate installation kits on the distribution CD-ROM. They are usually located in the same directory. The X.25 for OpenVMS kit, however, is a separately licensed product and as such is in a different directory on the distribution CD-ROM. 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 the OpenVMS System Management Utilities Reference Manual 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. 3.1.1 Installing DECnet-Plus on an OpenVMS I64 or 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. Locate the distribution kit. Access the online Release Notes. Verify required hardware. See Sections 1.1 through 1.4. 2. Verify that all prerequisite software and licenses are installed. See Sections 1.5 and 1.6. 3. Back up the system disk. Shut down all network-related applications and tell users to log out. See Sections 1.8 and 1.9. 4. Install DECnet-Plus for OpenVMS. See Section 3.3. Installing DECnet-Plus for OpenVMS 3-3 Installing DECnet-Plus for OpenVMS 3.1 Recommended Order for Installing Software 5. If necessary, set any required system parameters. See Section 1.7. 6. Reboot the system. 7. Install X.25 for OpenVMS and WANDD, if necessary. See Chapter 9 and Chapter 10. 8. Configure DECnet-Plus for OpenVMS. See Chapter 4 to determine which configuration option to choose: FAST, BASIC, or ADVANCED. For a FAST configuration, see Chapter 5. For BASIC or ADVANCED configurations, see Chapter 6. 9. Configure X.25 for OpenVMS. See the HP X.25 for OpenVMS Configuration manual. 10. Install and configure the optional OSI applications software components (OSAK, FTAM, and VT). See Chapter 12 and Chapter 13. 3-4 Installing DECnet-Plus for OpenVMS Installing DECnet-Plus for OpenVMS 3.1 Recommended Order for Installing Software 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 on an OpenVMS 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. Locate the distribution kit. Access the online Release Notes. Verify required hardware. See Sections 1.1 through 1.4. 2. Verify that all prerequisite software and licenses are installed. See Sections 1.5 and 1.6. 3. Back up the system disk. Shut down all network-related applications and tell users to log out. See Sections 1.8 and 1.9. 4. Install DECnet-Plus for OpenVMS. See Section 3.3. ________________________ Note ________________________ If you want to install X.25 functionality (formerly VAX P.S.I.), select the option now while installing DECnet-Plus for OpenVMS. ______________________________________________________ 5. If necessary, set any required system parameters. See Section 1.7. 6. Reboot the system. 7. Configure DECnet-Plus for OpenVMS. See Chapter 4 to determine which configuration option to choose: FAST, BASIC, or ADVANCED. For a FAST configuration, see Chapter 5. For a BASIC or ADVANCED configuration, see Chapter 6. 8. Configure X.25 functionality (formerly VAX P.S.I.). See Chapter 8. 9. Install and configure the optional OSI applications software component (OSAK, FTAM, and VT). See Chapter 12 and Chapter 13. 3-6 Installing DECnet-Plus for OpenVMS Installing DECnet-Plus for OpenVMS 3.1 Recommended Order for Installing Software Installing DECnet-Plus for OpenVMS 3-7 Installing DECnet-Plus for OpenVMS 3.2 PCSI Process Account Quotas 3.2 PCSI Process Account Quotas The POLYCENTER Software Installation utility requires that the installation account has, as a minimum, the quotas shown in Table 3-1. Table_3-1_Process_Quotas_for_the_Installing_Account________ Quota_____Value____________________________________________ ASTLM 24 BIOLM 18 BYTLM 32768 DIOLM 18 ENQLM 200 FILLM_____100______________________________________________ Use the OpenVMS Authorize utility to verify and change process quotas for the installation account in the user authorization file (sysuaf.dat). (Some sites may restrict the use of the OpenVMS Authorize utility to certain accounts or people.) For example, to verify and then change the BYTLM quota for the account-name installation account, enter the following command sequence: ___________________________________________________________ To..._______________Enter..._______________________________ Invoke the $ run sys$system:authorize Authorize utility Show the account UAF> show account-name quotas Modify the BYTLM UAF> modify account-name /BYTLM = 32768 quota Exit from the UAF> exit Authorize utility Log_out_____________$_logout_______________________________ After you verify and change the quotas for the installation account, log out of the installation account and log in 3-8 Installing DECnet-Plus for OpenVMS Installing DECnet-Plus for OpenVMS 3.2 PCSI Process Account Quotas again. The new quotas will take effect and you can proceed with the installation. User account quotas are stored in the sysuaf.dat file. For more information about modifying account quotas, see the description of the Authorize utility in the OpenVMS system management documentation subkit. 3.3 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. You must have SYSPRV privileges on the local or remote node where you want to run this utility. ________________________ Note ________________________ Kits included on the OpenVMS Version 8.3 distribution media are signed using Secure Delivery. ______________________________________________________ 3.3.1 DECnet-Plus for OpenVMS I64 Installation Dialog To start the installation, follow these steps: 1. Log in to the SYSTEM account. 2. Mount the Software Products Library media CD-ROM, locate the DECnet-Plus distribution directory, and define the PCSI$SOURCE logical name to reference the directory. See Section 1.1 for information about locating the distribution kit. 3. Enter the following command: $ product install DECNET_PLUS For a description of all the features you can request when starting an installation (such as purging files and using a product configuration file), refer to DCL help for the product install command. The actual kit location may change with new releases. See Section 1.1 for information about locating the distribution kit. Installing DECnet-Plus for OpenVMS 3-9 Installing DECnet-Plus for OpenVMS 3.3 Installing DECnet-Plus Using the POLYCENTER Software Installation Utility 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. Performing product kit validation ... %PCSI-I-VALPASSED, validation of DKB200:[KITS]HP-I64VMS-DECNET_PLUS-V0803--1.PCSI$COMPRESSED;1 succeeded The following product has been selected: HP I64VMS DECNET_PLUS V8.3 Layered Product 1 Do you want to continue? [YES] Configuration phase starting ... You will be asked to choose options, if any, for each selected product and for any products that may be installed to satisfy software dependency requirements. HP I64VMS DECNET_PLUS V8.3: DECnet-Plus V8.3 for OpenVMS I64 Copyright 2006 Hewlett-Packard Development Company, L.P. Hewlett-Packard Company This product requires one of two PAKs: DVNETEND or DVNETEXT. 2 Do you want the defaults for all options? [YES] NO HP I64VMS VMS V8.3 [Installed] * Configuration options for this referenced product cannot * be changed now because the product is already installed. * (You can use PRODUCT RECONFIGURE later to change options.) DECdns Server software [NO] YES DECdts Server software [NO] YES 3 Do you want to review the options? [NO] YES HP I64VMS DECNET_PLUS V8.3: DECnet-Plus V8.3 for OpenVMS I64 HP I64VMS VMS V8.3 [Installed] DECdns Server software: YES DECdts Server software: YES 4 Are you satisfied with these options? [YES] Execution phase starting ... The following product will be installed to destination: HP I64VMS DECNET_PLUS V8.3 DISK$XBAI:[VMS$COMMON.] 3-10 Installing DECnet-Plus for OpenVMS Installing DECnet-Plus for OpenVMS DECnet-Plus Using the POLYCENTER Software Installation Utility Portion done: 0%...10%...20%...30%...40%...50%...60%...80%...90%...100% The following product has been installed: HP I64VMS DECNET_PLUS V8.3 Layered Product $ 1 At this point, you can stop the installation process. If you want to continue, press Return. If you want to stop, type NO and press Return. 2 This question allows you to select which optional parts of the DECnet-Plus base components product you want to install. If you want to take the installation defaults, press Return. If you want to select each optional DECnet-Plus base component (for example, DECdns Server), 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. 4 Responding NO to this question causes the procedure to reprompt you to enter values for each of the installation options. If you are satisfied with the options, press Return to accept the default YES response. 3.3.2 DECnet-Plus for OpenVMS Alpha Installation Dialog To start the installation, follow these steps: 1. Log in to the SYSTEM account. 2. Mount the Software Products Library media CD-ROM, locate the DECnet-Plus distribution directory, and define the PCSI$SOURCE logical name to reference the directory. See Section 1.1 for information about locating the distribution kit. 3. Enter the following command: $ product install DECnet_OSI For a description of all the features you can request when starting an installation (such as purging files and using a product configuration file), refer to DCL help for the product install command. Installing DECnet-Plus for OpenVMS 3-11 Installing DECnet-Plus for OpenVMS 3.3 Installing DECnet-Plus Using the POLYCENTER Software Installation Utility The actual kit location may change with new releases. See Section 1.1 for information about locating the distribution 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. Performing product kit validation ... %PCSI-I-VALPASSED, validation of DKB500:[KITS]DEC-AXPVMS-DECNET_OSI-V0803--1.PCSI$COMPRESSED;1 succeeded The following product has been selected: DEC AXPVMS DECNET_OSI V8.3 Layered Product 1 Do you want to continue? [YES] Configuration phase starting ... You will be asked to choose options, if any, for each selected product and for any products that may be installed to satisfy software dependency requirements. DEC AXPVMS DECNET_OSI V8.3: DECnet-Plus V8.3 for OpenVMS AXP Copyright 2006 Hewlett-Packard Development Company, L.P. Hewlett-Packard Company This product requires one of two PAKs: DVNETEND or DVNETEXT. 2 Do you want the defaults for all options? [YES] NO Do you want to change any options? [YES] DEC AXPVMS VMS V8.3 [Installed] * Configuration options for this referenced product cannot * be changed now because the product is already installed. * (You can use PRODUCT RECONFIGURE later to change options.) DECdns Server software [NO] YES DECdts Server software [NO] YES 3 Do you want to review the options? [NO] Execution phase starting ... The following product will be installed to destination: DEC AXPVMS DECNET_OSI V8.3 DISK$XBAJ:[VMS$COMMON.] Portion done: 0%...10%...20%...30%...40%...50%...80%...90%...100% 3-12 Installing DECnet-Plus for OpenVMS Installing DECnet-Plus for OpenVMS DECnet-Plus Using the POLYCENTER Software Installation Utility The following product has been installed: DEC AXPVMS DECNET_OSI V8.3 Layered Product $ 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 base components product you want to install. If you want to take the installation defaults, press Return. If you want to select each optional DECnet-Plus base component (for example, DECdns Server), 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.3.3 DECnet-Plus for OpenVMS VAX Installation Dialog To start the installation, follow these steps: 1. Log in to the SYSTEM account. 2. Mount the Software Products Library media CD-ROM, locate the DECnet-Plus distribution directory, and define the PCSI$SOURCE logical name to reference the directory. See Section 1.1 for information about locating the distribution kit. 3. Enter the following command: $ product install DECnet_OSI For a description of all the features you can request when starting an installation (such as purging files and using a product configuration file), refer to DCL help for the product install command. The actual kit location may change with new releases. See Section 1.1 for information about locating the distribution kit. Installing DECnet-Plus for OpenVMS 3-13 Installing DECnet-Plus for OpenVMS 3.3 Installing DECnet-Plus Using the POLYCENTER Software Installation Utility 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. The following product has been selected: DEC VAXVMS DECnet_OSI V7.3 Layered Product 1 Do you want to continue? [YES] Configuration phase starting ... You will be asked to choose options, if any, for each selected product and for any products that may be installed to satisfy software dependency requirements. DEC VAXVMS DECnet_OSI V7.3: DECnet-Plus V7.3 for OpenVMS VAX Copyright 2004 Hewlett-Packard Development Company, L.P. Hewlett-Packard Company This product requires one of two PAKS: DVNETEND or DVNETRTG. 2 Do you want the defaults for all options? [YES] NO DEC VAXVMS VMS V7.3 * Configuration options for this referenced product cannot * be changed now because the product is already installed. * (You can use PRODUCT RECONFIGURE later to change options.) VAX P.S.I. or P.S.I. Access software [NO]: NO VAX Wide Area Device Drivers [NO]: NO DECdns Server software [NO] NO DECdts Server software [NO] NO 3 Do you want to review the options? [NO] YES DEC VAXVMS DECnet_OSI V7.3: DECnet-Plus V7.3 for OpenVMS VAX DEC VAXVMS VMS V7.3 [Installed] 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.3 3-14 Installing DECnet-Plus for OpenVMS Installing DECnet-Plus for OpenVMS DECnet-Plus Using the POLYCENTER Software Installation Utility Portion Done: 0%...10%...20%...30%...40%...50%...80%...90%...100% The following product has been installed: DEC VAXVMS DECnet_OSI V7.3 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 base components product you want to install. If you want to take the installation defaults, press Return. If you want to select each optional DECnet-Plus base component (for example, VAX P.S.I.), 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.4 Rights Identifiers Added to the System During the final phase of the installation process, several rights identifiers are created in the rights identifiers database. If you are installing from the system console and have the Audit Server properly enabled, it alerts you as these rights are added. In addition, the NET$MANAGE rights identifier is granted to the SYSTEM account. Table 3-2 lists the rights identifiers added during the installation. See the "Managing Network Security" chapter in the HP DECnet-Plus for OpenVMS Network Management manual for more information about these rights identifiers. Table_3-2_Rights_Identifiers_______________________________ Rights_Identifier_____Description__________________________ NET$DECLAREOBJECT Declares an application (continued on next page) Installing DECnet-Plus for OpenVMS 3-15 Installing DECnet-Plus for OpenVMS 3.4 Rights Identifiers Added to the System Table_3-2_(Cont.)_Rights_Identifiers_______________________ Rights_Identifier_____Description__________________________ NET$DECNETACCESS Gives $IPC users access to the network in the absence of the NETMBX privilege NET$DIAGNOSE Permits use of network diagnostics NET$EXAMINE Permits display of the attributes of an entity NET$MANAGE Permits display, creation, or modification of an entity NET$POSTEVENT Permits posting of events NET$REGISTERDNSOBJECT Permits registration or deregistration of a DECdns object NET$SECURITY Permits setting a user name for session control or session control application NET$TRACEALL Permits tracing of entire messages on a local node NET$TRACEALLREMOTE Permits tracing of entire messages on a remote node NET$TRACEHEADERS Permits tracing of message headers on a local node NET$TRACEHEADERSREMOTEPermits tracing of message headers on ______________________a_remote_node________________________ 3.5 Files Installed on the System The DECnet-Plus installation procedure installs a number of files on your system. To list the files, enter one of the following commands (see also Appendix A): For OpenVMS I64 systems: $ product show object /product=decnet_plus For OpenVMS Alpha and OpenVMS VAX systems: $ product show object /product=decnet_osi 3-16 Installing DECnet-Plus for OpenVMS Installing DECnet-Plus for OpenVMS 3.6 Rebooting the System 3.6 Rebooting the System After completing the installation of the DECnet-Plus for OpenVMS software, you must reboot your system before beginning the configuration process. Because the system has not been configured yet, you may see the following messages during system startup: Copyright 2006 Hewlett-Packard Development Company, L.P. %NET$STARTUP-W-NONETCONFIG, this node has not been configured to run DECnet-Plus for OpenVMS use SYS$MANAGER:NET$CONFIGURE.COM if you wish to configure DECnet %NET$STARTUP-I-OPERSTATUS, DECnet-Plus for OpenVMS operational status is OFF Proceed to Chapter 4 for information about selecting the configuration option appropriate for your system. Installing DECnet-Plus for OpenVMS 3-17 Part II _________________________________________________________________ Configuring DECnet-Plus for OpenVMS Part II provides help to determine which configuration option to use: FAST, BASIC, or ADVANCED. It describes using each of the configuration options to configure a new DECnet-Plus node. It also discusses using the BASIC or ADVANCED configuration option to modify an existing configuration. It contains the following chapters: o Chapter 4 - Configuration Options o Chapter 5 - Using the FAST Configuration Option o Chapter 6 - Using the BASIC and ADVANCED Configuration Options o Chapter 7 - Modifying a Current Configuration 4 _________________________________________________________________ Configuration Options This chapter explains the three configuration options you can use to configure your system for the HP DECnet-Plus for OpenVMS software. These configuration options enable you to configure the DECnet-Plus for OpenVMS base components so that the system becomes a DECnet-Plus node 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 (see Chapter 5) The FAST configuration option allows you to quickly upgrade a non-clustered system from DECnet Phase IV to DECnet Phase V. o BASIC configuration option (see Chapter 6) The BASIC configuration option 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 (see Chapter 6) The ADVANCED configuration option 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.7.4 for a list of account privileges you need to run net$configure. Configuration Options 4-1 Configuration Options 4.1 Choosing an Initial Configuration Option 4.1 Choosing an Initial 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. 4-2 Configuration Options Configuration Options 4.1 Choosing an Initial Configuration Option Table_4-1_Choosing_an_Initial_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 an OpenVMS cluster. You are running the configuration procedure for the first time. _________________________________________________________________ BASIC The node is in an OpenVMS cluster. You are upgrading to DECnet-Plus. You need to access a DECdns server for network addresses. You have only 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 DECnet over TCP/IP (RFC 1859) or OSI applications over TCP/IP (RFC 1006). 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 (to control the interpretation of address structuring). You want to use integrated mode routing. _________________________________________________________________ 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. (continued on next page) Configuration Options 4-3 Configuration Options 4.1 Choosing an Initial Configuration Option Table_4-1_(Cont.)_Choosing_an_Initial_Configuration_Option_______ Option..._Choose_if...___________________________________________ 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 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-4 Configuration Options Configuration Options 4.2 How to Run NET$CONFIGURE 4.2 How to Run NET$CONFIGURE The net$configure procedure configures the DECnet-Plus software. This command creates or modifies the Network Control Language (NCL) startup scripts required to run DECnet-Plus on your node. The net$configure procedure is an interactive procedure that displays a series of questions. After each question, the default response, if there is one, appears in brackets ([ ]). 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/Z. To invoke net$configure with the BASIC option, enter the following: $ @sys$manager:net$configure basic To invoke net$configure with the ADVANCED option, enter the following: $ @sys$manager:net$configure advanced If you execute net$configure 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 option. However, the FAST configuration option can only be run once on a system, and after that the BASIC Configuration Options 4-5 Configuration Options 4.2 How to Run NET$CONFIGURE configuration option automatically becomes the default. ______________________________________________________ 4.2.1 Local and Global Symbols The net$configure procedure deletes all of your local and global symbols at the beginning of the procedure in order to free the symbol table. This action is required because net$configure creates and uses a large number of symbols. If the symbols were not deleted at the beginning of the procedure, net$configure could run out of symbol table space to use while configuring the system. In most cases, the configuration procedure restores your symbols as it exits. 4.2.2 Running the Procedure from Different Processes Although net$configure 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 HP DECnet-Plus for OpenVMS base components using the FAST configuration option so that the system becomes a DECnet-Plus end node on a DECnet-Plus network. ________________________ Note ________________________ If you have already run the FAST configuration procedure once on your system, the configuration procedure automatically defaults to the BASIC configuration option. ______________________________________________________ 5.1 Invoking the FAST Configuration Option To invoke the net$configure procedure using the FAST configuration option, enter the following command: $ @sys$manager:net$configure The procedure starts: Copyright 2006 Hewlett-Packard Development Company, L.P. 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 *** Not supported on cluster nodes. 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. The procedure also creates several accounts for the standard DECnet-Plus applications. (Note that, in the interest of clarity, several AUDIT$SERVER-related OPCOM messages related to this account creation and modification process have been omitted from this example.) %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 %NET$CONFIGURE-I-MAKEACCOUNT, this procedure creates user account VPM$SERVER %NET$CONFIGURE-I-MAKEACCOUNT, this procedure creates user account MIRRO$SERVER The procedure continues by displaying the current system configuration and asking if you want to apply the configuration: 5-2 Using the FAST Configuration Option Using the FAST Configuration Option 5.1 Invoking the FAST Configuration Option Summary of Configuration Node Information: Directory Services Chosen: LOCAL Primary Directory Service: LOCAL Node Synonym: ASHFLD Phase IV Address: 4.260 Phase IV Prefix: 49:: Session Control Address Update Interval: 10 Routing Node Type: ENDNODE Autoconfiguration of Network Addresses: Enabled Routing ESHello Timer: 600 Routing ES Cache Size: 512 Device Information: Device: EWA (TULIP): Data Link name: EWA-0 Routing Circuit Name: EWA-0 Transport Information: NSP Transport: Configured Maximum number of logical links: 200 Maximum Transmit and Receive Window: 20 Maximum Receive Buffers: 4000 Flow Control Policy: Segment Flow Control 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 option. If you answer YES, the procedure displays the following message: %NET$CONFIGURE-I-CHECKSUM, checksumming NCL management scripts The procedure then asks if you want to start the network: * Do you want to start the network? [YES] : Using the FAST Configuration Option 5-3 Using the FAST Configuration Option 5.1 Invoking the FAST Configuration Option 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 warning: ******************************************************************** 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. ******************************************************************** HP recommends that you answer YES and start the network. If you choose to start the network, the procedure displays information similar to the following (note that not all net$startup messages are shown and that OPCOM messages have been omitted): Copyright 2006 Hewlett-Packard Development Company, L.P. %NET-I-LOADED, executive image LES$LES_V30.EXE loaded %NET-I-LOADED, executive image NET$ALIAS.EXE loaded %NET-I-LOADED, executive image NET$SESSION_CONTROL.EXE loaded . . . %NET$STARTUP-I-EXECUTESCRIPT, executing NCL script SYS$SYSROOT:[SYSMGR]NET$NODE_STARTUP.NCL %NET$STARTUP-I-EXECUTESCRIPT, executing NCL script SYS$SYSROOT:[SYSMGR]NET$CSMACD_STARTUP.NCL . . . %NET$STARTUP-I-OPERSTATUS, DECnet-Plus for OpenVMS operational status is RUNNING-MAJOR Directory Service: Phase IV database 5-4 Using the FAST Configuration Option Using the FAST Configuration Option 5.1 Invoking the FAST Configuration Option Exporting node name information using: * ASHFLD Number of nodes exported: 1 Directory Service: Local name file Updating nodes listed in SYS$MANAGER:NET$PHASEIV_NODES.DAT ASHFLD Number of nodes registered: 1 Number of nodes modified: 0 %NET$CONFIGURE-I-CONVERTNODEDB, converted the Phase IV node database %NET$CONFIGURE-I-NODERENAMED, node successfully renamed to LOCAL:.ASHFLD %NET$CONFIGURE-I-FLUSHCACHE, flushing selected cache entries Copyright 2006 Hewlett-Packard Development Company, L.P. %NET$STARTUP-I-STARTPROCESS, starting process EVD %NET$STARTUP-I-EXECUTESCRIPT, executing NCL script SYS$SYSROOT:[SYSMGR]NET$EVENT_STARTUP.NCL . . . %NET$STARTUP-I-OPERSTATUS, DECnet-Plus for OpenVMS operational status is RUNNING-ALL %NET$CONFIGURE-I-CONFIGCOMPLETED, DECnet-Plus for OpenVMS configuration completed $ You have just completed the initial configuration of DECnet-Plus. It should now be operational as an end node on the network. See Figure 3-1 or Figure 3-2 to determine your next step. According to the flowcharts, you have just completed configuring DECnet-Plus. 5.2 Modifying 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 startup scripts that you can use to modify the system's configuration. See Chapter 7 for information about running the net$configure BASIC or ADVANCED options to modify your DECnet-Plus configuration. Using the FAST Configuration Option 5-5 6 _________________________________________________________________ Using the BASIC and ADVANCED Configuration Options This chapter describes the BASIC and ADVANCED options of the net$configure.com procedure. Most sections begin with a general explanation of the configuration dialog discussed in the section. When the configuration dialog is common to both options, no special presentation is used. BASIC If a portion of the configuration dialog description is unique to the BASIC option, the description is preceded by a BASIC subheading as shown here. ADVANCED If a portion of the configuration dialog description is unique to the ADVANCED option, the description is preceded by an ADVANCED subheading as shown here. BASIC and ADVANCED In certain rare cases, the BASIC and ADVANCED subheading is used to denote that the description is common to both options. 6.1 Invoking the Configuration Procedure Begin by invoking the configuration procedure. BASIC To invoke the net$configure procedure using the BASIC configuration option, enter the following command: $ @sys$manager:net$configure basic ADVANCED To invoke the net$configure procedure using the ADVANCED configuration option, enter the following command: $ @sys$manager:net$configure advanced Using the BASIC and ADVANCED Configuration Options 6-1 Using the BASIC and ADVANCED Configuration Options 6.2 Opening Messages 6.2 Opening Messages The procedure prints an opening message dependent on the configuration option you choose. BASIC Copyright 2006 Hewlett-Packard Development Company, L.P. 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 ADVANCED Copyright 2006 Hewlett-Packard Development Company, L.P. 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 BASIC and ADVANCED If the procedure detects that the DECnet-Plus software has not been properly installed, it displays the following warning: 6-2 Using the BASIC and ADVANCED Configuration Options Using the BASIC and ADVANCED Configuration Options 6.2 Opening Messages The base DECnet system components are not yet properly loaded. DECnet cannot be started until the DECnet software has been successfully installed and the system has been rebooted. NET$CONFIGURE may fail if you answer YES to the next question. That is because it may be necessary to start the network to establish certain configurations. Hewlett-Packard recommends that you reboot before attempting to configure the network. Next, the procedure asks if you want to proceed with the configuration. * Do you want to continue? [YES] : Press Return to continue with the configuration. The procedure now checks for the privileges and rights identifiers required to run the net$configure procedure. For a list of required privileges and rights identifiers, see Section 1.7.4. If the procedure finds insufficient process privileges, it displays the following messages and exits: %NET$CONFIGURE-E-NOREQPRIV, privilege-list privileges are required %NET$CONFIGURE-E-NOPRIV, insufficient privileges to run this procedure. If the procedure finds insufficient rights identifiers, it displays the following messages and exits: NET$CONFIGURE-E-NOREQRIGHTSID, rights id rights-identifier not granted %NET$CONFIGURE-E-NORIGHTSID, insufficient rights identifiers to run this procedure If you have the required privileges and rights identifiers and if this is the first time that you have run the configuration procedure, the procedure informs you that you are configuring your DECnet-Plus system for the first time: %NET$CONFIGURE-I-SETUPNEW, setting up for new configuration Now you will be asked a few questions. If you need more information to answer a question, you can type ? at the prompts, or consult the DECnet-Plus for OpenVMS Installation and Configuration guide. To configure DECnet, you need to know your node's full name and network address(es). Please review the Installation and Configuration guide, and the checklists in particular, before continuing. Using the BASIC and ADVANCED Configuration Options 6-3 Using the BASIC and ADVANCED Configuration Options 6.3 Specifying Phase IV Conversion Options 6.3 Specifying Phase IV Conversion Options If a Phase IV database exists on the system, the procedure displays the following a message and asks if you want to convert the database: %NET$CONFIGURE-I-PHASEIVDATA, Phase IV DECnet database found A Phase IV database exists on your system. You have the option of using the existing Phase IV database to generate the 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 will configure the system based on your answers to the configuration questions. * Do you want to convert Phase IV databases? [YES] : If you answer NO, the net$configure procedure does not use the system's existing Phase IV database to generate the NCL startup scripts and proceeds to ask all the configuration questions. Proceed to Section 6.4. If you answer YES, the net$configure procedure uses the system's existing Phase IV database to generate the NCL startup scripts and configure the system. The procedure asks the following question to determine the Phase IV prefix to use during the conversion: * Enter Phase IV Prefix [49::] : Usually, when a Phase IV database is found, a Phase IV local node name database is also found. The procedure continues by asking if you want to convert the Phase IV local node name database: You may convert your Phase IV node database to a local node name database. This will provide node name translation if you opt to use LOCAL in the list of directory services to be used on this system. This is unnecessary if you do not intend to include LOCAL in your directory service search list. * Do you want to convert the Phase IV node name database? [YES] : Answer YES if you want the configuration procedure to use the entries in the existing Phase IV node name database to generate a Phase V Local namespace database. (See Section 6.4.1 for information about directory services and the Local namespace.) Answer NO if you do not want to convert the database. 6-4 Using the BASIC and ADVANCED Configuration Options Using the BASIC and ADVANCED Configuration Options 6.3 Specifying Phase IV Conversion Options The procedure converts the Phase IV databases immediately. However, the conversion of the Phase IV node name database is delayed until the namespace modification section (see Section 6.16). The procedure indicates that it has successfully converted the Phase IV databases with the following message: %NET$CONFIGURE-I-PHASEIVCMPL, Phase IV database conversion complete ________________________ Note ________________________ The conversion process enables all FDDI and CSMA- CD stations found in the Phase IV configuration, regardless of their previous line states. ______________________________________________________ 6.4 Configuring Node and Session Control Information The process for configuring node and session control information consists of the following items: o Directory name services o Node full names o Node synonym o Naming cache timeout interval o Session control address update interval o Naming cache checkpoint interval If you have installed the DECdns Server option during the DECnet-Plus installation process, the procedure begins by informing you that the DECdns server startup file is being renamed and that you must configure the node as a DECdns clerk before you can configure the node as a DECdns server: A SYS$STARTUP:DNS$SERVER_STARTUP.COM file has been located. This file is being renamed because the node must be configured as a DNS clerk before it can be re-configured as a DNS server. After the node has been configured as a DNS clerk, you may choose to re-run NET$CONFIGURE Option 2 to rename the node into a DNS server. Using the BASIC and ADVANCED Configuration Options 6-5 Using the BASIC and ADVANCED Configuration Options 6.4 Configuring Node and Session Control Information Once you have configured the node as a DECdns clerk, see Section 7.6.5 for an example of converting the node from a DECdns clerk to a DECdns server. 6.4.1 Specifying 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. o DECdns - The HP DECnet-Plus Distributed Name Service, a distributed, global name service. o Domain Name System - The Domain Name System (DNS/BIND), a global name service for the storage of IP addresses. The sections that follow give a short introduction to each of the name services. For more information on name services, refer to the DECnet-Plus Planning Guide. 6.4.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 actual number of nodes that the Local namespace can hold depends on the space available on your system. 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. 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:.ma.ashfld and local:.ashfld. Unlike DECdns, the Local namespace does not employ backtranslation directories for address-to-node-name translation. 6-6 Using the BASIC and ADVANCED Configuration Options Using the BASIC and ADVANCED Configuration Options 6.4 Configuring Node and Session Control Information 6.4.1.2 The HP DECnet-Plus 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, such as the resource's network address, for DECdns to store. Users then need to remember only the name, and DECdns acts as a lookup service, providing the rest of the data when necessary. The following are typical node full names properly formatted for the DECdns namespace: XYZ_CORP:.usa.ma.ashfld and CMP:.accounting.recv.paul. 6.4.1.3 The Domain Name System The Domain Name System (DNS/BIND) is supported for storage of IP addresses. Refer to your BIND server documentation for specific installation and configuration instructions. For a list of supported vendors, see the DECnet-Plus for OpenVMS Software Product Description (SPD). Any properly constructed DNS/BIND node name is supported by DECnet-Plus. DECnet-Plus recognizes that when a node full name begins with DOMAIN:, information for that node is stored in a DNS/BIND server. In most cases, the configuration procedure also accepts fully-qualified host names for the node's full name. The following are typical node full names properly formatted for the DOMAIN namespace: DOMAIN:ashfld.ma.com. and ashfld.ma.com. 6.4.1.4 The Name Service Search Path The name service search path applies systemwide and allows DECnet-Plus to search a list of name services in a predetermined order when looking up names or addressing information. The search path includes naming templates that tell DECnet-Plus how to interpret any abbreviated node names entered by users. The ordering of the name services is very important. The first name service listed is the primary name service to use on the system. The primary name service is the first choice used when looking up names and addressing information. The remaining name services listed are the secondary name services used on the system. Using the BASIC and ADVANCED Configuration Options 6-7 Using the BASIC and ADVANCED Configuration Options 6.4 Configuring Node and Session Control Information The search path contains a list of name service keywords, each followed by a naming template that specifies a defaulting rule so users can enter shorter node names. To create the node's name service search path, begin by entering an ordered list of the directory name services you want to use on the system. At the prompt, you can choose the following name services for the system: LOCAL, DECDNS, and DOMAIN. If you enter more than one name service, separate the name services with commas. * Enter the directory services to use on the system [DECdns,Local,Domain] : For example, entering DECDNS,LOCAL,DOMAIN at the prompt, 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. ________________________ Notes ________________________ If you intend to make this node a DECdns server, you must first configure the node with only the Local name service or as a clerk in an existing DECdns namespace. After completing the initial configuration, reinvoke the net$configure procedure and select Option 2 - Change Naming Information. At this point, net$configure will give you the option of converting the node to a DECdns server. All members in a cluster should have identical name service search paths configured. This helps to ensure that nodes are recognized in the various services you have identified. For example, if you receive mail on one node in the cluster, the "From" node name may be LOCAL:.NODE::SMITH. If you attempt to reply to this node from a node in the cluster that does not have the Local namespace configured, the system would indicate that there is no such node. ______________________________________________________ 6-8 Using the BASIC and ADVANCED Configuration Options Using the BASIC and ADVANCED Configuration Options 6.4 Configuring Node and Session Control Information 6.4.2 Specifying Node Full Names After requesting the ordered list of directory name services, the configuration procedure prompts you for one or more node full names. 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. Use the following guidelines for selecting a node full name: o For DECdns and Local, the node full name has the format NamespaceNickname:[.DirectoryPath].NodeObject. Note that the name must begin with the namespace nickname and a colon (:). The nickname for the Local namespace is always LOCAL: (or local:). The namespace nickname LOCAL is reserved for the Local namespace and cannot be used for a DECdns namespace. The namespace nickname and the node object cannot be null strings. o For DECdns and Local, the directory path must begin with a dot (.). o The full name can be up to 512 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 HP DECnet-Plus for OpenVMS DECdns Management manual. o For DNS/BIND, enter a fully qualified IP host name. The following are some examples of suitable node full names: Local namespace - LOCAL:.TomThumb DECdns - ACME:.wabbit.Elmer Domain - elmer.wabbit.acme.edu ________________________ Note ________________________ If you plan to use a Local namespace and you are converting a Phase IV system to DECnet-Plus, HP Using the BASIC and ADVANCED Configuration Options 6-9 Using the BASIC and ADVANCED Configuration Options 6.4 Configuring Node and Session Control Information 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. The prompts used by the configuration procedure depend on the directory name services you entered. For example, if you enter LOCAL,DECDNS,DOMAIN at the directory services prompt, the configuration dialog asks for a Local full name, a DECdns 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.4.3 Specifying the 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 are transitioning from 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. 6-10 Using the BASIC and ADVANCED Configuration Options Using the BASIC and ADVANCED Configuration Options 6.4 Configuring Node and Session Control Information 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 information on node synonym directories, see Section B.2. 6.4.4 Specifying the Naming Cache Timeout Value A naming cache is used to improve the performance of node name to address resolution. This naming cache supersedes the DECdns cache in older DECnet-Plus versions 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 will continue to use the DECdns cache instead of the naming cache. The naming cache includes a mechanism to time out old entries. In this way, these entries are refreshed periodically to reflect the actual network environment. BASIC The BASIC option sets the naming cache timeout value to the default value of 30 days (30-00:00:00). ADVANCED The ADVANCED option prompts for the naming cache value: * Naming cache timeout value? [30-00:00:00] : To choose the default value of 30 days, press Return. Otherwise, enter any legal OpenVMS delta time value. Using the BASIC and ADVANCED Configuration Options 6-11 Using the BASIC and ADVANCED Configuration Options 6.4 Configuring Node and Session Control Information 6.4.5 Specifying the Session Control Address Update Interval The session control address update interval is the time, in seconds, between updates of local tower address information. BASIC The BASIC option sets the session control address update interval to the default value of 10 seconds. ADVANCED The ADVANCED option prompts for the session control address update interval: * Session Control Address Update Interval ? [10] : To choose the default value of ten seconds, press Return. Otherwise, enter an interval value in seconds and press Return. 6.4.6 Specifying the 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. BASIC The BASIC option sets the naming cache checkpoint interval to the default value of 8 hours. ADVANCED The ADVANCED option prompts for the naming cache checkpoint interval: * Naming cache checkpoint interval? [08:00:00] : To choose the default value of eight hours, press Return. Otherwise, enter any legal OpenVMS delta time value. 6-12 Using the BASIC and ADVANCED Configuration Options Using the BASIC and ADVANCED Configuration Options 6.5 Configuring Routing Parameters 6.5 Configuring Routing Parameters The process for configuring routing parameters consists of the following items: o Node type (end node or router) o Router information - Router type - Maximum path splits - Phase IV maximum address - Phase IV maximum area o Phase IV address o Phase IV prefix o End node information - Network addresses - DNA address format - Routing mode o Default ES Hello Timer o ES Cache Size 6.5.1 Specifying the Node Type DECnet-Plus for OpenVMS allows an OpenVMS system to run integrated IS-IS, thus providing host-based routing functionality. Answer ROUTER if you want this system to support the host-based routing functionality. If you answer ROUTER, you must have the extended function license (see Section 1.6) for the host-based routing software to function. Answer ENDNODE if this system will depend on other nodes to provide routing. * What type of node (Endnode or Router)? [ENDNODE] : To configure an end node system, press Return. Otherwise, enter the node type. Using the BASIC and ADVANCED Configuration Options 6-13 Using the BASIC and ADVANCED Configuration Options 6.5 Configuring Routing Parameters 6.5.2 Specifying Router Information This section only applies if you chose to configure your system as a router. 6.5.2.1 Routing Type A DECnet-Plus router can provide intra-area routing capability (known as level 1 routing) or inter-area level routing capability (known as level 2 routing). * Type of routing node (L1 or L2)? [L1] : To configure a level 1 router, press Return. Otherwise, enter L2 for level 2 routing capability. ________________________ Note ________________________ Immediately preceding this question, the procedure displays an informational message explaining that net$configure always generates a router that uses the routing vector protocol: NET$CONFIGURE will assume that the MANUAL L1 ALGORITHM and the MANUAL L2 ALGORITHM (if present) will be ROUTING VECTOR. If LINK STATE is to be designated as the preferred routing algorithm at either level, the DCL command file SYS$MANAGER:ISIS$CONFIGURE.COM must be invoked AFTER this procedure to correctly configure the NET$ROUTING_STARTUP.NCL. For information about using the isis$configure procedure to configure a router that uses the link state routing protocol, see Appendix D. ______________________________________________________ 6.5.2.2 Maximum Path Splits A routing node may use multiple paths of equal cost to route traffic. The answer to this question specifies the maximum number of these paths between which the traffic is split. BASIC The BASIC option sets maximum path splits to the default value of 2. 6-14 Using the BASIC and ADVANCED Configuration Options Using the BASIC and ADVANCED Configuration Options 6.5 Configuring Routing Parameters ADVANCED The ADVANCED option prompts for the maximum path splits value: * Maximum path splits [2] : To choose the default value of 2, press Return. Otherwise, enter a number between 1 and 32. 6.5.2.3 Phase IV Maximum Address and Maximum Area The next two questions control which Phase IV packets are forwarded by a router. The Phase IV maximum address characteristic prohibits Phase IV packet forwarding to any node with a higher address than the specified value. The Phase IV maximum area characteristic prohibits Phase IV packet forwarding to any area with a higher area number than the specified value. The Phase IV maximum area question is asked only for level 2 routers. HP recommends that both defaults be taken to prevent any unintended packet loss. BASIC The BASIC option sets the Phase IV maximum address to the default value of 1023. If the system is a level 2 router, the BASIC option sets Phase IV maximum area to the default value of 63. ADVANCED The ADVANCED option prompts for the Phase IV maximum address value: * PhaseIV Maximum Address [1023] : To choose the default value of 1023, press Return. Otherwise, enter a number between 1 and 1023. If the router is a level 2 router, the ADVANCED option also prompts for the Phase IV maximum area value: * PhaseIV Maximum Area [63] : To choose the default value of 63, press Return. Otherwise, enter a number between 1 and 63. Using the BASIC and ADVANCED Configuration Options 6-15 Using the BASIC and ADVANCED Configuration Options 6.5 Configuring Routing Parameters 6.5.3 Specifying a DECnet Phase IV Address If you want your system to communicate with Phase IV nodes, you must specify a Phase IV address and a Phase IV prefix. DECnet-Plus systems reference all network addresses (including Phase IV addresses) using the OSI Network Service Access Point (NSAP) address formats. The Phase IV address and a Phase IV prefix are used to construct a complete NSAP address. A DECnet Phase IV-compatible address is a DECnet-Plus address, in the form area-number.node-number, 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 does 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.5.4 Specifying a Phase IV Prefix All nodes within a single addressing domain contain the same initial domain part (IDP) in their network addresses. 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. ________________________ Note ________________________ 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 is 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 DECnet-Plus Planning Guide contains a detailed 6-16 Using the BASIC and ADVANCED Configuration Options Using the BASIC and ADVANCED Configuration Options 6.5 Configuring Routing Parameters description of how to construct an IDP and how to apply to a standards organization for an IDP. ______________________________________________________ BASIC The BASIC option sets the Phase IV prefix to its default value of 49::. If you do not enter a Phase IV-compatible address, the BASIC option does not assign a Phase IV prefix value. ADVANCED If you entered a Phase IV-compatible address, the ADVANCED option prompts for the Phase IV prefix value: * Enter Phase IV Prefix [49::] : To choose the default value of 49::, press Return. Otherwise, enter a valid IDP value. 6.5.5 Specifying End Node Information This section applies only if you chose to configure your system as an end node. 6.5.5.1 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 network. 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. Using the BASIC and ADVANCED Configuration Options 6-17 Using the BASIC and ADVANCED Configuration Options 6.5 Configuring Routing Parameters BASIC The BASIC option autoconfigures one network address for you. ADVANCED The ADVANCED option prompts you for the method to create network addresses: * Autoconfigure network addresses? [YES] : There are two ways to configure NETs: by autoconfiguring addresses or by manually configuring addresses. To choose to autoconfigure network addresses, press Return. Otherwise, enter NO. The two methods are described in detail in the following paragraphs. Autoconfiguring Network Addresses Answer YES to have your system autoconfigure its network address. To use this option, you must be using only Phase V (OSI) addressing. If you have an OSI router from a supplier other than HP 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 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. 6-18 Using the BASIC and ADVANCED Configuration Options Using the BASIC and ADVANCED Configuration Options 6.5 Configuring Routing Parameters Manually Configuring Addresses If you answer NO, the procedure prompts you to manually enter network entity titles. If you configured a DECnet Phase IV-compatible address the procedure precedes the prompt with a message informing you that it is including that address in the list of NETs: %NET$CONFIGURE-I-PHASEIVNETINCL, the Phase IV N.E.T. will be included: phaseiv-net * Enter Manual Network Entity Titles [ ]: You can assign a maximum of three network addresses to the system, including the Phase IV-compatible network address. If you enter multiple addresses, separate the addresses using commas. 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 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 DECnet-Plus Planning Guide. Using the BASIC and ADVANCED Configuration Options 6-19 Using the BASIC and ADVANCED Configuration Options 6.5 Configuring Routing Parameters 6.5.5.2 DNA Address Format 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. BASIC The BASIC option sets the routing characteristic DNA address format to TRUE. ADVANCED The ADVANCED option prompts you for the DNA address format setting: * DNA Address Format [TRUE] : To choose the default value of TRUE, press Return. Otherwise, enter FALSE, and enter at least one manual network entity title. See Section 6.5.5.1. 6.5.5.3 Segregated Mode Routing and Integrated Mode Routing You have the option of using integrated mode routing or segregated mode routing. Integrated mode routing - 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 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. 6-20 Using the BASIC and ADVANCED Configuration Options Using the BASIC and ADVANCED Configuration Options 6.5 Configuring Routing Parameters 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 routers that do not support the technique of translating DECnet Phase V addresses to DECnet Phase IV, you must 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 routers cannot perform Phase-IV-to-Phase-V or Phase-V-to-Phase-IV packet conversions. ________________________ Note ________________________ If your OpenVMS system is using a cluster alias, you must use integrated mode. ______________________________________________________ BASIC The BASIC option selects the integrated routing mode. ADVANCED The ADVANCED option prompts you for the routing mode setting: * Do you want to use segregated mode routing? [NO] : To choose the default value of integrated routing mode, press Return. Otherwise, enter YES to choose segregated routing mode. Using the BASIC and ADVANCED Configuration Options 6-21 Using the BASIC and ADVANCED Configuration Options 6.5 Configuring Routing Parameters 6.5.6 Specifying the Default ES Hello Timer The default ES Hello timer value determines the interval, in seconds, that the end system (ES) uses when sending out its Hello messages. This interval multiplied by 3 is the amount of time the other end of a routing adjacency waits before determining that this system is no longer able to accept connections. BASIC The BASIC option sets the ES Hello timer value to 600. ADVANCED The ADVANCED option prompts you for the ES Hello timer setting: * Routing Default ES Hello Timer? [600] : To select the default of 600, press Return. Otherwise, choose your own value and press Return. 6.5.7 Specifying the ES Cache Size The routing ES Cache Size attribute specifies the maximum number of entries in the ES cache. BASIC The BASIC option sets the ES cache size value to 512. ADVANCED The ADVANCED option prompts you for the ES cache size setting: * Routing ES Cache Size? [512] : To select the default of 512, press Return. Otherwise, choose your own value and press Return. 6.6 Configuring Devices The net$configure procedure checks for network devices on the system that are supported by net$configure and then configures them. 6-22 Using the BASIC and ADVANCED Configuration Options Using the BASIC and ADVANCED Configuration Options 6.6 Configuring Devices 6.6.1 Configuring WANDD Device Support The net$configure procedure begins device configuration by checking to see if the Wide Area Network Device Drivers (WANDD) software has been installed but not configured. The WANDD software provides synchronous device support for DECnet-Plus. If it finds the WANDD configuration file (sys$startup:wandd$configure.com), it displays a short message and asks if you want to add WANDD devices to your configuration: 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] : To add WANDD devices to your configuration, press Return. To skip over the WANDD device configuration, enter NO and press Return. If you select WANDD device configuration, the net$configure procedure invokes the WANDD configuration file, (sys$startup:wandd$configure.com). The next two sections describe the WANDD configuration dialog on OpenVMS I64 and OpenVMS Alpha systems and on OpenVMS VAX systems. 6.6.1.1 WANDD Device Configuration on OpenVMS I64 and OpenVMS Alpha Systems If you select WANDD device configuration on an OpenVMS I64 or OpenVMS Alpha system, the WANDD configuration procedure displays the following messages and asks the indicated questions: Configuring WANDD... ['?' for HELP] %WANDD$CONFIGURE-I-WANDDNOTCONFIG, WANDD has not been configured. Configure WANDD? [YES] All installed autoconfigurable synchronous device drivers will be configured. However, the built-in serial port will only be configured if you answer "YES" to the next question. Configure built-in serial port as synchronous? [YES] Are you satisfied with your answers? [YES] Using the BASIC and ADVANCED Configuration Options 6-23 Using the BASIC and ADVANCED Configuration Options 6.6 Configuring Devices By default, when the WANDD configuration procedure is called for the first time, the procedure does the following: 1. Loads the appropriate synchronous device drivers which enable connection to a wide area network via a serial port. 2. If the processor supports the built-in serial port (TTA1), a question is displayed asking if you want to configure the port for wide area network use. The built-in serial port supports both asynchronous and synchronous communications. If you elect to configure the built-in port, it will be available for synchronous wide area network communications only. The dialog displays the following text if the port is present but unavailable: The built-in serial port is currently unavailable for synchronous communications. This is possibly because the console has been configured to use it. You are still able to reserve this port for synchronous communications but be aware that it will only be made available when the console is not making use of it. 6.6.1.2 WANDD Device Configuration on OpenVMS VAX Systems If you select WANDD device configuration on an OpenVMS VAX system, the WANDD configuration procedure displays the following messages and asks the indicated questions: This is the Configuration Procedure for the =========================================== VAX Wan Device Drivers for DECnet-Plus for VMS ============================================= The Wide Area Network Datalinks and Drivers are a prerequisite for DECnet-Plus. They also provide synchronous datalinks in systems that do not use DECnet-Plus for networking. Access to DECnet-Plus 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. 6-24 Using the BASIC and ADVANCED Configuration Options Using the BASIC and ADVANCED Configuration Options 6.6 Configuring Devices Do you wish to use WANDRIVER [N] ? 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. 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. 6.6.2 The Configuration Procedure Device Scan After adding the WANDD devices, the net$configure procedure does a complete system device scan: %NET$CONFIGURE-I-SCANCONFIG, scanning device configuration - please wait If no devices are found, the procedure displays a message and asks if you want to perform an autoconfigure operation to create a new set of available devices: %NET$CONFIGURE-W-NODEVICES, no devices found Should devices be autoconfigured? [YES] : Using the BASIC and ADVANCED Configuration Options 6-25 Using the BASIC and ADVANCED Configuration Options 6.6 Configuring Devices If you want to have the procedure autoconfigure devices, press Return. If you enter NO, the configuration procedure continues without autoconfiguring devices. However, if you do not autoconfigure devices, no devices will be available. On OpenVMS I64 and OpenVMS Alpha systems, the autoconfiguration is done using the command mcr sysman io auto. On OpenVMS VAX systems, the autoconfiguration is done using the command mcr sysgen autoconfigure all. 6.6.3 Configuring Asynchronous Data Link Support (OpenVMS VAX Only) Normally, the OpenVMS system controls lines connected to terminal ports, as in interactive logins. You can, however, switch the line so that the DECnet-Plus software can use the line for an asynchronous data link to another system. Asynchronous data links are implemented in software and can be run over any directly connected terminal line that the OpenVMS system supports. The asynchronous protocol provides for a full-duplex data link and can be used for remote asynchronous communications over a telephone line using a modem. Asynchronous data links are not supported for maintenance operations or for controller loopback testing. ________________________ Note ________________________ For more information about asynchronous data link support on VAX systems, see the "Configuring Asynchronous Data Links" appendix in the HP DECnet- Plus for OpenVMS Network Management manual. ______________________________________________________ BASIC The BASIC option does not offer the choice of configuring asynchronous devices. Proceed to Section 6.6.4. ADVANCED The ADVANCED option asks whether you want to configure asynchronous data links: * Do you want asynchronous datalink support? [YES] : Answer NO if you do not want to configure any asynchronous data links. Proceed to Section 6.6.4. 6-26 Using the BASIC and ADVANCED Configuration Options Using the BASIC and ADVANCED Configuration Options 6.6 Configuring Devices If you answer YES, the procedure verifies that the asynchronous device driver (sys$ldr:asydriver.exe) is available. If the file is not found, the procedure displays a warning that you must install the WANDD software: **************************************************************** WARNING The WANDD software is not installed on the system. If you want asynchronous datalink support, make sure that the WANDD software is installed and configured on your system. **************************************************************** The procedure allows you to continue. However, you must install the WANDD software or the data links you configure will be unusable. 6.6.3.1 Static Data Links A static asynchronous data link creates a permanent DECnet link to a single remote node. Two nodes are connected either by a dialup line or by a physical line attached to a terminal port at each end. Before the DECnet connection is made, the terminal line must be converted to a static asynchronous DDCMP line (see Section 6.6.3.3). The procedure begins by asking if you want to configure any static data links: * Do you want to configure static lines? [YES]: Answer NO if you do not want to configure any static asynchronous data links. Proceed to Section 6.6.3.2. If you answer YES, the procedure asks you for the device names of the terminal lines that you want to configure as static asynchronous data links: * Terminal device name (ex: TXA0,TXA2,...)? []: Enter the OpenVMS device names of one or more available terminal lines. If you want to configure multiple devices enter two or more device names separated by commas. The configuration procedure displays the following dialog for each device you enter. 1. First, the procedure checks for the presence of the device. If the procedure is unable to find the indicated Using the BASIC and ADVANCED Configuration Options 6-27 Using the BASIC and ADVANCED Configuration Options 6.6 Configuring Devices terminal device, it displays a warning message and asks if you want to continue: %NET$CONFIGURE-W-NOSUCHDEV, no such device found - device-name Do you want to continue configuring this line? [YES]: Answer NO to quit the configuration of this line. Answer YES if you want to continue. 2. If you answer YES, the procedure continues the device configuration by asking you for the device's line speed: Line speed for TTA0? [2400]: 3. Next, the procedure asks you about the modem control requirements for the device: Will this line require full modem control? [YES]: When all devices in the device list have been configured, the procedure begins the dynamic data link configuration section. 6.6.3.2 Dynamic Data Links A dynamic asynchronous data link provides a temporary DECnet link. A dynamic asynchronous line is normally switched on for network use only for the duration of a dialup connection between two nodes. When the telephone is hung up, the line reverts to being a terminal line. An advantage of dynamic data links is that you can establish connections to different remote nodes at different times. When using a dynamic data link, you can use an explicit line or you can use a floating line. An explicit line is tied to a specific OpenVMS terminal device. A floating line is not tied directly to a specific terminal device. Before the DECnet connection is made, the terminal line must be converted to a dynamic asynchronous DDCMP line (see Section 6.6.3.3). The procedure begins by asking if you want to configure any dynamic data links: Do you want to configure dynamic lines? [YES]: Answer NO if you do not want to configure any dynamic asynchronous data links. Answer YES if you want to configure either explicit or floating dynamic data links. 6-28 Using the BASIC and ADVANCED Configuration Options Using the BASIC and ADVANCED Configuration Options 6.6 Configuring Devices Explicit Dynamic Data Links The procedure then asks if you want to create any explicit dynamic lines: * Do you want to configure explicit dynamic lines? [YES]: Answer NO if you do not want to configure any explicit dynamic asynchronous data links. Proceed to the section entitled "Floating Dynamic Data Links." If you answer YES, the procedure uses the same questions discussed in Section 6.6.3.1 to obtain the list of terminal device names, and then the line speed and modem control requirements of each device. When all devices in the device list have been configured, the procedure proceeds to the floating dynamic data link configuration section. Floating Dynamic Data Links The procedure next asks if you want to create any floating dynamic lines: * Do you want to configure floating dynamic lines? [YES]: Answer NO if you do not want to configure any floating dynamic asynchronous data links. If you answer NO, the procedure asks if you want to configure any more asynchronous data links at this time: * Do you want to configure any more asynch lines? [NO]: Answer YES to return to the static asynchronous lines dialog (see Section 6.6.3.1). If you answer NO, proceed to Section 6.6.4. If you answer YES to the floating dynamic lines question, the procedure begins their configuration. Floating dynamic lines are configured in groups based on line speed and modem control requirements. First, the configuration procedure asks you the line speed and modem control requirements for the data link group using the line speed and modem questions discussed in Section 6.6.3.1: * Line speed for device-name? [2400]: * Will this line require full modem control [YES]: Using the BASIC and ADVANCED Configuration Options 6-29 Using the BASIC and ADVANCED Configuration Options 6.6 Configuring Devices Next, the procedure asks you for the number of floating lines to configure with these characteristics: * Number of floating speed bps control modem ctrl lines? [1]: Enter the number of floating data lines you want to configure with the indicated device characteristics. The procedure then asks if you want to configure another set of floating dynamic lines with different speed and modem characteristics: * Do you want to configure any more floating lines? [YES]: If you answer YES, the procedure asks another series of speed, modem control, and number questions for the next group of floating dynamic lines. Answer NO if you are finished configuring floating dynamic lines. If you answer NO, the procedure asks if you want to configure any more asynchronous data links at this time: * Do you want to configure any more asynch lines? [NO]: Answer YES to return to the static asynchronous lines dialog (see Section 6.6.3.1). If you answer NO, proceed to Section 6.6.4. 6.6.3.3 Preparing the Terminal Lines for DECnet Use The configuration procedure configures all the network entities to support asynchronous data links. However, it does not enable or disable the individual terminal devices themselves. To switch a terminal line to a DECnet line or a DECnet line back to a terminal line, use DCL set commands such as the following: o To switch a terminal line to a static asynchronous line: $ set terminal/protocol=ddcmp device-name o To switch a terminal line to a floating dynamic asynchronous line: $ set terminal/protocol=ddcmp/switch=decnet device-name 6-30 Using the BASIC and ADVANCED Configuration Options Using the BASIC and ADVANCED Configuration Options 6.6 Configuring Devices o To switch a terminal line to an explicit dynamic asynchronous line: $ set terminal/protocol=ddcmp/switch=decnet/manual device-name o To switch a DECnet line back to OpenVMS terminal driver use: $ set terminal/protocol=noddcmp device-name 6.6.4 Configuring Data Links and Routing Circuits You now need to supply names for the data links and routing circuits you have on your system. For HDLC and synchronous links, you also need to select which protocol should be used on the link (HDLC, DDCMP, or NONE). o DDCMP (Digital Data Communications Message Protocol) provides synchronous point-to-point connections and asynchronous static or dynamic point-to-point connections. o HDLC (High-Level Data Link protocol) conforms to ISO standards. HDLC provides synchronous point-to-point connections. o NONE indicates that you do not want DECnet-Plus to configure this line directly. You may still configure this line for X.25 and then configure DECnet over X.25 for the line (see Section 6.6.5 for information about using DECnet over X.25 data links). BASIC The BASIC option automatically configures all available network devices. It uses the default naming conventions for all data links and routing circuits. It also uses built- in defaults for the protocol on all HDLC and synchronous links. ADVANCED The ADVANCED option prompts you for the simple name that you want to use for each data link and routing circuit. For HDLC and synchronous lines, the procedure precedes the link and routing circuit name questions with a question about which protocol should be used on the link (HDLC, DDCMP, or NONE): Using the BASIC and ADVANCED Configuration Options 6-31 Using the BASIC and ADVANCED Configuration Options 6.6 Configuring Devices * Data Link protocol for ZR-0-0 (SSCC) [HDLC] : * Data Link name to use for ZR-0-0 (SSCC)? [HDLC-0] : * Routing Circuit Name for Data Link 'HDLC-0'? [HDLC-0] : The "Data Link name" question can take on several slightly different forms depending on the device being configured. 6.6.4.1 FDDI Large Packet Support For each 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 utilize the bandwidth of FDDI. (A Phase V router on the LAN, preferably on the FDDI, is required before you can enable large packet support.) If you choose not to enable FDDI large packet support on the circuit, the FDDI circuit uses the bandwidth of Carrier Sense, Multiple Access with Collision Detection (CSMA-CD) instead. BASIC The BASIC option automatically selects the CSMA-CD packet size instead of the FDDI large packet size. ADVANCED For each FDDI-type circuit on the system, the ADVANCED option displays the following message and prompt: You have the option of enabling FDDI large packet support on this routing circuit. Note that a Phase V router on the LAN (preferably on the FDDI) is required in order to use FDDI large packet support. * Use large packets on Routing Circuit FDDI-0? [YES] : If you want to enable FDDI large packet support, press Return. Otherwise, answer NO. 6.6.4.2 Circuit Cost and Routing Priority The following applies only if your DECnet-Plus system 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 a level 2 router, the procedure also asks you for the level 2 cost and router priority. 6-32 Using the BASIC and ADVANCED Configuration Options Using the BASIC and ADVANCED Configuration Options 6.6 Configuring Devices 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. BASIC The BASIC option assigns the level 1 and level 2 routing cost based on link type: o Asynchronous data links are assigned a cost of (38400/line-speed) + 48. o Synchronous and HDLC data links are assigned a cost of 20. o All other data links are assigned a cost of 8. The level 1 and level 2 routing priorities are always set to 64. ADVANCED The ADVANCED option prompts you for the routing cost and priority information: * 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] : Press Return to take the defaults or enter you own values. 6.6.4.3 Enabling Phase IV Addressing on Routing Circuits If you previously specified a Phase IV-compatible address for your node in order to communicate with other Phase IV nodes (as in Section 6.5.3), you must specify for each circuit whether you want to enable Phase IV addressing on that circuit. If the node has multiple connections to a LAN, enable Phase IV addressing on only one circuit for that LAN. BASIC The BASIC option enables Phase IV addressing on the first broadcast circuit that the procedure encounters. The device list is structured so that if both FDDI and CSMA-CD circuits are available, Phase IV addressing is allowed on the first FDDI circuit in preference to the first CSMA-CD circuit. Using the BASIC and ADVANCED Configuration Options 6-33 Using the BASIC and ADVANCED Configuration Options 6.6 Configuring Devices If you have multiple broadcast circuits and you are performing a Phase IV migration (that is, you elected to convert the Phase IV database (see Section 6.3), the procedure displays the following information about enabling additional broadcast circuits: NET$CONFIGURE has determined that you have multiple broadcast circuits. Your system has been configured to enable Phase IV addressing on only one of those circuits. When Phase IV addressing is enabled, the datalink MAC address is set according to Phase IV addressing rules (i.e. AA-00-04-00-nn-nn). It is undesirable (and invalid) for more than one circuit using Phase IV addressing to be connected to the same LAN. However, if your circuits are on distinct and separate LANs, and the Phase IV style MAC address is desired on more circuits, you may edit the SYS$MANAGER:NET$ROUTING_STARTUP.NCL script prior to starting your network. For example, you would change the following command: SET NODE 0 ROUTING CIRCUIT SVA-1 ENABLE PHASEIV ADDRESS = FALSE to this in order to enable Phase IV addressing on the circuit: SET NODE 0 ROUTING CIRCUIT SVA-1 ENABLE PHASEIV ADDRESS = TRUE ADVANCED The ADVANCED option prompts you whether you want to enable Phase IV addressing on a circuit: * Enable Phase-IV Addressing on Routing Circuit 'CSMACD-0'? [YES] : Entering YES allows Phase IV messages to be transmitted on that circuit. Answering NO indicates that no Phase IV messages will be transmitted on that circuit. 6.6.5 Configuring DECnet over X.25 If you have configured X.25 for OpenVMS on an I64 or OpenVMS Alpha system or the X.25 functionality provided by DECnet-Plus on an OpenVMS VAX system (formerly known as VAX P.S.I.), the configuration procedure now gives you the option of configuring DECnet-Plus to use any previously configured X.25 data links. 1. The procedure begins by displaying a message indicating that X.25 software has been installed. 6-34 Using the BASIC and ADVANCED Configuration Options Using the BASIC and ADVANCED Configuration Options 6.6 Configuring Devices For an OpenVMS I64 or OpenVMS Alpha system, the procedure displays the following information: X.25 for OpenVMS software has been installed on this system. You have the option of configuring DECnet to run over X.25. For an OpenVMS VAX system, the procedure displays the following information: The VAX P.S.I. software has been installed on this system. You have the option of configuring DECnet over P.S.I. (i.e., configuring DECnet over X.25 or data link mapping). 2. Next, the procedure asks if you want to configure DECnet-Plus to use 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 NO, proceed to Section 6.7. 3. Routing supports four types of X.25 circuits: o A dynamically assigned routing circuit operates over a number of X.25 switched virtual circuits (SVCs), both incoming and outgoing. o A static incoming routing circuit operates over a single incoming X.25 switched virtual circuit (SVC). o A static outgoing routing circuit operates over a single outgoing X.25 switched virtual circuit (SVC). o A permanent routing circuit uses a permanent virtual circuit (PVC) instead of an SVC. The procedure asks you which type of X.25 routing circuit you want to configure: 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 Enter the number for the type of circuit you want. Using the BASIC and ADVANCED Configuration Options 6-35 Using the BASIC and ADVANCED Configuration Options 6.6 Configuring Devices 4. The procedure asks for a name to use for the routing circuit: * Routing Circuit Name to use? [X25-PVC-0] : Specify the simple name you want to use for the routing circuit. The default circuit names are derived from the circuit type (X25-DA-x, X25-IN-x, X25-OUT-x, or X25- PVC-x). You can use the default or you can supply a name (for example, X25-STATICIN-0). 5. All X.25 routing circuits use an X.25 access template to make or accept a network connection. o For a static outgoing (OUT) circuit, the X.25 access template must specify DTE class, destination DTE address, and call data. The X.25 access template can also specify other call characteristics to make the outbound network connection. o For a static incoming (IN) routing circuit, the X.25 access template can specify call characteristics to accept the inbound network connection. o For a dynamically assigned (DA) routing circuit, the X.25 access template must specify DTE class and call data. The X.25 access template can also specify other call characteristics to make the outbound or accept the inbound network connections. Use the appropriate X.25 configuration program to configure X.25 access templates. The procedure asks for a template name to use for the circuit: * Template name? [X25-PVC-0] : Specify the simple name of an X.25 access template. A default name is provided or you may enter your own name (for example, X25-DA-1). 6. Static incoming and dynamically assigned X.25 circuits use an X.25 access filter to receive inbound network connections. o For a static incoming circuit, the X.25 access filter must specify inbound DTE class, sending DTE address, call data value, and call data mask. 6-36 Using the BASIC and ADVANCED Configuration Options Using the BASIC and ADVANCED Configuration Options 6.6 Configuring Devices o For a dynamically assigned circuit, the X.25 access filter must specify inbound DTE class, call data value, and call data mask. Use the appropriate X.25 configuration program to configure X.25 access filters. 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 X.25 access filter. You may accept the default or you may enter your own name (for example, X25-IN-0). 7. If you chose to configure an X.25 dynamic assigned (DA) circuit, the procedure asks if you want to configure any routing circuit reachable addresses: * Do you want to configure any reachable addresses? [NO] : If you answer NO, the procedure omits the remaining questions discussed here. Proceed to Step 8. If you want to configure any routing circuit reachable address entities, answer YES. The procedure displays a series of prompts to request a set of reachable addresses. a. The procedure prompts for the name you want to assign to this set of reachable addresses: * Reachable address name? : Specify the simple name of the reachable address subentity that you want to create (for example, ACCOUNTS_DEPT). b. 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. Using the BASIC and ADVANCED Configuration Options 6-37 Using the BASIC and ADVANCED Configuration Options 6.6 Configuring Devices The procedure asks for the reachable address prefix for this set of reachable addresses: * Reachable address prefix? : Specify the address prefix for this reachable address entity. The address prefix is a string of characters that is the valid beginning of an NSAP (for example, 41:45436192:). The address prefix matches all NSAPs. c. 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. The procedure asks for the reachable address data terminal equipment (DTE) list for this set of reachable addresses: * Reachable address dte list? : 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). d. The procedure then asks if you want to configure 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. The procedure returns you to the reachable address name prompt (Step 7a). 8. 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 X.25 routing circuits. * Configure another X.25 routing circuit for DECnet? [NO] : 6-38 Using the BASIC and ADVANCED Configuration Options Using the BASIC and ADVANCED Configuration Options 6.6 Configuring Devices Press Return if you do not want to configure any other X.25 routing circuits. Answer YES if you want to configure another X.25 routing circuit. The procedure returns you to Step 4. After you complete the configuration of all X.25 routing circuits, the configuration procedure continues with the transport section. 6.7 Configuring Transports Next, the configuration procedure configures the NSP and OSI transports. BASIC The BASIC option configures the NSP and OSI transports using default values. See Section 6.7.1 for the default values for the NSP transport. See Section 6.7.2 for the default values for the OSI transport. ADVANCED The ADVANCED option begins the transport configuration by displaying the following message: You have the option of configuring the NSP and OSI Transports. Configure the NSP Transport if you want the system to communicate with DECnet Phase IV nodes. Configure the OSI Transport if you want the system to communicate with DECnet-Plus nodes; if you want to run DECnet or OSI applications over TCP/IP; or if you plan to install OSI Applications such as OSAK, FTAM, or VT software. _______________________ Warning _______________________ If you do not configure one of the two transports, the procedure issues a warning and asks you to confirm your decision: %NET$CONFIGURE-W-NOTRANSPORTS, no transports selected * Are you sure? [NO] : y If you answer YES, no transport configuration information is generated. The configuration procedure creates empty NCL startup script files for both transports. To create a usable configuration, you will have to run the configuration procedure again to create valid transport scripts. ______________________________________________________ Using the BASIC and ADVANCED Configuration Options 6-39 Using the BASIC and ADVANCED Configuration Options 6.7 Configuring Transports 6.7.1 Specifying the Network Service Protocol (NSP) Transport Configuration BASIC The BASIC option configures the NSP transport using the default values discussed in this section. Proceed to Section 6.7.2. ADVANCED The ADVANCED option begins the NSP transport configuration with following question: * Configure the NSP Transport? [YES] : Answer YES if you want the system to communicate with DECnet Phase IV nodes 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 preceding question. ________________________ Note ________________________ If you answer NO to this question and you specified a valid Phase IV address for the node (that is, not 0.0), the procedure overrides your decision. Instead, it uses the default values to configure the NSP transport. The procedure displays the following message to indicate this action: %NET$CONFIGURE-I-NSPCONFIG, NSP will be configured since a Phase IV address is being used ______________________________________________________ The procedure then displays a series of prompts for three interrelated settings of the NSP transport configuration: * Maximum number of logical links? [200] : * Maximum transmit and receive window? [20] : * Maximum receive buffers? [4000] : The first question determines the maximum number of active transport connections (logical links) allowed at any one time to the NSP transport. Press Return to select the default value or enter a number from 1 to 65535. 6-40 Using the BASIC and ADVANCED Configuration Options Using the BASIC and ADVANCED Configuration Options 6.7 Configuring Transports The second question determines the value of the transport's maximum window attribute. HP recommends setting a value of 20 for the maximum transmit and receive window option. Press Return to select the default value or enter a number from 1 to 65535. The third question prompts for the number of receive buffers to preallocate. In a typical network environment, HP recommends setting a value for maximum receive buffers that is no more than the value you entered for the maximum window option multiplied by the value you specified for the maximum number of logical links. ________________________ Notes ________________________ Selecting values for the maximum transmit and receive window option or maximum receive buffers option other than those recommended by HP 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. Selecting a high value for maximum receive buffers may require considerable buffering capacity on your node; therefore, non-paged pool should be allocated accordingly. If your node does not have enough non- paged pool, you may want to set maximum receive buffers to a smaller value than the recommended value. ______________________________________________________ For additional information about these parameters, see the subsection about configuring the NSP transport in the "Managing Transport Services" section in the HP DECnet-Plus for OpenVMS Network Management manual. 6.7.1.1 Flow Control Policy The NSP transport configuration finishes with a question about NSP's flow control policy. Flow control is the mechanism that determines when to send normal and expedited data messages. During connection establishment, each end of the connection uses this setting to determine when to expect data when acting as the receiver. It is not required that both ends of a connection use the same flow control policy. Using the BASIC and ADVANCED Configuration Options 6-41 Using the BASIC and ADVANCED Configuration Options 6.7 Configuring Transports BASIC The BASIC option configures NSP with segment flow control. Proceed to Section 6.7.2. ADVANCED The ADVANCED option prompts for the flow control policy: * NSP flow control policy (SEGMENT, NO)? [SEGMENT] : Enter SEGMENT to choose segment flow control. Enter NO to disable flow control. 6.7.2 Specifying the OSI Transport Configuration BASIC The BASIC option configures the OSI transport using the default values discussed in this section (including enabling OSI applications over TCP/IP and DECnet over TCP/IP). Proceed to Section 6.7.3. ADVANCED The ADVANCED option begins the OSI transport configuration with following question: * Configure the OSI Transport or run over TCP/IP? [YES] : Answer YES 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. Also answer YES if you want to use DECnet over TCP/IP or OSI applications over TCP/IP. 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 preceding question. The procedure then displays a series of prompts for three interrelated settings of the OSI transport configuration: * Maximum number of logical links? [200] : * Maximum transmit and receive window? [20] : * Maximum receive buffers? [4000] : The first question determines the maximum number of active transport connections (logical links) allowed at any one time to the OSI transport. Press Return to select the default value or enter a number from 1 to 65535. 6-42 Using the BASIC and ADVANCED Configuration Options Using the BASIC and ADVANCED Configuration Options 6.7 Configuring Transports The second question determines the value of the transport's maximum window attribute. HP recommends setting a value of 20 for the maximum transmit and receive window option. Press Return to select the default value or enter a number from 1 to 65535. The third question prompts for the number of receive buffers to preallocate. In a typical network environment, HP recommends setting a value for maximum receive buffers that is no more than the value you entered for the maximum window option multiplied by the value you specified for the maximum number of logical links. ________________________ Notes ________________________ Selecting values for the maximum transmit and receive window option or maximum receive buffers option other than those recommended by HP 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. Selecting a high value for maximum receive buffers may require considerable buffering capacity on your node; therefore, non-paged pool should be allocated accordingly. If your node does not have enough non- paged pool, you may want to set maximum receive buffers to a smaller value than the recommended value. ______________________________________________________ For additional information about these parameters, see the subsection about configuring the OSI transport in the "Managing Transport Services" section in the HP DECnet-Plus for OpenVMS Network Management manual. 6.7.2.1 Enabling OSI Applications over TCP/IP and DECnet over TCP/IP If you configure the OSI transport, you have the option of allowing OSI applications and DECnet to use the services provided by HP TCP/IP Services for OpenVMS (or any other vendor's TCP/IP product that supports the PATHWORKS Internet Protocol (PWIP) interface) to run OSI or DECnet applications over a TCP/IP network. Using the BASIC and ADVANCED Configuration Options 6-43 Using the BASIC and ADVANCED Configuration Options 6.7 Configuring Transports Enabling OSI applications over TCP/IP includes port 102 in the set of OSI transport RFC 1006 listener ports and builds the appropriate RFC 1006 template. However, to fully support OSI applications over TCP/IP you must also ensure the following: o HP TCP/IP Services for OpenVMS (or any other vendor's TCP/IP product that supports the PWIP interface) is configured and running on both the local and remote system. o The remote node also has OSI applications over TCP/IP enabled (that is, it is listening on port 102). Enabling DECnet over TCP/IP includes port 399 in the set of OSI transport RFC 1006 listener ports and builds the appropriate RFC 1859 template (considered an RFC 1006-type template). However, to fully support DECnet over TCP/IP you must also ensure the following: o HP TCP/IP Services for OpenVMS (or any other vendor's TCP/IP product that supports the PWIP interface) is configured and running on both the local and remote system. o The remote node also has DECnet over TCP/IP enabled (that is, it is listening on port 399). BASIC The BASIC option enables OSI applications over TCP/IP and DECnet over TCP/IP. ADVANCED The ADVANCED option begins by asking whether you want to enable OSI applications over TCP/IP: * Run OSI Applications over TCP/IP? [YES] : Answer YES to this question if you want to run OSI applications over TCP/IP. Next, the procedure asks if you want to enable DECnet over TCP/IP: * Run DECnet over TCP/IP? [YES] : 6-44 Using the BASIC and ADVANCED Configuration Options Using the BASIC and ADVANCED Configuration Options 6.7 Configuring Transports Answering YES to this question enables DECnet-Plus to run over a TCP/IP network to any system that has enabled this same feature. * Interface(s) for DECnet/OSI over TCP/IP ? [ALL] : Answering ALL to this question enables DECnet-Plus to listen on ALL IP-configured interfaces. If you do not wish to listen on all interfaces, then you can specify the static IP address of the interface(s) on which DECnet- Plus should listen for inbound DECnet/OSI connections over TCP/IP. BASIC and ADVANCED If OSI applications over TCP/IP or DECnet over TCP/IP are configured, the net$configure procedure checks for the availability of the DOMAIN name service and the PWIP driver. If the DOMAIN name service is not available, the procedure displays the following message: NET$CONFIGURE-W-NODOMAIN, DECnet over IP requires DOMAIN in the directory services list If the PWIP driver is not available, the procedure displays the following message: NET$CONFIGURE-W-NOPWIP, DECnet over IP requires the PWIP driver to be enabled Both of these messages are warnings; the configuration continues. As long as the functionality is not required the configuration need not be changed. If you need the DOMAIN name service, run net$configure again and include DOMAIN in the directory service list and enter a DOMAIN node name. 6.7.3 Specifying Transport Congestion Avoidance One feature of both transports 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 the transport receives data that passed through a network path where the Congestion Experienced bit is set, the transport reduces the transmit Using the BASIC and ADVANCED Configuration Options 6-45 Using the BASIC and ADVANCED Configuration Options 6.7 Configuring Transports 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. HP recognizes that most of its customers have multi- protocol networks. In this environment, not all network protocols have Congestion Avoidance mechanisms. Therefore, the default for this option is to disable Congestion Avoidance. If you operate in an environment where you can take advantage of Congestion Avoidance mechanisms, HP recommends that you enable the feature. BASIC The BASIC option configures each transport with congestion avoidance disabled. ADVANCED The ADVANCED option asks the following question about your network environment: * Is this system operating in a multi-protocol network? [YES] : If you take the default answer of YES, then both transport's Congestion Avoidance characteristics are set to FALSE and this option is disabled. Answer NO to this question to set the characteristics to TRUE and enable the option. 6.7.4 Configuring Slow-Speed NSP Transport Connections NSP connections over slow-speed point-to-point lines require adjustments to NSP's delay factor and maximum window settings. The configuration utility asks the following question if you have configured point-to-point devices that have the potential to operate at very slow line speeds: * Are the point-to-point lines utilizing line speeds less than 9600 BPS? [NO] : Answer YES if you have slow-speed point-to-point device. Otherwise, press Return to accept the default answer. 6-46 Using the BASIC and ADVANCED Configuration Options Using the BASIC and ADVANCED Configuration Options 6.7 Configuring Transports 6.7.5 Specifying the OSI Loopback Test Application Account If the OSI transport is configured, a test program (sys$test:osit$ivp) is installed. You can use this program to verify OSI transport operation. For more information about the OSI test program, see the subsection about testing the OSI transport in the "Managing Transport Services" section in the HP DECnet-Plus for OpenVMS Network Management manual. BASIC The BASIC option selects the user name SYSTEST for the test account. ADVANCED The ADVANCED option asks for the user name to use when running the OSI test program: * Username for OSI loopback test application to use? [SYSTEST] : Press Return to accept the default user name for the application loopback test account or enter a user name. 6.7.6 Configuring OSI Templates If you configured the OSI transport, net$configure automatically creates the default OSI templates required by the OSAK and FTAM installation verification procedures (IVPs). The procedure displays a message stating that these default OSI templates have been created: %NET$CONFIGURE-I-CREDEFOSITEMPLATE, created default OSI templates The default templates created are osit$loop_clns, osit$loop_cons, osit$rfc1006, and, if DECnet over TCP/IP was chosen, osit$rfc1006plus. In addition, a template with the name DEFAULT is created when the OSI transport entity is enabled. This template is used when no template is specified. BASIC The BASIC option does not provide the opportunity to create additional OSI templates. You will not be able to use OSI applications to make connections to other OSI systems unless you use the ADVANCED option to create additional OSI templates. You can do this at a later time. Proceed to Section 6.8. Using the BASIC and ADVANCED Configuration Options 6-47 Using the BASIC and ADVANCED Configuration Options 6.7 Configuring Transports ADVANCED The ADVANCED option provides the opportunity to create additional OSI templates. The dialog begins by asking if you want to create additional templates: * Do you want to create additional OSI templates? [NO] : yes If you answer YES, the procedure uses the prompts discussed in this section to obtain the information required to configure the OSI templates. If you answer NO, you can create additional templates at a later time. Proceed to Section 6.8. 6.7.6.1 Common Template Parameters The template questions begin with the parameters common to all templates for all transport service types: 1. The procedure asks for the type of template you want to create: o Connectionless-mode Network Service (CLNS) There are two forms of CLNS: Internet/ES-IS and Null Internet. Both forms support only one transport class: Class 4. - CLNS with Internet/ES-IS The communicating end systems may be on the same subnetwork or on different subnetworks. This network service is provided by the implementation of the ES-IS (end system to intermediate system) Internet routing protocols, which route packets from the end system to an intermediate system on the same subnetwork. The intermediate system ensures that packets reach their final destination. Two end systems that implement ES-IS on the same subnetwork may communicate without an intervening intermediate system. - CLNS with Null Internet The communicating end systems must be on the same 802.3 local area network. This network service is provided by the inactive subset of the Internet protocol. No intermediate system is involved in the network connection. o Connection Oriented Network Service (CONS) 6-48 Using the BASIC and ADVANCED Configuration Options Using the BASIC and ADVANCED Configuration Options 6.7 Configuring Transports In DECnet-Plus, CONS is supported by X.25 connections. CONS supports all transport classes (class 0, 2, and 4). The underlying X.25 network connection can be any of the following: - A connection between two systems attached to an X.25 Packet Switching Data Network (PSDN), either directly or via a connector system. - A point-to-point connection between two end systems using the LAPB protocol as the data link protocol. - A direct connection between two end systems attached to the same IEEE 802.3 local area network, using the LLC2 protocol. o A connection between two systems using the X.25 over TCP/IP (XOT) protocol as described in RFC 1613. o RFC 1006 Network Service (RFC 1006) Indicates that the OSI transport should use the TCP/IP protocol stack. This service supports transport classes 0 and 4. When using DECnet applications over RFC 1006 connections, the OSI transport template osit$rfc1006 is used for inbound connections; the default template is used for outbound connections. Enter the template type you want to create: * Type of network service (CLNS/CONS/RFC1006)? [CLNS] : If you want to use Connectionless-mode Network Service (CLNS), press Return. Otherwise, enter the network service for which you want to define the template. 2. Depending on which network service you select, the procedure displays 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] : 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. Using the BASIC and ADVANCED Configuration Options 6-49 Using the BASIC and ADVANCED Configuration Options 6.7 Configuring Transports 3. Next, the procedure asks if the template will be used exclusively for inbound packets. Templates for inbound connections provide OSI transport characteristics required for inbound transport connections. If no other template can be found with the inbound characteristic set, OSI transport uses the template with the name DEFAULT. For more information about how an inbound template is selected, see the description of the inbound characteristic of the osi transport template entity in the HP DECnet-Plus for OpenVMS Network Control Language Reference manual. Indicate if this template will be used exclusively for inbound connections: * Will this template be used for inbound packets? [YES] : 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. 4. DECnet-Plus supports three transport classes: 0, 2, and 4. The following list provides a short summary of the services provided by each transport class: o Class 0 - The most basic transport service. This service does not support flow control, multiplexing, or error detection and recovery. o Class 2 - Supports class 0 functions plus multiplexing and flow control. The OSI transport always uses the flow control capabilities. o Class 4 - Supports class 2 functions plus error detection and recovery. If you selected CONS as the network service type, the default is 0, 2, 4. If you selected CLNS, the default is 4. If you selected RFC1006, the default is 0, 2. Enter the numbers of the transport protocol classes you want to allow for connections that use this template: * Transport Classes to support? [4] : For more information about transport protocol classes, refer to the HP DECnet-Plus for OpenVMS Network Management manual. 6-50 Using the BASIC and ADVANCED Configuration Options Using the BASIC and ADVANCED Configuration Options 6.7 Configuring Transports 5. The following two questions are common to all templates. However, the order in which they appear varies depending on the network service type. ________________________ Note ________________________ For CLNS and RFC 1006 template definitions, enter the information discussed in this step, proceed to the appropriate service-specific subsection, and then return to Step 6 in this section. For CONS template definitions, proceed to the CONS- specific subsection (Section 6.7.6.3) and then return to this step after entering the CONS-specific information. ______________________________________________________ The configuration procedure asks if you want to allow expedited data on transport connections using this template: * Allow use of expedited data? [YES] : If you want to support the use of expedited data, answer YES. The configuration procedure asks if you want to allow checksums on transport connections using this template: * Allow use of Checksums? [YES] : If you want to use the error correction feature, answer YES. 6. All template definitions end with a question asking if you want to create additional templates: * 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 (starting with the "Name of the OSI template?" prompt discussed in Step 2). If you answer NO, proceed to Section 6.8. Using the BASIC and ADVANCED Configuration Options 6-51 Using the BASIC and ADVANCED Configuration Options 6.7 Configuring Transports 6.7.6.2 CLNS Network Service Template Parameters A CLNS OSI transport template can specify the use of Internet/ES-IS routing protocols or Null Internet routing protocol. The Null Internet protocol only operates over LAN routing circuits (CSMA-CD and FDDI data links). 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. Specify the CLNS routing protocol supported by this template: * Use full CLNP or Null Internet? [Full CLNP] : Press Return to accept the default of full clnp or enter null internet. _______________________ Warning _______________________ If you specify the Null Internet option and no LAN circuits are available, the configuration procedure terminates with the following message: %NET$CONFIGURE-E-ERRINRTGCIRC, error in accessing a default routing circuit name ______________________________________________________ If you answer Null Internet, the procedure asks two additional questions. The first question asks for the routing circuit you want to use for this CLNS Null Internet template: * Which routing circuit is this Null Internet template for? [CSMACD-0] : _______________________ Warning _______________________ If you specify either a nonexistent routing circuit or a non-LAN routing circuit, the configuration procedure terminates with the following message: 6-52 Using the BASIC and ADVANCED Configuration Options Using the BASIC and ADVANCED Configuration Options 6.7 Configuring Transports %NET$CONFIGURE-E-RTGCIRCNOTFND, routing circuit name circuit-name not found in the routing circuit list ______________________________________________________ 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 this templates supports Null Internet routing, you must configure an inactive area address for the circuit. The inactive area address for the circuit must be different from 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. Specify the CLNS inactive area address to use for this template: * Which CLNS Inactive Area to use? [49::FF-00] : 6.7.6.3 CONS Network Service Template Parameters For CONS transport connections, you must specify the name of the X.25 Access template that transport should use when making outgoing calls using this transport template. Enter the name of the X.25 Access template to use for outgoing calls: * CONS template name? [OSI Transport] : If the CONS template is used for inbound packets, you must specify the name of the X.25 Access filter that transport should use when receiving incoming calls using this transport template. Enter the name of the X.25 Access filter to use for incoming calls: * CONS filter name? [OSI Transport] : Using the BASIC and ADVANCED Configuration Options 6-53 Using the BASIC and ADVANCED Configuration Options 6.7 Configuring Transports 6.7.6.4 RFC 1006 Network Service Template Parameters OSI applications over TCP/IP (RFC 1006) and DECnet over TCP/IP (RFC 1859) connections use RFC 1006 templates. For more information on configuring OSI applications over TCP/IP and DECnet-Plus over TCP/IP, refer to Section 6.7.2.1 and the "Managing Transport Services" section in the HP DECnet-Plus for OpenVMS Network Management manual. For RFC 1006 templates, you must define the local TCP/IP port number to use for outgoing transport connections using this template. Enter the port number to use for outgoing RFC 1006-type connections: * Local RFC1006 port number? [102] : For OSI applications over TCP/IP, use 102 as the port number. For DECnet over TCP/IP connections, use 399 as the port number. If the RFC 1006 template is used for inbound packets, you must define the local TCP/IP port number to be used as the listener port for incoming transport connections using this template. If the listener port number does not match the outgoing port number, this template will not be used for incoming connections. Enter the port number to use for incoming RFC 1006-type connections: * RFC1006 listener port number? [102] : For OSI applications over TCP/IP, use 102 as the port number. For DECnet over TCP/IP connections, use 399 as the port number. 6.8 Configuring Time Zone Differential Factors The UTC (Coordinated Universal Time) is calculated automatically by using the OpenVMS UTC. No messages are displayed. 6-54 Using the BASIC and ADVANCED Configuration Options Using the BASIC and ADVANCED Configuration Options 6.9 Configuring the Event Dispatcher 6.9 Configuring the Event Dispatcher BASIC The procedure displays a message stating that it is providing the default Event Dispatcher configuration: %NET$CONFIGURE-I-EVDDEFAULT, providing default Event Dispatcher configuration Proceed to Section 6.10. ADVANCED If you are configuring the Event Dispatcher on a cluster member, the procedure asks if you want the resultant event NCL script file created in the cluster common directory: There is no EVENT startup script present on your system. Would you like this script to be made common to all systems in this cluster, or private to this system? If you answer YES to this question, the script will be made common. * Create a cluster common EVENT startup script? [YES] : Answer YES to create an event NCL script file common to all cluster members. Answer NO to create an event NCL script file unique to the cluster member on which you are running net$configure. The procedure begins the Event Dispatcher configuration by asking if you want to customize the event dispatcher configuration: * Do you want to customize the Event Dispatcher? [NO] : If you answer YES, proceed to Section 6.9.1. If you answer NO, the procedure displays a message stating that it is providing the default Event Dispatcher configuration: %NET$CONFIGURE-I-EVDDEFAULT, providing default Event Dispatcher configuration You have the option of blocking the display of events targeted for this system's console. The procedure asks if you want to display events on the console: * Display events logged to the console of this machine? [YES] : Answer YES if you want to see the events targeted for the console on this system. Answer NO if you want to block the display of events on your system's console. Proceed to Section 6.10. Using the BASIC and ADVANCED Configuration Options 6-55 Using the BASIC and ADVANCED Configuration Options 6.9 Configuring the Event Dispatcher 6.9.1 Configuring Event Sinks The procedure begins the customization of the event dispatcher by asking if you want to configure any event sinks. Event sinks manage incoming event connections and maintain a set of filters (global, specific, and catch-all) that are applied to all data streams assigned to the sink. Indicate if you want to configure a custom sink: * Configure a Sink? [YES] : If you want to create a customized sink, answer YES (for example, if you want to change where to send the output: a terminal, a printer, or a file). If you do not want to configure a customized sink, answer NO and proceed to Section 6.9.2. 1. If you indicate that you want to create a custom sink, the procedure asks you for the sink's name: * Sink name? : Specify the name of the sink you want to create. 2. Next, specify the maximum buffer size (in octets) that the sink can use to process events: * Maximum buffer size? : Specify an integer value. 3. You have the option of associating a DECdns full name with the sink being created. To allow outbound streams to connect to this sink, you must specify either a DECdns object name or an end-user name. If you specify a DECdns object name it must match the sink object you supply when you create any outbound streams using this sink. Next, the procedure asks you for the sink's object name: * Object name? : If you will be using an object name when defining outbound streams associated with this sink, specify the sink's object name: 6-56 Using the BASIC and ADVANCED Configuration Options Using the BASIC and ADVANCED Configuration Options 6.9 Configuring the Event Dispatcher 4. You have the option of associating a session control end-user specification with the sink being created. This is equivalent to specifying the addresses characteristic of a session control application. To allow outbound streams to connect to this sink, you must specify either a DECdns object name or an end-user specification. If you specify an end-user specification it must match the sink end-user specification you supply when you create any outbound streams using this sink. If desired, specify the sink's end-user specification: * End user specification? : Enter an end-user specification in the form number=number, name=name, or uic=[uic- identifier]username. 5. If no other filter actions match an event, or if all other filter actions for an event are set to ignore, the actions specified for the catch-all filter are used. Specify the action that the catch-all filter should use: * Catch all filter action? : The choices are: o BLOCK - Discard the event. o PASS - Report the event. 6. You have the option of entering an informational string to describe the sink: * Description? : Enter informational string. 7. You can specify that an entity's unique identifier be displayed with each event. * Display UIDs? : Answering YES displays the entity's unique identifier. 8. You can specify how the application is to accept the events received by the sink. The choices are: o CONSOLE - Events go the operator's console (OPCOM). o DEVICE - Events go to a device. Using the BASIC and ADVANCED Configuration Options 6-57 Using the BASIC and ADVANCED Configuration Options 6.9 Configuring the Event Dispatcher o FILE - Events go to a file. Enter your choice for the sink's client type: * Client type? : If you answer FILE to the "Client type?" prompt, the procedure asks you for the file name to use: * File name? : Enter the file specification you want to use to capture events (for example, sys$manager:evd_events.log). If you answer DEVICE to the "Client type?" prompt, the procedure asks you for the device to use: * Device name? : Enter the device you want to use to capture events (for example, TWA1:). The sink's configuration is now complete. Next, the procedure asks if you want to create another sink: * Configure another Sink? [NO] : If you do not want to configure another sink, press Return to proceed to Section 6.9.2. If want to configure another sink, enter YES and press Return. The procedure returns you to the "Sink name?" prompt discussed in Step 1 and repeats the prompts required to configure another sink. 6.9.2 Outbound Streams The procedure continues the customization of the event dispatcher by asking if you want to configure any outbound streams. Outbound streams represent an outgoing connection to an event sink. An outbound stream manages the connection to the sink and it filters, processes, and transmits events to the sink. Indicate if you want to configure a custom outbound stream: * Configure an Outbound Stream? [YES] : 6-58 Using the BASIC and ADVANCED Configuration Options Using the BASIC and ADVANCED Configuration Options 6.9 Configuring the Event Dispatcher If you want to create a customized outbound stream, answer YES (for example, if you want to change where to send the event data stream). If you do not want to create a customized outbound stream, answer NO and proceed to Section 6.9.3. 1. If you indicate that you want to create a custom outbound stream, the procedure asks you for the outbound stream's name: * Outbound Stream name? : Specify the name of the outbound stream you want to create. 2. Next, specify the maximum buffer size (in octets) that the outbound stream can use to process events: * Maximum buffer size? : Specify an integer value. 3. The connect retry timer operates continuously from the time the outbound stream is enabled until the stream is disabled or until the connect timer enabled characteristic is set to FALSE. If the outbound stream is already connected to the sink when the timer expires, no connection is attempted at that time. The timer resets and connection attempts continue whenever the timer expires. Specify the number of seconds to wait between connection attempts: * Connect retry timer? : Specify an integer value. 4. If you intend to have the outbound stream use the retry timer value you provided in the previous question, you must enable the connect retry timer. Specify if you want to enable the connect retry timer: * Connect timer enabled? : Answer YES to have the connect retry timer operational. Answer NO to disable it. Using the BASIC and ADVANCED Configuration Options 6-59 Using the BASIC and ADVANCED Configuration Options 6.9 Configuring the Event Dispatcher 5. The disconnect timer is the number of seconds to wait before shutting down an idle connection. A value of 0 indicates that the no disconnect timer is used and that connections are never disconnected automatically. Specify the number of seconds to wait before shutting down an idle connection: * Disconnect timer? : Specify an integer value. 6. The catch-all filter specifies the action to take if neither the specific filter setting nor the global filter setting matches an event or if a filter setting that matches an event is set to Ignore. The choices are: o BLOCK - Discard the event. o PASS - Report the event. Enter the action to take for the catch-all filter: * Catch all filter action? : 7. You have the option of specifying the DECdns full name of the event sink. For an outbound stream to connect with an event sink, you must specify the sink's DECdns object name, the sink's node name/end-user pair, or the sink's address tower. If you specify a DECdns object name, it must match the object name you used when you created the event sink. * Sink object? : If desired, enter the full DECdns object name of the sink associated with this outbound stream. 8. You have the option of specifying a sink node/sink end- user pair to identify the event sink. For an outbound stream to connect with an event sink, you must specify the sink's DECdns object name, the sink's node name/end- user pair, or the sink's address tower. If you are specifying a sink by its node name/end-user pair, enter the full node name (namespace name included) of the sink associated with outbound stream: * Sink node? : 6-60 Using the BASIC and ADVANCED Configuration Options Using the BASIC and ADVANCED Configuration Options 6.9 Configuring the Event Dispatcher If you are specifying a sink by its node name/end-user pair, enter the Session Control end-user specification of the sink associated with this outbound stream (for example, number=82): * Sink end user? : Enter an end-user specification in the form number=number, name=name or uic=[uic- identifier]username. 9. You have the option of specifying a sink address tower to identify the event sink. For an outbound stream to connect with an event sink, you must specify the sink's DECdns object name, the sink's node name/end-user pair, or the sink's address tower. If you are specifying a sink by its address tower, enter the sink address tower of the sink associated with this outbound stream: * Sink address? : The outbound stream's configuration is now complete. Next, the procedure asks if you want to create another outbound stream: * Configure another Outbound Stream? [NO] : If you do not want to configure another outbound stream, press Return to proceed to the Phase IV Relay section. If you want to configure another outbound stream, enter YES and press Return. The procedure returns you to the "Outbound Stream name?" prompt discussed in Step 1 and repeats the prompts required to configure another outbound stream. 6.9.3 Phase IV Relay A Phase IV relay allows you to record and process events that occur on an OpenVMS system running DECnet Phase IV software. The Phase IV Relay entity receives the events from a Phase IV node, encapsulates them, and posts them in the DECnet-Plus system Event Dispatcher. Indicate if you want to include a Phase IV relay: * Configure Phase IV Relay? [YES] : Using the BASIC and ADVANCED Configuration Options 6-61 Using the BASIC and ADVANCED Configuration Options 6.9 Configuring the Event Dispatcher Answer YES to create the Phase IV Relay. 6.10 Configuring the Application Database This configuration section sets up the default accounts used by the following DECnet-Plus applications: o File access listener (FAL) - 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). o CMIP Management Listener (CML) - is the DECnet-Plus management module that implements the Common Management Information Protocol (CMIP). CML enables the system to respond to remote management commands. o MAIL - allows users to send and receive messages. o VMScluster Performance Monitor (VPM) - supports the OpenVMS Monitor utility command monitor cluster. o MIRROR - supports particular forms of loopback testing. o PHONE - allows users on the same or different OpenVMS systems to communicate interactively. BASIC The BASIC option includes the DECnet-Plus default applications 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). The procedure displays the following messages as it creates the default accounts: %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 ________________________ Note ________________________ The procedure also assigns certain process privileges and rights identifiers to each account. If you have the audit server enabled during configuration, it 6-62 Using the BASIC and ADVANCED Configuration Options Using the BASIC and ADVANCED Configuration Options 6.10 Configuring the Application Database displays several OPCOM messages related to this process. ______________________________________________________ Proceed to Section 6.11. ADVANCED The ADVANCED option allows you to control the default accounts for all the DECnet applications. If you are configuring a cluster member, the procedure asks if you want the resultant applications NCL script file created in the cluster common directory: There is no APPLICATION startup script present on your system. Would you like this script to be made common to all systems in this cluster, or private to this system? If you answer YES to this question, the script will be made common. * Create a cluster common APPLICATION startup script? [YES] : Answer YES to create an applications NCL script file common to all cluster members. Answer NO to create an applications NCL script file unique to the cluster member on which you are running net$configure. 1. The procedure begins the applications configuration by asking you for the default account to use for FAL: * Do you want to use a default account for the 'FAL' application? [NO] : If you want an account set up and used for FAL, answer YES. If you answer YES, the procedure displays the following message: %NET$CONFIGURE-I-MAKEACCOUNT, this procedure creates user account FAL$SERVER 2. The procedure then asks if you want to set up a default account for CML: * Do you want to use a default account for the 'CML' application? [YES] : If you want an account set up and used for CML, answer YES. Using the BASIC and ADVANCED Configuration Options 6-63 Using the BASIC and ADVANCED Configuration Options 6.10 Configuring the Application Database If you answer YES, the procedure displays the following message: %NET$CONFIGURE-I-MAKEACCOUNT, this procedure creates user account CML$SERVER 3. Next, the procedure asks if you want to set up a default account for MAIL: * Do you want to use a default account for the 'MAIL' application? [YES] : If you want an account set up and used for MAIL, answer YES. If you answer YES, the procedure displays the following message: %NET$CONFIGURE-I-MAKEACCOUNT, this procedure creates user account MAIL$SERVER 4. The procedure continues by asking if you want to set up a default account for VPM: * Do you want to use a default account for the 'VPM' application? [YES] : Answer YES if the system is part of an OpenVMS Cluster. Answer NO if the system is to be a non-cluster end system. If you answer YES, the procedure displays the following message: %NET$CONFIGURE-I-MAKEACCOUNT, this procedure creates user account VPM$SERVER 5. Next, the procedure asks if you want to set up a default account for the MIRROR application: * Do you want to use a default account for the 'MIRROR' application? [YES] : If you want to use MIRROR, answer YES. If you answer YES, the procedure displays the following message: %NET$CONFIGURE-I-MAKEACCOUNT, this procedure creates user account MIRRO$SERVER 6. Finally, the procedure asks if you want set up a default account for PHONE: * Do you want to use a default account for the 'PHONE' application? [YES] : If you intend to use the OpenVMS PHONE utility, answer YES. 6-64 Using the BASIC and ADVANCED Configuration Options Using the BASIC and ADVANCED Configuration Options 6.10 Configuring the Application Database If you answer YES, the procedure displays the following message: %NET$CONFIGURE-I-MAKEACCOUNT, this procedure creates user account PHONE$SERVER ________________________ Note ________________________ The procedure also assigns certain process privileges and rights identifiers to each account. If you have the audit server enabled during configuration, it displays several OPCOM messages related to this process. ______________________________________________________ 6.11 Configuring the MOP Client By default, MOP is not started by net$startup. To enable this system to service MOP requests, the NET$STARTUP_ MOP logical name must be defined to signal net$startup to load the MOP software. This logical name is normally defined in sys$startup:net$logicals.com. Based on your input, the procedure modifies net$logicals.com by adding or removing the definition of the NET$STARTUP_MOP logical name. This section of the procedure also generates a short NCL startup script file containing the NCL commands to create and enable the MOP entity. The procedure asks if you want MOP loaded: * Load MOP on this system? [YES] : Answer YES to enable MOP service on this system. Answer NO to disable MOP service on this system. Note that your answer will have no effect if the NET$STARTUP_MOP logical name is defined elsewhere. If you are configuring a cluster member, the procedure asks if you want the resultant MOP NCL startup script file created in the cluster's common directory: There is no MOP_CLIENT startup script present on your system. Would you like this script to be made common to all systems in this cluster, or private to this system? If you answer YES to this question, the script will be made common. * Create a cluster common MOP_CLIENT startup script? [YES] : Using the BASIC and ADVANCED Configuration Options 6-65 Using the BASIC and ADVANCED Configuration Options 6.11 Configuring the MOP Client Answer YES to create a MOP NCL startup script file common to all cluster members. Answer NO to create a MOP NCL startup script file unique to the cluster member on which you are running net$configure. 6.12 Configuring the Cluster Alias All of the nodes or a subset of the nodes that are members of an OpenVMS Cluster can be represented in the network as a single node by establishing an alias for the cluster members. The alias allows users access to common resources on the OpenVMS Cluster members without knowing which nodes are members of the alias. Refer to the HP DECnet-Plus for OpenVMS Network Management manual for more information about setting up an OpenVMS Cluster alias. If the node is an OpenVMS Cluster member or if net$configure finds an alias NCL startup script file on the system, the procedure prompts you to enter the full name of the cluster alias: * Full name of Cluster Alias : If you do not want the node to participate in a cluster alias, press Return. Proceed to Section 6.13. 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). ________________________ Note ________________________ If you create a cluster alias, you must manually enter the alias information into the appropriate namespace. See the "Using an OpenVMS Cluster Alias" section in the HP DECnet-Plus for OpenVMS Network Management manual for more information. ______________________________________________________ If you entered a cluster alias, you must associate a unique address with the cluster alias. Do not use your node's address for the cluster alias. If you are unsure which address to enter, consult your network manager. Use either a DECnet Phase IV node address or Ethernet physical address for the alias. 6-66 Using the BASIC and ADVANCED Configuration Options Using the BASIC and ADVANCED Configuration Options 6.12 Configuring the Cluster 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: 1. 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) 2. 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) 3. Incorporate the hexadecimal node address in the following format: AA-00-04-00-hexnodeaddress (For example, AA-00-04-00-8B-30) Enter the unique address to associate with the cluster alias: * Cluster Alias Phase IV Address (aa.nnnn OR AA-00-04-00-xx-xx) : 12.139 If you entered a cluster alias full name, you need to specify the selection weight for this node. 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 for the 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. Setting a selection weight that is too low encourages needless connection delay Using the BASIC and ADVANCED Configuration Options 6-67 Using the BASIC and ADVANCED Configuration Options 6.12 Configuring the Cluster Alias because each incoming connection is treated in a round- robin fashion. That is, as each new connection comes in, it must be passed to the next cluster member. HP recommends values between 5 and 10. Enter the selection weight for this cluster member: * Selection weight for this cluster node [0 for satellites] : 6.13 Summary Display At this point, the procedure has asked all questions related to the node's configuration. The procedure displays a summary of most of the information gathered by the net$configure dialog: 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:: Session Control Address Update Interval: 10 Routing Node Type: ENDNODE Autoconfiguration of Network Addresses: Enabled Routing ESHello Timer: 600 Routing ES Cache Size: 512 Alias Name: ACME:.WABBIT.HELP Device Information: Device: ESA0 (DESVA): Data Link name: CSMACD-0 Routing Circuit Name: CSMACD-0 Transport Information: 6-68 Using the BASIC and ADVANCED Configuration Options Using the BASIC and ADVANCED Configuration Options 6.13 Summary Display NSP Transport: Configured Maximum number of logical links: 200 Maximum Transmit and Receive Window: 20 Maximum Receive Buffers: 4000 Flow Control Policy: Segment Flow Control OSI Transport: Configured Maximum number of logical links: 200 Maximum Transmit and Receive Window: 20 Maximum Receive Buffers: 4000 OSI applications over TCP/IP: Enabled DECnet Applications over TCP/IP: Enabled Congestion Avoidance Disabled Event Dispatcher Configuration: Sinks: local_sink Outbound Streams: local_stream Phase IV Relay: Enabled 6.14 Generating the NCL Scripts After displaying the configuration summary, the procedure asks if you want to create the NCL startup scripts based on the information you entered: * Do you want to generate NCL configuration scripts? [YES] : Answer YES to accept the configuration you just specified. The procedure automatically generates a collection of NCL startup scripts in the sys$manager directory (all with the name net$function_startup.ncl. These scripts are invoked by the net$startup process when the network is started. You can see each script being invoked by watching for the NET$STARTUP-I-EXECUTESCRIPT messages during network startup. For more information about starting up the network, see the "Defining Logical Names That Modify Network Operation" and "Managing a Node" sections in the HP DECnet-Plus for OpenVMS Network Management manual. The procedure also performs a checksum process on the scripts so that it can be aware if any of the scripts have changed when you run net$configure again. It displays a message indicating that the checksum process is in progress: Using the BASIC and ADVANCED Configuration Options 6-69 Using the BASIC and ADVANCED Configuration Options 6.14 Generating the NCL Scripts %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. ______________________________________________________ 6.15 Starting the Network To complete the configuration, the net$configure procedure must start the network. Although it can complete most of the network configuration without an active network, it must start the network to complete the registration of the node in the various name services. 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 6-70 Using the BASIC and ADVANCED Configuration Options Using the BASIC and ADVANCED Configuration Options 6.15 Starting the Network HP strongly recommends that you answer YES to start the network. When you choose to start the network, net$configure invokes the sys$startup:net$startup.com procedure to start the network. The net$startup procedure displays information similar to the following: Copyright 2006 Hewlett-Packard Development Company, L.P. %NET-I-LOADED, executive image LES$LES_V30.EXE loaded %NET-I-LOADED, executive image NET$ALIAS.EXE loaded %NET-I-LOADED, executive image NET$SESSION_CONTROL.EXE loaded . . . %NET$STARTUP-I-EXECUTESCRIPT, executing NCL script SYS$SYSROOT:[SYSMGR]NET$NODE_STARTUP.NCL; %NET$STARTUP-I-EXECUTESCRIPT, executing NCL script SYS$SYSROOT:[SYSMGR]NET$CSMACD_STARTUP.NCL; %NET$STARTUP-I-EXECUTESCRIPT, executing NCL script SYS$SYSROOT:[SYSMGR]NET$FDDI_STARTUP.NCL; . . . %NET$STARTUP-I-OPERSTATUS, DECnet-Plus for OpenVMS operational status is RUNNING-MAJOR Although the system parameters process has been automated, you may still see the following message if net$startup is not able to start the network due to insufficient system resources: %NET$STARTUP-I-OPERSTATUS, DECnet-Plus for OpenVMS operational status is OFF-AUTOGENREQ 6.16 Namespace Modification Based on your answers about Phase IV database conversion, the directory service path, and the node's full name for each specified name service, the configuration procedure now performs a series of actions to register your node in the appropriate namespaces. The exact actions taken depend on the information you supplied, the existence of former node identification information for your node, and Using the BASIC and ADVANCED Configuration Options 6-71 Using the BASIC and ADVANCED Configuration Options 6.16 Namespace Modification the state of the network and any DECdns name servers used during the namespace modification process. The following series of messages is for a Local namespace- only configuration (including a Phase IV database conversion which includes the local node ASHFLD): Directory Service: Phase IV database Exporting node name information using: * CONWAY HEATH ASHFLD Number of nodes exported: 3 Directory Service: Local name file Updating nodes listed in SYS$MANAGER:NET$PHASEIV_NODES.DAT CONWAY HEATH ASHFLD Number of nodes registered: 3 Number of nodes modified: 0 %NET$CONFIGURE-I-CONVERTNODEDB, converted the Phase IV node database Directory Service: Local name file Modifying the node: LOCAL:.ASHFLD Modifying the node towers %NET$CONFIGURE-I-NODERENAMED, node successfully renamed to LOCAL:.ASHFLD %NET$CONFIGURE-I-FLUSHCACHE, flushing selected cache entries ________________________ Note ________________________ For sets of namespace modification messages for different name service and network configurations, see Section 7.6. ______________________________________________________ After namespace information is updated, the net$configure procedure calls net$startup a second time to start the event dispatcher, DECdts, the DECnet applications, and MOP (if enabled). It also enables the cluster alias at this time. During this phase of the startup, the procedure displays several messages similar to the following: 6-72 Using the BASIC and ADVANCED Configuration Options Using the BASIC and ADVANCED Configuration Options 6.16 Namespace Modification Copyright 2006 Hewlett-Packard Company, L.P. %NET$STARTUP-I-STARTPROCESS, starting process EVD %RUN-S-PROC_ID, identification of created process is 00000117 %NET$STARTUP-I-EXECUTESCRIPT, executing script SYS$SYSROOT:[SYSMGR]NET$EVENT_STARTUP.NCL . . . (a series of event messages are displayed by OPCOM) . . . %NET$STARTUP-I-STARTPROCESS, starting process DTSS %RUN-S-PROC_ID, identification of created process is 00000118 %DTSS-I-SETTDF DTSS$SERVICE set new timezone differential %NET$STARTUP-I-EXECUTESCRIPT, executing script SYS$SYSROOT:[SYSMGR]NET$APPLICATION_STARTUP.NCL %NET-I-LOADED, executive image NET$LOOP_APPLICATION.EXE loaded Finally, net$configure indicates that the configuration process is complete: %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 a 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 DECnet-Plus. 6.17 Modifying 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 7 for information about running the net$configure BASIC or ADVANCED options to modify your DECnet-Plus configuration. Using the BASIC and ADVANCED Configuration Options 6-73 7 _________________________________________________________________ Modifying a Current Configuration This chapter describes the steps necessary to modify a current configuration. 7.1 Choosing a Configuration Option If your system has already been configured, you can modify it with the net$configure basic configuration option (the default) or with the net$configure advanced configuration option. Table 7-1 provides some guidelines for making your configuration choice. After you have decided with option to use, proceed to Section 7.2. Table 7-1 Choosing a Configuration Option to Modify a Current __________Configuration__________________________________________ Option..._Choose_if...___________________________________________ BASIC The node is in an OpenVMS Cluster. You are upgrading or reconfiguring DECnet-Plus. You need to access a DECdns server for network addresses. You have only 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. (continued on next page) Modifying a Current Configuration 7-1 Modifying a Current Configuration 7.1 Choosing a Configuration Option Table 7-1 (Cont.) Choosing a Configuration Option to Modify a __________________Current_Configuration__________________________ Option..._Choose_if...___________________________________________ You want to configure both the NSP and OSI transports and only want to create default OSI templates. You want to enable DECnet over TCP/IP (RFC 1859) or OSI applications over TCP/IP (RFC 1006). 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 (to control the interpretation of address structuring). You want to use integrated mode routing. (continued on next page) 7-2 Modifying a Current Configuration Modifying a Current Configuration 7.1 Choosing a Configuration Option Table 7-1 (Cont.) Choosing a Configuration Option to Modify a __________________Current_Configuration__________________________ 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 an OpenVMS 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.___________________________________________________ 7.2 Invoking the Configuration Procedure Begin by invoking the configuration procedure. BASIC To invoke the net$configure.com procedure using the BASIC configuration option, enter the following command: $ @sys$manager:net$configure basic Modifying a Current Configuration 7-3 Modifying a Current Configuration 7.2 Invoking the Configuration Procedure ADVANCED To invoke the net$configure.com procedure using the ADVANCED configuration option, enter the following command: $ @sys$manager:net$configure advanced 7.3 Opening Messages The procedure prints an opening message dependent on the configuration option you chose. BASIC Copyright 2006 Hewlett-Packard Development Company, L.P. 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 ADVANCED Copyright 2006 Hewlett-Packard Development Company, L.P. 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 7-4 Modifying a Current Configuration Modifying a Current Configuration 7.3 Opening Messages BASIC and ADVANCED Next, the procedure asks if you want to proceed with the configuration. * Do you want to continue? [YES] : Answer YES if you want to continue. The procedure displays the date that the checksum file for the NCL startup scripts was last modified: Configuration last run by SYSTEM on 18-SEP-2004 16:04:24.19 If previous configurations resulted in cluster-common NCL startup script files, the procedure uses one or more of the following messages to tell you which cluster-common script files are in use (see Section 7.16 for more information about cluster-common script files): %NET$CONFIGURE-I-USECOMMON, using cluster common APPLICATION script %NET$CONFIGURE-I-USECOMMON, using cluster common EVENT script %NET$CONFIGURE-I-USECOMMON, using cluster common MOP_CLIENT script If both cluster-common script files and system-specific script files exist, the procedure uses one or more of the following messages to tell you which system-specific script files are overriding the cluster-common script files: %NET$CONFIGURE-I-OVERRIDECOMMON, node specific APPLICATION script overrides the cluster common settings %NET$CONFIGURE-I-OVERRIDECOMMON, node specific EVENT script overrides the cluster common settings %NET$CONFIGURE-I-OVERRIDECOMMON, node specific MOP_CLIENT script overrides the cluster common settings The configuration procedure maintains a lock file (sys$common:[sysmgr]net$configure-lock.dat;1) to prevent multiple users from running the procedure at the same time. If another process is using the procedure, it displays the following message: %NET$CONFIGURE-I-WAITFORLOCK, the configuration database is in use by another process, waiting... If the configuration procedure is unable to access the checksum file, or it can access the file but experiences a read error, the procedure displays one of the following two messages: Modifying a Current Configuration 7-5 Modifying a Current Configuration 7.3 Opening Messages %NET$CONFIGURE-E-CKSOPENERR, error opening checksum file %NET$CONFIGURE-E-CKSREADERR, error reading checksum file If one of these error messages is displayed, the procedure exits. Determine the cause for the error and rerun net$configure. 7.4 The Main Options Menu The configuration procedure now displays the main options menu that you can use to modify the current configuration: Configuration Options for Node node-name: [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] : ________________________ Note ________________________ If this is the first time you are invoking the net$configure procedure, or if you have deleted the checksum file, the main menu is not displayed. Instead, the procedure begins the full configuration dialog discussed in Chapter 6. ______________________________________________________ Choose the option you want. Selecting an option allows you to modify either the entire configuration or a particular portion. Based on your menu selection, proceed to the section indicated in the following table. 7-6 Modifying a Current Configuration Modifying a Current Configuration 7.4 The Main Options Menu ___________________________________________________________ Menu Item__Option_____________________Proceed_to_...____________ 1 Perform an entire Section 7.5 configuration 2 Change naming information Section 7.6 3 Configure Devices on this Section 7.7 machine 4 Configure Transports Section 7.8 5 Configure Timezone Section 7.9 Differential Factor 6 Configure Event Section 7.10 Dispatcher 7 Configure Application Section 7.11 database 8 Configure MOP Client Section 7.12 database 9 Configure Cluster Alias Section 7.13 10 Replace MOP Client Section 7.14 Configuration 11 Configure satellite nodes Section 7.15 12 Configure cluster script Section 7.16 ______locations____________________________________________ ________________________ Note ________________________ The procedure displays Options 11 or 12 only if the procedure is executing on a cluster member. Option 12 is displayed only if you invoke the procedure in ADVANCED mode. See Section 7.15 and Section 7.16 for more information. ______________________________________________________ 7.5 Changing an Entire Configuration To make changes to the entire configuration, select option 1 from the main options menu: * Which configuration option to perform? [1] : 1 Modifying a Current Configuration 7-7 Modifying a Current Configuration 7.5 Changing an Entire Configuration In most sections, the procedure displays the same prompts that were displayed during the initial configuration dialog. However, in some dialog sections there are differences. For this reason, you should see the following sections for the resulting dialog: 1. Phase IV database conversion - Section 6.3 2. Node naming service and name information - Section 7.6 3. Routing information - Section 6.5 4. Device information - Section 6.6 5. Transport information - Section 7.8 6. Event Dispatcher information - Section 7.10 7. Applications information - Section 7.11 8. MOP information - Section 6.11 9. Configuration summary display - Section 7.17 10. NCL script generation - Section 7.18 11. Network startup - Section 7.19 Because it is highly likely that you will do a reconfiguration while the network is running using a previous configuration, you will probably not see the prompts related to starting the network. Therefore, to implement the new NCL scripts, you must reboot the system. The system displays the same prompts that were displayed for the initial configuration. In most cases, the prompts now show the current configuration values as the default. If you do not want to change the current values, accept the default value. Refer to the sections indicated above for an explanation of the prompts. 7.6 Changing the Node Name/Namespace Name To change the directory name services used on the system, the system's full names or the fully qualified host name, or the system's node synonym, select option 2 from the main menu: * Which configuration option to perform? [1] : 2 7-8 Modifying a Current Configuration Modifying a Current Configuration 7.6 Changing the Node Name/Namespace Name Although the basic dialog questions are identical to those documented in Section 6.4, there are many possible variants and many possible final configuration outcomes based on the answers you provide in this section and the current status of your system. After a discussion of some processing topics common to all configuration variants, the remainder of this section discusses several possible configuration modifications for name services and node names: o Changing the node from the Local-only namespace to a DECdns namespace as the primary with the Local namespace as the secondary (see Section 7.6.3). o Changing the node as in the previous item except using a DECdns server on a WAN instead of on a LAN (see Section 7.6.4). o Changing a DECdns clerk system to a DECdns server system (see Section 7.6.5). o Changing a DECdns server system back to a DECdns clerk system (see Section 7.6.6). o Changing a DECdns clerk system with a previous DECdns server configuration back to a DECdns server system (see Section 7.6.7). o Modifying a DECdns server system to use the DECdns namespace as a secondary namespace (see Section 7.6.8). For each of the modifications in the previous list, the net$configure procedure processing occurs in three steps: 1. Configuration dialog processing - occurs as you provide the configuration information. Based on the information you provide and the status of the current configuration, the procedure customizes the configuration dialog to each task. 2. Namespace selection processing - occurs after all configuration dialog processing has finished and before the actual namespace configuration processing begins. Based on the information you provide, the procedure places the system in a condition suitable for the namespace configuration processing. This processing usually involves calling the dns$configure.com procedure to configure the DNS clerk to use the new namespace. It may also involve namespace creation. Modifying a Current Configuration 7-9 Modifying a Current Configuration 7.6 Changing the Node Name/Namespace Name 3. Namespace configuration processing - occurs after any necessary namespace selection processing. This processing actually registers the new node information in the appropriate namespace. 7.6.1 Common Namespace Selection Processing When configuring a local system (versus a satellite system), all configuration changes made by using option 2 are executed directly. For this reason, the network must be running. During namespace selection processing, net$configure always begins by verifying that the network is running. If the network is not running, the procedure asks you if you want to start the network: * Do you want to start the network ? [YES]: Answer YES to start the network and continue the node's configuration. If you answer NO, or if the procedure fails in it's attempt to start the network, the procedure warns you that you must elect to start the network or correct the problem that is causing the start attempt to fail and then reinvoke option 2: %NET$CONFIGURE-E-NETNOTSTARTED, network not started %NET$CONFIGURE-DNSNOTCONFIG, DNS could not be configured ********************************************************************** NET$CONFIGURE.COM cannot complete your system's network configuration. 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. When the problem is rectified and you are ready to start the network, please invoke the NET$CONFIGURE.COM procedure and choose menu option 2 (Change naming information) so that the configuration procedure can finish your system's network configuration before starting the network. ********************************************************************** After displaying this warning, the procedure aborts the transaction and returns to the main options menu: %NET$CONFIGURE-I-LASTTRANSABORT, last transaction aborted Configuration Options for Node ASHFLD [0] Exit this procedure 7-10 Modifying a Current Configuration Modifying a Current Configuration 7.6 Changing the Node Name/Namespace Name [1] Perform an entire configuration [2] Change naming information . . . * Which configuration option to perform? [0] : ________________________ Note ________________________ The remaining tasks in this section assume that the network is running or that net$configure can successfully start it. ______________________________________________________ 7.6.2 Modifying Node Information on Satellite Systems During satellite node configurations (see Section 7.15), the procedure does only configuration dialog processing. Rather than actually manipulate the namespace, the procedure generates a node rename file (net$startup_ rename.com) in the satellite's sys$manager: directory. To apply the node name change, you must reboot the satellite node. During startup, the net$startup.com procedure searches for the node rename file and executes the file if located. ______________________ Important ______________________ When configuring a satellite node, you must register the node before rebooting the satellite. The net$configure procedure does not register the node for you. ______________________________________________________ 7.6.3 Changing a Node to Use DECdns as the Primary Namespace This section describes how to add the DECdns namespace as the primary namespace to a system formerly configured exclusively in the Local namespace. ________________________ Note ________________________ This task discussion assumes that no DECdns server software exists on the system being configured. If the DECdns server software exists on the system but Modifying a Current Configuration 7-11 Modifying a Current Configuration 7.6 Changing the Node Name/Namespace Name has never been configured, see Section 7.6.5. If the DECdns server software exists on the system and has been configured, see Section 7.6.7. ______________________________________________________ Configuration Dialog Processing The following example shows a typical dialog to change the node from a Local namespace-only node to a node using both the DECdns and Local namespaces (with DECdns as the primary name service): * Which configuration option to perform? [1] : 2 * Enter the directory services to use on the system [LOCAL] : decdns,local * Enter the full name for directory service DECDNS : hp:.ashfld * Enter the full name for directory service LOCAL [LOCAL:.ASHFLD] : * What is the synonym name for this node? [ASHFLD] : * Naming cache timeout value? [30-00:00:00] : * Session Control Address Update Interval ? [10] : * Naming cache checkpoint interval? [08:00:00] : Namespace Selection Processing Based on the answer provided during configuration dialog processing, the configuration procedure verifies that it can communicate with the server containing the DECdns directory and then calls the dns$configure.com procedure to configure the clerk for this namespace: sys$manager:net$dns_clerk_startup.ncl changed to use the new default namespace. Your default namespace nickname is HP. Your default namespace NSCTS is AA-00-04-00-DE-11-A0-AA-F9-6F-56-DE-8E-00. If the configuration procedure cannot communicate with the DECdns server containing the DECdns directory, the procedure displays the following message: %NET$CONFIGURE-E-DNSNOSHOW, unable to show directory directory Namespace Configuration Processing Based on the answers provided during configuration dialog processing, the configuration procedure executes the new name service searchpath NCL script, renames the node, modifies the Local namespace entry, registers the node in the DECdns namespace, flushes the CDI cache, updates 7-12 Modifying a Current Configuration Modifying a Current Configuration 7.6 Changing the Node Name/Namespace Name the node's address towers, and updates the backtranslation softlink for the node: %NET$CONFIGURE-I-NODERENAMED, node successfully renamed to HP:.ASHFLD Directory Service: Local name file Modifying the node: LOCAL:.ASHFLD Modifying the node towers Finished obtaining address tower information %NET$CONFIGURE-I-IMPORTFILECREATED, created the DECNET_REGISTER import file Directory Service: DECdns Updating nodes listed in SYS$MANAGER:DECNET_REGISTER_IMPORT_FILE_ASHFLD.TXT 1) HP:.ASHFLD Number of nodes registered: 1 Number of nodes modified: 0 %NET$CONFIGURE-I-REGSUCCESS, node has been successfully registered in the DECdns directory service %NET$CONFIGURE-I-FLUSHCACHE, flushing selected cache entries %NET$CONFIGURE-I-CHECKPOINTWAIT, waiting for CDI to write the node name to the CDI cache file %NET$CONFIGURE-I-CHECKPOINTDONE, the node name has been written to SYS$SYSTEM:DECNET$CDI_CACHE.DAT %NET$CONFIGURE-I-TOWERSUPDATED, updated address towers for node %NET$CONFIGURE-E-BCKTRNUPDATED, updated backtranslation softlink for node The procedure then displays the configuration summary, recalculates the NCL script file checksums, and redisplays the main options menu: Summary of Configuration Node Information: Modifying a Current Configuration 7-13 Modifying a Current Configuration 7.6 Changing the Node Name/Namespace Name Directory Services Chosen: DECDNS,LOCAL Primary Directory Service: DECDNS DECdns Full name: HP:.ASHFLD Local Full name: LOCAL:.ASHFLD Node Synonym: ASHFLD Phase IV Address: 24.66 Phase IV Prefix: 49:: DECdns Node Type: Clerk Session Control Address Update Interval: 10 Routing Node Type: ENDNODE Autoconfiguration of Network Addresses: Enabled Routing ESHello Timer: 600 Routing ES Cache Size: 512 . . . %NET$CONFIGURE-I-MODCHECKSUM, checksumming NCL management scripts modified by NE T$CONFIGURE %NET$CONFIGURE-I-CONFIGCOMPLETED, DECnet-Plus for OpenVMS configuration complete Configuration Options for Node ASHFLD [0] Exit this procedure [1] Perform an entire configuration [2] Change naming information . . . * Which configuration option to perform? [0] : 7-14 Modifying a Current Configuration Modifying a Current Configuration 7.6 Changing the Node Name/Namespace Name ________________________ Note ________________________ If you are joining a Distributed Name Service (DNS) Version 1.1 namespace, make sure you have access to the remote server's sys$library:dns$ns_def_file.dat file. Invoke the procedure sys$manager:dns$configure.com and use Option 2 on the DECdns configuration menu to connect to a remote DNS Version 1 server. Make sure the SYSTEM account on your DECdns Version 2 clerk has DECnet_FAL access or proxy access to the sys$library:dns$ns_def_file.dat file on the remote Version 1 server. These accounts need this access to successfully copy the Version 1 server information contained in the sys$library:dns$ns_def_file.dat file. If you are running the DECdns configuration program under a privileged account other than SYSTEM, the account still requires the appropriate access. ______________________________________________________ 7.6.4 Configuring a DECdns Clerk System to Use a WAN DECdns Server This section discusses the same task as the previous section (adding a DECdns namespace name to a system formerly configured exclusively in the Local namespace). However, it shows the extra processing that occurs when you join a namespace that is not available on your node's LAN. Configuration Dialog Processing For the purposes of this discussion, the configuration dialog processing is assumed to be identical to the processing shown in Section 7.6.3. Namespace Selection Processing If your node is a DECdns clerk and the net$configure procedure detects that the namespace you identified in the system's DECdns full name is not served by a DECdns server on the LAN, it displays a list of all the namespaces that do exist on the LAN: Modifying a Current Configuration 7-15 Modifying a Current Configuration 7.6 Changing the Node Name/Namespace Name The namespace you specified was HP. %DNS-E-NOMATNS, The specified namespace is not being served on your LAN. Please choose from the following list: [ 1] APOLLO [ 2] IAF [ 3] MIDAS_NS [ 0] - Reject this list - Pick a number from the list: 0 When you see this display, type 0 and press Return to reject the list of namespaces currently known on your LAN. The procedure then asks if you want to continue the process using a WAN connection: Attempts to configure DECdns via a LAN have failed. Type Y to attempt a WAN connection to a remote DECdns server. To stop DECdns Configuration and return control to the NET$CONFIGURE utility, type N at the following prompt: Do you want to connect to a remote DECdns server via a WAN [y]: Answer YES to connect to a remote server via a WAN. The procedure then prompts you for the remote server's network service access point (NSAP), Phase IV-compatible address (if it has one), or IP address. The NSAP is the network entity title (NET) with a valid transport selector. To find this information, contact the DECdns server's system administrator. The server system probably has a number of different NSAPs. You can use any of these NSAPs to connect to the server system, but you must enter the NSAP in the format in which it is displayed. Attempting to configure a clerk via a WAN connection. Enter the NSAP or Phase IV compatible address or IP address of the server you want to connect to: 24.16 Getting server data, please wait... If the procedure successfully connects with the server, the remainder of the namespace selection processing is identical to Section 7.6.3. 7-16 Modifying a Current Configuration Modifying a Current Configuration 7.6 Changing the Node Name/Namespace Name If the procedure cannot connect to the remote server, the procedure displays the following messages, aborts the transaction, and displays the main options menu: Could not get information from server. Both Phase IV and Phase V connection attempts failed. Use the following information to help correct the problem. Could not connect to remote Phase V server Could not connect to remote Phase IV server: The WAN configuration attempt failed. Do you wish to retry? [y]: N %DNS-E-NOCONFIG, DECdns clerk is not configured. %NET$CONFIGURE-I-LASTTRANSABORT, last transaction aborted Correct the problem preventing the connection to the WAN server and run net$configure again. Namespace Configuration Processing The namespace configuration processing is identical to the namespace configuration processing shown in Section 7.6.3. When performing the actual namespace configuration processing, it makes no difference whether the DECdns server is on a LAN or on a WAN. 7.6.5 Converting a DECdns Clerk System to a DECdns Server System This section describes how to convert a DECdns clerk system into a DECdns server system. ________________________ Note ________________________ This description assumes that the DECdns namespace name that you specify in the dialog section is not currently configured in your network and that it is your intention to configure the first occurrence of this namespace on your system. ______________________________________________________ Configuration Dialog Processing To convert a DECdns clerk system to a DECdns server, you must install the DECdns server component using the PCSI installation procedure (see Chapter 3). You can install the DECdns server before or after the initial network configuration. Modifying a Current Configuration 7-17 Modifying a Current Configuration 7.6 Changing the Node Name/Namespace Name o If you installed the DECdns server software before you did the initial configuration, the net$configure procedure renamed the sys$startup:dns$server_startup.com file to dns$server_startup.com-disabled during the initial configuration. The procedure informs you that this was done and asks if you want to change the system into a DECdns server: A SYS$STARTUP:DNS$SERVER_STARTUP.COM-DISABLED file has been located. This indicates that the DECdns server software has been installed, but this system was previously configured as a DECdns clerk. Answer YES to the next question if you want to rename this file to DNS$SERVER_STARTUP.COM and configure the node as a DNS Server. If you take the default, this node will remain a DNS Clerk. * Do you want to change this system into a DECdns server? [NO]: Answer NO to leave your system configured as a DECdns clerk system. Answer YES to rename the sys$startup:dns$server_startup.com-disabled file to sys$startup:dns$server_startup.com and configure your system as a DECdns server. o If you installed the DECdns server option after the initial configuration, the procedure indicates that it has found a sys$startup:dns$server_startup.com file and asks you if you want to rename the file to sys$startup:dns$server_startup.com-disabled: A SYS$STARTUP:DNS$SERVER_STARTUP.COM file has been located. If you do not want to configure this node as a DECdns server, you may now choose to rename that file to DNS$SERVER_STARTUP.COM-DISABLED. Answer YES to the next question if you want to configure this node as a DECdns clerk. If you take the default, this node will be configured as a DECdns server. Do you want to rename DNS$SERVER_STARTUP.COM to .COM-DISABLED? [NO]: Answer YES to rename the sys$startup:dns$server_ startup.com file to sys$startup:dns$server_startup.com- disabled and to leave your system configured as a DECdns clerk system. Answer NO to leave the sys$startup:dns$server_startup.com as is and to configure your system as a DECdns server. 7-18 Modifying a Current Configuration Modifying a Current Configuration 7.6 Changing the Node Name/Namespace Name Whether you installed the DECdns server software before or after the initial configuration, if you elect to create a new DECdns server system, the procedure warns you that you must specify DECdns as the primary name service when you configure a DECdns server for the first time: Your node will be configured as a DNS Server. Since you are configuring this DNS server for the first time, you must specify DECdns as the primary naming service. If you did not enter DECdns as the primary name service, the procedure displays the following warning and gives you a chance to re-enter the name service list with DECdns as the primary name service: You must specify DECdns as the primary naming service while configuring a DECdns server for the first time. If you answer NO to the next question, then NET$CONFIGURE will rename the SYS$STARTUP: DNS$SERVER_STARTUP.COM file to .COM-DISABLED so that the node will not boot as a DNS server until it has been configured properly. * Do you want to re-enter your list of directory services? [YES]: If you specify DECdns as the primary naming service, configuration dialog processing continues as shown in the configuration dialog processing section of Section 7.6.3. If you do not re-enter the list of directory services with DECdns as the first name service, the procedure renames the DECdns server startup file back to .com-disabled and the conversion to a DECdns server is aborted. If you do not have a proper license for the DECdns server software (DVNETEXT for OpenVMS I64 and OpenVMS Alpha systems or DVNETRTG for OpenVMS VAX systems), the procedure displays a message explaining that you need a license, renames the dns$server_startup.com file to dns$server_ startup.com-disabled, and reprompts you for a list of directory services: OpenVMS I64 and OpenVMS Alpha DECdns servers require the DVNETEXT license. This license is not yet loaded so this system will be configured as a DECdns clerk. To reconfigure this system as a server, please load this license and run NET$CONFIGURE again choosing Option 2. Modifying a Current Configuration 7-19 Modifying a Current Configuration 7.6 Changing the Node Name/Namespace Name %RENAME-I-RENAMED, SYS$SYSROOT:[SYS$STARTUP]DNS$SERVER_STARTUP.COM;1 renamed to SYS$SYSROOT:[SYS$STARTUP]DNS$SERVER_STARTUP.COM-DISABLED;1 * Enter the directory services to use on the system [LOCAL] : ________________________ Note ________________________ For the purposes of this example, the DECdns full name was specified using a null directory path: * Enter the full name for directory service DECDNS : HP:.ASHFLD The net$configure procedure does not support automatic creation of any directories in the directory path of the node's DECdns full name; only node object creations in the root directory ( . ) are supported. If you need to specify a directory path, enter it in the dialog. When the automatic node registration fails, use the DECdns Control Program (DNSCP) to create the directories in the directory path (see the "Managing Directories" chapter in the HP DECnet- Plus for OpenVMS DECdns Management manual) and then use decnet_register to register the node (see the "Managing Name Service Searches and Information" chapter in the HP DECnet-Plus for OpenVMS Network Management manual). ______________________________________________________ Namespace Selection Processing To configure a new namespace, the net$configure procedure calls dns$configure.com twice: first to configure the system with the Local namespace as primary (this is a requirement for namespace creation), then to configure the system with the new namespace as primary: sys$manager:net$dns_clerk_startup.ncl changed to use the new default namespace. Your default namespace nickname is LOCAL. Your default namespace NSCTS is 08-00-2B-0D-C0-9D-5F-FA-A9-88-43-46-95-00. The namespace you specified was HP. When dns$configure.com is called with the new namespace, it indicates that the namespace is not currently being served on the LAN, displays a list of all the known namespaces, and asks you to choose a known namespace or reject the list entirely: 7-20 Modifying a Current Configuration Modifying a Current Configuration 7.6 Changing the Node Name/Namespace Name %DNS-E-NOMATNS, The specified namespace is not being served on your LAN. please choose from the following list [ 1] AUTUMN [ 2] DEC [ 3] DOMAIN [ 0] - Reject this list - Pick a number from the list: 0 When you see this display, enter 0 and press Return to reject the list of known namespaces. The procedure then asks if you want to create a new namespace: If you are installing DECnet-Plus for OpenVMS for the first time and you want to create a namespace, type Y. If you want to attempt a WAN connection to a remote DECdns server, type N (default) at the following prompt: Do you want to proceed with creating a new namespace [n]: y If you answer NO, the dns$configure.com procedure returns an error to the net$configure procedure. The transaction is aborted and the main options menu is redisplayed. If you answer YES, the dns$configure.com procedure asks you for the clearinghouse name to use for the new namespace, starts the DECdns server process, and informs you that the default namespace has been set to the new namespace: Your next input will determine the name of the clearinghouse in your namespace HP. Enter the clearinghouse name as alphanumeric and/or underscore characters. Enter a simple name for the clearinghouse: HP_CH Node 0 at 2003-03-28-17:40:35.901-04:00I675.395 Creating DECdns Server process ... %RUN-S-PROC_ID, identification of created process is 00000082 Your default namespace nickname is HP. Node 0 at 2003-03-28-17:40:46.777-04:00I675.396 Namespace Configuration Processing Modifying a Current Configuration 7-21 Modifying a Current Configuration 7.6 Changing the Node Name/Namespace Name During namespace selection processing, the dns$configure.com procedure only creates the new namespace. The net$configure procedure now populates the namespace with the initial groups and directories required of all namespaces (see the DECnet-Plus Planning Guide for more information about how DECnet-Plus uses the DECdns namespace): %NET$CONFIGURE-I-NEWNAMESPACE, a new namespace has been created %NET$CONFIGURE-I-ADDGROUP, adding .WorldRead_Group to the new namespace Create the initial namespace directories. Press Ctrl/Z at any question to cancel the initialization. * Phase IV prefix value [afi:idi:predsp, Def=49::]: * Maximum Phase IV area to use [1-63, Def=63]: The DECdns namespace groups and directories will now be created. This might take up to 67 minutes or more, depending on the speed of the DECdns server system and the amount of traffic on the network. Creating the HP:.DNA_Registrar group. Creating the HP:.DNA_BackTranslation directory. Creating the HP:.DNA_BackTranslation.%X49 directory. Creating the HP:.DNA_BackTranslation.%X49.%X0001 directory. Creating the HP:.DNA_BackTranslation.%X49.%X0002 directory. . . . Creating the HP:.DNA_NodeSynonym directory. Creating the HP:.DTSS_GlobalTimeServers directory. DECdns namespace initialization for DECnet use is complete. The procedure then gives you a summary of further actions you must take to make the namespace fully functional and displays a summary of the directories it created (and any errors encountered during their creation): If this is the first time you have initialized the namespace for DECnet use, use SYS$SYSTEM:DECNET_REGISTER.EXE to: * Press Return to continue - Create a command file to automatically register previously defined Phase IV nodes. Execute this command file before you manually register any other nodes using SYS$SYSTEM:DECNET_REGISTER.EXE. 7-22 Modifying a Current Configuration Modifying a Current Configuration 7.6 Changing the Node Name/Namespace Name - Create any directories you need for node names that should be registered immediately, according to your namespace design. This includes the node you are currently running on. - Be sure to add backtranslation directories for any non Phase IV areas/IPDs. Failure to do so will lead to Backtranslation Failures. Once you've added the necessary backtranslation directories, you may need to use the ncl flush session control naming cache entry "*" command. - Change the local node's registered name from its default name to its final full name. The local node will be registered as a Phase IV node with a default name when you execute the Phase IV node registration command file above. - Change the currently registered names of other nodes from their default names to their final full names when appropriate (for example, when they are upgraded to run DECnet-Plus software). Continue to use SYS$SYSTEM:DECNET_REGISTER.EXE to: - Create any additional directories you need for node names, as new nodes are brought up on the network. - Register new nodes as they are brought up on the network. - Add members to the HP:.DNA_Registrar access control group. * Press Return to continue Additionally, you can use the DECdns control utility to: - Add specific access control to individual directories, objects, and soft links. - Create replicas of directories. The following were created: Group: HP:.DNA_Registrar Directory: HP:.DNA_BackTranslation Directory: HP:.DNA_BackTranslation.%X49 Directories: HP:.DNA_BackTranslation.%X49.* Directory: HP:.DNA_NodeSynonym Directory: HP:.DTSS_GlobalTimeServers * Press Return to continue %NET$CONFIGURE-I-CREATEINITDIR, created initial namespace directories Modifying a Current Configuration 7-23 Modifying a Current Configuration 7.6 Changing the Node Name/Namespace Name Now that the new namespace is properly configured for DECnet-Plus use, the procedure registers your system in the new namespace using the information you supplied during configuration dialog processing: Directory Service: DECdns Registering the node: HP:.ASHFLD %NET$CONFIGURE-I-REGSUCCESS, node has been successfully registered in the HP: directory service Based on the answers provided during configuration dialog processing, the configuration procedure executes the new name service searchpath NCL script, renames the node, modifies the Local namespace entry, flushes the CDI cache, updates the node's address towers, and updates the backtranslation softlink for the node: %NET$CONFIGURE-I-NODERENAMED, node successfully renamed to HP:.ASHFLD Directory Service: Local name file Modifying the node: LOCAL:.ASHFLD Modifying the node towers %NET$CONFIGURE-I-FLUSHCACHE, flushing selected cache entries %NET$CONFIGURE-I-TOWERSUPDATED, updated address towers for node %NET$CONFIGURE-I-BCKTRNUPDATED, updated backtranslation softlink for node The procedure then displays the configuration summary, recalculates the NCL script file checksums, and redisplays the main options menu: Summary of Configuration Node Information: 7-24 Modifying a Current Configuration Modifying a Current Configuration 7.6 Changing the Node Name/Namespace Name Node Type: ENDNODE Directory Services Chosen: DECDNS Primary Directory Service: DECDNS DECdns Full name: HP:.ASHFLD DECdns Node Type: Server Node Synonym: ASHFLD Phase IV Address: 24.121 Phase IV Prefix: 49:: Autoconfiguration of Network Addresses: Enabled Session Control Address Update Interval: 10 Routing ESHello Timer: 600 Routing ES Cache Size: 512 . . . %NET$CONFIGURE-I-MODCHECKSUM, checksumming NCL management scripts modified by NET$CONFIGURE %NET$CONFIGURE-I-CONFIGCOMPLETED, DECnet-Plus for OpenVMS configuration completed Configuration Options for Node ASHFLD [0] Exit this procedure [1] Perform an entire configuration [2] Change naming information Modifying a Current Configuration 7-25 Modifying a Current Configuration 7.6 Changing the Node Name/Namespace Name ________________________ Note ________________________ If the node registration fails, use the decnet_ register tool to register the node (the procedure does not create a decnet_register import file when creating a local namespace): $ net_register = "$sys$system:decnet_register" $ net_register register node HP:.ASHFLD directory DECDNS - _$ towers {SC3/NSP/phaseiv-address,SC3/TP4/phaseiv-address} SYNONYM ASHFLD ______________________________________________________ 7.6.6 Converting a DECdns Server to a DECdns Clerk System This section describes how to convert a DECdns server system to a DECdns clerk system. Configuration Dialog Processing The procedure checks for the existence of a valid DECdns server configuration (by searching for the sys$manager:dns_ files.txt file). If it finds the file and the file passes verification testing, the procedure displays the following message and asks if you want to convert the server to a clerk: The directory pointed to by SYS$MANAGER:DNS_FILES.TXT is valid. This indicates that the node has been previously configured as a DECdns server. Answer YES to the next question if you would like to rename the the DNS$SERVER_STARTUP.COM file to .COM-DISABLED to change this node to a DECdns clerk. If you take the default, the node will be configured as a DECdns server. Do you want to rename DNS$SERVER_STARTUP.COM to .COM-DISABLED.COM? [NO]: Answer NO to leave your system configured as a DECdns server system. Answer YES to rename the sys$startup:dns$server_startup.com file to sys$startup:dns$server_startup.com-disabled and configure your system as a DECdns clerk. In both cases, configuration dialog processing continues as shown in the configuration dialog processing section of Section 7.6.3. 7-26 Modifying a Current Configuration Modifying a Current Configuration 7.6 Changing the Node Name/Namespace Name ________________________ Notes ________________________ Except for renaming the dns$server_startup.com file, the net$configure procedure does not delete any configuration information associated with the existing DECdns server configuration. Therefore, when you follow the procedures given in Section 7.6.7, the DECdns server is fully restored to its former configuration. The net$configure procedure does not shut down the DECdns server. To shut down the server without having to reboot the system, invoke the sys$startup:dns$server_shutdown.com procedure. ______________________________________________________ Namespace Selection Processing Assuming that no other changes are made during configuration dialog processing, namespace selection processing verifies that it can communicate with another DECdns server containing the same namespace and then calls the dns$configure procedure to reconfigure the clerk for the namespace: sys$manager:net$dns_clerk_startup.ncl changed to use the new default namespace. Your default namespace nickname is HP. Your default namespace NSCTS is AA-00-04-00-DE-11-A0-AA-F9-6F-56-DE-8E-00. Namespace Configuration Processing The procedure reruns the name service searchpath NCL script. Whenever a DECdns namespace is involved the process renames the node, flushes the cache, updates the address towers, and updates the backtranslation softlink: %NET$CONFIGURE-I-NODERENAMED, node successfully renamed to HP:.ASHFLD %NET$CONFIGURE-I-FLUSHCACHE, flushing selected cache entries %NET$CONFIGURE-I-TOWERSUPDATED, updated address towers for node %NET$CONFIGURE-I-BCKTRNUPDATED, updated backtranslation softlink for node The procedure then displays the configuration summary, recalculates the NCL script file checksums, and redisplays the main options menu: Modifying a Current Configuration 7-27 Modifying a Current Configuration 7.6 Changing the Node Name/Namespace Name Summary of Configuration Node Information: Node Type: ENDNODE Directory Services Chosen: DECDNS Primary Directory Service: DECDNS DECdns Full name: HP:.ASHFLD DECdns Node Type: Clerk Node Synonym: ASHFLD Phase IV Address: 24.121 Phase IV Prefix: 49:: Autoconfiguration of Network Addresses: Enabled Session Control Address Update Interval: 10 Routing ESHello Timer: 600 Routing ES Cache Size: 512 . . . %NET$CONFIGURE-I-MODCHECKSUM, checksumming NCL management scripts modified by NET$CONFIGURE %NET$CONFIGURE-I-CONFIGCOMPLETED, DECnet-Plus for OpenVMS configuration completed Configuration Options for Node ASHFLD [0] Exit this procedure [1] Perform an entire configuration [2] Change naming information 7.6.7 Reverting a DECdns Clerk System Back to a DECdns Server System This section describes how to revert back to a previous DECdns server configuration after converting a DECdns server system to a DECdns clerk system. Configuration Dialog Processing When you previously converted the system to a DECdns clerk system, the net$configure procedure renamed the sys$startup:dns$server_startup.com file to dns$server_ startup.com-disabled during the conversion. The procedure informs you that this was done and asks if you want to change the system back into a DECdns server: 7-28 Modifying a Current Configuration Modifying a Current Configuration 7.6 Changing the Node Name/Namespace Name A SYS$STARTUP:DNS$SERVER_STARTUP.COM-DISABLED file has been located. This indicates that the DECdns server software has been installed, but this system was previously configured as a DECdns clerk. Answer YES to the next question if you want to rename this file to DNS$SERVER_STARTUP.COM and configure the node as a DNS Server. If you take the default, this node will remain a DNS Clerk. * Do you want to change this system into a DECdns server? [NO]: Answer NO to leave your system configured as a DECdns clerk system. Answer YES to rename the sys$startup:dns$server_ startup.com-disabled file to sys$startup:dns$server_ startup.com and reconfigure your system as a DECdns server. If you choose to convert the system back to a DECdns server, the procedure checks for the existence of a valid DECdns server configuration (by searching for the sys$manager:dns_files.txt file). If it finds the file and the file passes verification testing, the procedure displays the following message: The directory pointed to by SYS$MANAGER:DNS_FILES.TXT is valid. This indicates that the node has been previously configured as a DECdns server. If the procedure does not find the configuration file or the file does not pass verification testing, the procedure treats this configuration as a new conversion to a DECdns server. See the configuration dialog processing section in Section 7.6.5 for information about limitations on the directory service list in this case (see the information directly following the bulleted list). Assuming that the configuration file is found and that it passes verification testing, the procedure begins the standard directory service/node name dialog by asking for the directory services to use and, based on the answer, the DECdns full name: * Enter the directory services to use on the system [LOCAL] : decdns,local * Enter the full name for directory service DECDNS : hp:.ashfld Because you have specified a DECdns name on a system that already has a DECdns server configuration, the procedure checks the server's clearinghouses to make sure that you are specifying a namespace already served by this system: Modifying a Current Configuration 7-29 Modifying a Current Configuration 7.6 Changing the Node Name/Namespace Name NET$CONFIGURE is searching for pre-existing clearinghouses on this DNS Server. Clearinghouse: HP:.HP_CH Note that this check requires that the net$configure procedure start the DECdns server using the newly renamed sys$startup:dns$server_startup.com file. If you are running net$configure on the console and you have events enabled, you should see one or more Clearinghouse Enabled events as the DECdns server enables the existing clearinghouses on the server. The net$configure procedure does not support creation of more than one namespace on a system. If it cannot find a clearinghouse for the namespace you entered, it displays the following message: There is no clearinghouse on this DNS Server for the namespace you specified in your DECdns fullname. To proceed with this rename, you may now provide a different DECdns fullname -- one that is in a namespace displayed above. If you wish to use a namespace or clearinghouse name not previously known to this DNS Server, then this rename cannot proceed until you have manually ensured that the existing clearinghouse has been deleted. * Do you want to provide a different DECdns fullname? [YES]: If you answer YES, the procedure returns to the DECdns fullname prompt and, after you enter a DECdns full name using the proper namespace, configuration dialog processing continues: * Enter the full name for directory service LOCAL [LOCAL:.ASHFLD] : * What is the synonym name for this node? [ASHFLD] : * Naming cache timeout value? [30-00:00:00] : * Session Control Address Update Interval ? [10] : * Naming cache checkpoint interval? [08:00:00] : If you answer NO, the procedure displays the following message and aborts the rename operation: 7-30 Modifying a Current Configuration Modifying a Current Configuration 7.6 Changing the Node Name/Namespace Name Please refer to Section 9.6 of DECnet-Plus DECdns Management manual, for instructions on Deleting a Clearinghouse before invoking NET$CONFIGURE again to rename this DNS Server. %NET$CONFIGURE-I-LASTTRANSABORT, last transaction aborted Namespace Selection Processing The procedure calls dns$configure.com twice: first, to ensure that the system is configured with the Local namespace as primary, then to configure the system with the DECdns namespace as primary: sys$manager:net$dns_clerk_startup.ncl changed to use the new default namespace. Your default namespace nickname is LOCAL. Your default namespace NSCTS is 08-00-2B-0D-C0-9D-5F-FA-A9-88-43-46-95-00. sys$manager:net$dns_clerk_startup.ncl changed to use the new default namespace. Your default namespace nickname is HP. Your default namespace NSCTS is 00-00-F8-25-5A-72-D1-9D-2D-09-04-3C-A3-00. Namespace Configuration Processing Based on the answers provided during configuration dialog processing, the configuration procedure executes the new name service searchpath NCL script, renames the node, modifies the Local namespace entry, flushes the CDI cache, updates the node's address towers, and updates the backtranslation softlink for the node: %NET$CONFIGURE-I-NODERENAMED, node successfully renamed to HP:.ASHFLD Directory Service: Local name file Modifying the node: LOCAL:.ASHFLD Modifying the node towers %NET$CONFIGURE-I-FLUSHCACHE, flushing selected cache entries %NET$CONFIGURE-I-CHECKPOINTWAIT, waiting for CDI to write the node name to the CDI cache file %NET$CONFIGURE-I-CHECKPOINTDONE, the node name has been written to SYS$SYSTEM:DECNET$CDI_CACHE.DAT %NET$CONFIGURE-I-TOWERSUPDATED, updated address towers for node %NET$CONFIGURE-E-BCKTRNUPDATED, updated backtranslation softlink for node Modifying a Current Configuration 7-31 Modifying a Current Configuration 7.6 Changing the Node Name/Namespace Name The procedure then displays the configuration summary, recalculates the NCL script file checksums, and redisplays the main options menu: Summary of Configuration Node Information: Node Type: ENDNODE Directory Services Chosen: DECDNS Primary Directory Service: DECDNS DECdns Full name: HP:.ASHFLD DECdns Node Type: Server Node Synonym: ASHFLD Phase IV Address: 24.121 Phase IV Prefix: 49:: Autoconfiguration of Network Addresses: Enabled Session Control Address Update Interval: 10 Routing ESHello Timer: 600 Routing ES Cache Size: 512 . . . %NET$CONFIGURE-I-MODCHECKSUM, checksumming NCL management scripts modified by NET$CONFIGURE %NET$CONFIGURE-I-CONFIGCOMPLETED, DECnet-Plus for OpenVMS configuration completed Configuration Options for Node ASHFLD [0] Exit this procedure [1] Perform an entire configuration [2] Change naming information 7.6.8 Using the DECdns Namespace as Secondary on a DECdns Server System This section describes how to configure a DECdns server to run with the primary directory service set to a namespace other than DECdns. Configuration Dialog Processing 7-32 Modifying a Current Configuration Modifying a Current Configuration 7.6 Changing the Node Name/Namespace Name The following example shows the first portion of the dialog used to change the node from using DECdns as the primary directory service to using the Local namespace as the primary directory service (DOMAIN as primary is virtually identical): * Which configuration option to perform? [1] : 2 * Enter the directory services to use on the system [DECDNS,LOCAL] : local,decdns At this point, the configuration procedure displays a message indicating that HP strongly recommends using DECdns as the primary directory service on DECdns servers: Hewlett-Packard recommends that you specify DECdns as the primary naming service on a DECdns server, but the list of directory services you entered does not start with DECdns. Answer NO to the following question if you want to ignore this recommendation and proceed using the list of directory services you just entered. If you take the default, you will be prompted to re-enter your list of directory services so that you may enter DECdns as the first service in that list. Do you want DECdns as the primary naming service on this DECdns server? [YES]: If you answer YES, the procedure again prompts you for the directory services list. If you answer NO, your original order is accepted and the dialog continues: * Enter the full name for directory service LOCAL [LOCAL:.ASHFLD] : * Enter the full name for directory service DECDNS [HP:.ASHFLD]: Because you have specified a DECdns name on a system that is already configured as a DECdns server, the procedure checks the server's clearinghouses to make sure that you are specifying a namespace already served by this system: NET$CONFIGURE is searching for pre-existing clearinghouses on this DNS Server. Clearinghouse: HP:.HP_CH The net$configure procedure does not support creation of more than one namespace on a system. If it cannot find a clearinghouse for the namespace you entered, it displays the following message: Modifying a Current Configuration 7-33 Modifying a Current Configuration 7.6 Changing the Node Name/Namespace Name There is no clearinghouse on this DNS Server for the namespace you specified in your DECdns fullname. To proceed with this rename, you may now provide a different DECdns fullname -- one that is in a namespace displayed above. If you wish to use a namespace or clearinghouse name not previously known to this DNS Server, then this rename cannot proceed until you have manually ensured that the existing clearinghouse has been deleted. * Do you want to provide a different DECdns fullname? [YES]: If you answer YES, the procedure returns to the DECdns fullname prompt and, after entering a DECdns full name using the proper namespace, configuration dialog processing continues: * Enter the full name for directory service DECDNS [HP:.ASHFLD]: * What is the synonym name for this node? [ASHFLD] : * Naming cache timeout value? [30-00:00:00] : * Session Control Address Update Interval ? [10] : * Naming cache checkpoint interval? [08:00:00] : If you answer NO, the procedure displays the following message and aborts the rename operation: Please refer to Section 9.6 of DECnet-Plus DECdns Management manual, for instructions on Deleting a Clearinghouse before invoking NET$CONFIGURE again to rename this DNS Server. %NET$CONFIGURE-I-LASTTRANSABORT, last transaction aborted Namespace Selection Processing If you choose to configure the DECdns name service as a secondary service, the configuration procedure modifies the DECdns namespace on the system to allow access by the renamed server. It does this by adding access for the LOCAL or DOMAIN namespace based on which namespace is primary. The procedure displays the following message: NET$CONFIGURE is searching for pre-existing clearinghouses on this DNS Server in order to set up access control. 7-34 Modifying a Current Configuration Modifying a Current Configuration 7.6 Changing the Node Name/Namespace Name The procedure then calls the dns$configure.com procedure to configure the DECdns clerk for the new primary namespace: sys$manager:net$dns_clerk_startup.ncl changed to use the new default namespace. Your default namespace nickname is LOCAL. Your default namespace NSCTS is 08-00-2B-0D-C0-9D-5F-FA-A9-88-43-46-95-00 If the net$configure procedure is not successful in setting the new access information, it displays the following message and aborts the transaction: ERROR: NET$CONFIGURE did not succeed in setting up access control for pre-existing clearinghouses on this DNS Server. %NET$CONFIGURE-I-LASTTRANSABORT, last transaction aborted Configuration Options for Node ASHFLD [0] Exit this procedure [1] Perform an entire configuration [2] Change naming information . . . Namespace Configuration Processing Based on the answers provided during configuration dialog processing, the configuration procedure executes the new name searchpath NCL script, modifies the Local namespace entry, renames the node, and flushes the cache: Directory Service: Local name file Modifying the node: LOCAL:.ASHFLD Modifying the node towers %NET$CONFIGURE-I-NODERENAMED, node successfully renamed to LOCAL:.ASHFLD %NET$CONFIGURE-I-FLUSHCACHE, flushing selected cache entries The procedure then displays the configuration summary, recalculates the NCL script file checksums, and redisplays the main options menu: Modifying a Current Configuration 7-35 Modifying a Current Configuration 7.6 Changing the Node Name/Namespace Name Summary of Configuration Node Information: Directory Services Chosen: LOCAL,DECDNS Primary Directory Service: LOCAL DECdns Full name: HP:.ASHFLD Local Full name: LOCAL:.ASHFLD Node Synonym: ASHFLD Phase IV Address: 24.900 Phase IV Prefix: 49:: DECdns Node Type: Server Session Control Address Update Interval: 10 Routing Node Type: ENDNODE Autoconfiguration of Network Addresses: Enabled Routing ESHello Timer: 600 Routing ES Cache Size: 512 . . . %NET$CONFIGURE-I-MODCHECKSUM, checksumming NCL management scripts modified by NET$CONFIGURE %NET$CONFIGURE-I-CONFIGCOMPLETED, DECnet-Plus for OpenVMS configuration completed Configuration Options for Node ASHFLD [0] Exit this procedure [1] Perform an entire configuration [2] Change naming information . . . 7.6.9 Configuring a DECdns Server System into an Existing Namespace To configure additional DECdns servers into an existing namespace, you must use the DECdns configuration program, sys$system:dns$configure.exe. Be sure to refer to the HP DECnet-Plus for OpenVMS DECdns Management manual for DECdns access control information and for complete information about using the DECdns configuration program to configure a DECdns server into an existing namespace. 7-36 Modifying a Current Configuration Modifying a Current Configuration 7.6 Changing the Node Name/Namespace Name 7.6.9.1 Configuring a DECdns Server in a DNS Version 1 Namespace If you are already using a DNS Version 1 namespace (a namespace created with Version 1 of the Distributed Name Service), you can configure one or more DECdns Version 2 servers into that namespace. Before you try to configure a DECdns server into a DNS Version 1 namespace, make sure that the namespace has been prepared for use by DECnet- Plus (see Section B.3). For complete information on how to prepare a DNS Version 1 namespace for use by DECnet-Plus, refer to the HP DECnet-Plus for OpenVMS DECdns Management manual for DECdns access control information. ________________________ Note ________________________ The DECdns configuration program allows you to convert your DNS Version 1 clearinghouses to DECdns Version 2 format. By doing so, you get the improved performance offered by the DECdns Version 2 server while using your existing DNS Version 1 namespace. If you intend to convert your DNS Version 1 clearinghouses to DECdns Version 2 format, HP strongly recommends that you do not configure DECnet-Plus for OpenVMS on any of your DNS Version 1 server nodes until you have prepared your DNS Version 1 namespace for use by DECnet-Plus. ______________________________________________________ 7.7 Configuring Devices To configure devices, select option 3 from the main options menu: * Which configuration option to perform? [1] : 3 The dialog for a configuration modification is identical to the initial dialog. See Section 6.6 for the entire device dialog. As with the initial configuration dialog, if X.25 or WANDD components are found and have not been configured, the procedure gives you a chance to configure them. Once you have completed the device dialog, the procedure displays a summary of the configuration and asks if you want to configure the new NCL scripts. Proceed to Section 7.17 for more information. Modifying a Current Configuration 7-37 Modifying a Current Configuration 7.8 Configuring the NSP and OSI Transports 7.8 Configuring the NSP and OSI Transports To configure the NSP transport, the OSI transport, or both transports, select option 4 from the main options menu: * Which configuration option to perform? [1] : 4 BASIC The BASIC option begins by asking if you want to configure the NSP transport: * Configure the NSP Transport? [YES] : If you answer YES, the procedure displays the DEFAULT transport settings for the NSP transport and asks if you want to replace the existing transport values with the default values: Since you are using the BASIC option, if you answer YES to the next question, the NSP transport will be reconfigured using the default values which are: Maximum number of logical links: 200 Maximum Transmit and Receive Window: 20 Maximum Receive Buffers: 4000 Flow Control Policy: Segment Flow Control If you intend to customize the transports, then use the ADVANCED option instead. * Do you want to replace the existing NSP transport script? [NO] : If you answer YES, the NSP transport is reconfigured with the default values shown in the display. If you answer NO, the NSP configuration is left unchanged. Next, the procedure asks the same question for the OSI transport: * Configure the OSI Transport or run over TCP/IP? [YES] : If you answer YES, the procedure displays the DEFAULT transport settings for the OSI transport and asks if you want to replace the existing transport values with the default values: 7-38 Modifying a Current Configuration Modifying a Current Configuration 7.8 Configuring the NSP and OSI Transports Since you are using the BASIC option, if you answer YES to the next question, the OSI transport will be reconfigured using the default values which are: Maximum number of logical links: 200 Maximum Transmit and Receive Window: 20 Maximum Receive Buffers: 4000 OSI applications over TCP/IP: Enabled DECnet applications over TCP/IP: Enabled If you intend to customize the transports, then use the ADVANCED option instead. * Do you want to replace the existing OSI transport script? [NO] : If you answer YES, the OSI transport is reconfigured with the default values shown in the display. If you answer NO, the OSI configuration is left unchanged. Once you have completed the transport dialog, the procedure displays a summary of the configuration and asks if you want to configure the new NCL scripts. Proceed to Section 7.17 for more information. ADVANCED The ADVANCED option begins by asking if you want to configure the NSP transport: * Configure the NSP Transport? [YES] : If you answer YES, the procedure displays the CURRENT transport settings for the NSP transport and asks if you want to reconfigure the existing transport values: Answer YES to the next question if you wish to change the current NSP transport configuration: Maximum number of logical links: 200 Maximum Transmit and Receive Window: 20 Maximum Receive Buffers: 4000 Flow Control Policy: Segment Flow Control * Do you want to replace the existing NSP transport script? [NO] : If you answer YES, you are prompted for the new values. If you answer NO, the NSP configuration is left unchanged. Modifying a Current Configuration 7-39 Modifying a Current Configuration 7.8 Configuring the NSP and OSI Transports Next, the procedure asks the same question for the OSI transport: * Configure the OSI Transport or run over TCP/IP? [YES] : If you answer YES, the procedure displays the CURRENT transport settings for the OSI transport and asks if you want to reconfigure the existing transport values: Answer YES to the next question if you wish to change the current NSP transport configuration: Maximum number of logical links: 200 Maximum Transmit and Receive Window: 20 Maximum Receive Buffers: 4000 OSI applications over TCP/IP: Enabled DECnet applications over TCP/IP: Enabled * Do you want to replace the existing OSI transport script? [NO] : If you answer YES, you are prompted for the new values. If you answer NO, the OSI configuration is left unchanged. With the exception of the additional dialog shown here, the questions asked during a reconfiguration are identical to the initial configuration questions, including the section used to create additional OSI templates. If you elect to reconfigure either or both transports, see Section 6.7 for the prompts used in this section and for information about how to respond to the prompts. Note that the ADVANCED option of the reconfiguration dialog omits the opening message shown at the beginning of Section 6.7. _______________________ Warning _______________________ If you select this option and then indicate that you don't want to configure either transport, the procedure issues a warning and asks you to confirm your decision: %NET$CONFIGURE-W-NOTRANSPORTS, no transports selected * Are you sure? [NO] : y If you answer YES, all transport configuration information is lost. The configuration procedure creates empty NCL startup script files for both transports. To create a usable configuration, you 7-40 Modifying a Current Configuration Modifying a Current Configuration 7.8 Configuring the NSP and OSI Transports must run the configuration procedure again to create valid transport scripts. ______________________________________________________ Once you have completed the transport dialog, the procedure displays a summary of the configuration and asks if you want to configure the new NCL scripts. Proceed to Section 7.17 for more information. 7.9 Configuring the Time Zone Differential Factor (DECdts) To configure DECdts, select option 5 from the main options menu: * Which configuration option to perform? [1] : 5 7.9.1 DECdts Overview DECdts binary time values are based on Coordinated Universal Time (UTC), an international time standard that has largely replaced Greenwich Mean Time (GMT) as a reference. For most measurement purposes, UTC is the equivalent of GMT. Time zones are still determined by their relationship to the prime meridian in Greenwich, England. The local time in each time zone or locale is determined by its offset, or differential, from the Greenwich time zone. This value is commonly expressed as a time differential factor (TDF) of a positive or negative number of hours. When you initially configure an OpenVMS system, you must determine its geographical location and designate its time zone rule (TZR), which is based on the location. The TZR contains the abbreviated name of the system's time zone and the applicable TDF, so that DECdts can calculate UTC from the system (local) time during the initial configuration of the DECdts software. The TZR also contains information on any seasonal adjustments to the TDF that normally apply in the selected time zone. If you want to select the commonly accepted TZR for a given area and system, you can use the net$configure procedure menus to select the geographical location of the system. Based on your selection, the net$configure procedure automatically sets the TZR. After you configure your system, it displays the local time even though the DECdts software uses UTC in the background. Because the default Modifying a Current Configuration 7-41 Modifying a Current Configuration 7.9 Configuring the Time Zone Differential Factor (DECdts) value of the DECdts management attribute Automatic TDF Change is set to TRUE, DECdts also changes the displayed local time automatically if there is a seasonal adjustment to the system's TDF. Additionally, when you reconfigure the DECdts software, you are given the option of setting the system's time to UTC time. The following resources provide additional information about time management and use on OpenVMS systems: o HP DECnet-Plus for OpenVMS DECdts Management - discusses what DECdts is and how it works, managing DECdts, troubleshooting DECdts, and provides a command reference for all commands used to manage DECdts. o HP OpenVMS System Manager's Utility Guide ("Setting System Time" chapter) - discusses how time is managed on OpenVMS systems that do not use DECdts. Much of the information about how to configure DECdts is common to DECdts and OpenVMS and is documented in this manual. Specifically, this chapter discusses using the utc$time_ setup command procedure to set your system's time zone information. This procedure is used by the DECdts time zone configuration procedure. o Compaq C Run-Time Library Utilities Reference Manual (the "Creating Time Zone Conversion Information" section in the "Overview" chapter) - discusses using the Zone Information Compiler (ZIC) to create the binary time zone files required by OpenVMS and DECdts. o HP C Run-Time Library Reference Manual for OpenVMS Systems ("Date/Time Functions" chapter and tzset function description in the "Reference Section") - describes how C programs can make use of the date and time functions in the C run-time library. The tzset function description is useful in understanding the syntax used in the SYS$TIMEZONE_RULE logical name. 7-42 Modifying a Current Configuration Modifying a Current Configuration 7.9 Configuring the Time Zone Differential Factor (DECdts) 7.9.2 Selecting the DECdts Configuration Option After you invoke option 5, the net$configure procedure invokes the dtss$config procedure. The dtss$config procedure begins by displaying messages indicating that it is deassigning the four current SYS$TIMEZONE_xxx logical names and shutting down DECdts (the "Node 0 DTSS" messages come from the NCL commands used by the procedure): DTSS$CONFIG-I-LOGS Deassigning system timezone logicals DTSS$CONFIG-I-STOPDTS Deleting the DTSS Entity Node 0 DTSS at 1995-08-04-18:36:19.740+00:00Iinf Node 0 DTSS at 1995-08-04-18:36:23.960+00:00Iinf The dtss$config procedure then invokes the dtss$install_ timezone_rule procedure. This procedure is also invoked during the initial system configuration. However, during initial configuration the procedure usually gets the time zone rule from the SYS$LOCALTIME system logical name so no menu is displayed. In a reconfiguration, the procedure is called with a parameter that forces it to override the SYS$LOCALTIME system logical name and display an options menu: Timezone Options: [0] Exit Timezone Configuration [1] Choose a timezone using menus [2] Use Universal Coordinated Time (UTC) [3] Define your own timezone rule * Enter an option number [1] : The following sections explain each of the DECdts menu options. ________________________ Note ________________________ Changes made to DECdts take effect immediately. ______________________________________________________ Modifying a Current Configuration 7-43 Modifying a Current Configuration 7.9 Configuring the Time Zone Differential Factor (DECdts) 7.9.3 Choosing a Time Zone Using Menus Option 1 of the Timezone Options menu invokes the OpenVMS sys$manager:utc$time_setup procedure to allow you to choose the time zone rule for the system by using a hierarchy of geographically-based menus. DECdts uses the time zone you select to determine the time zone rule it should use to automatically convert UTC to the local time whenever the time is displayed. To specify a time zone rule by choosing your geographical region, select option 1 from the timezone options menu: * Enter an option number [1] : The procedure displays a menu of continental regions: Configuring the Local Time Zone TIME ZONE SPECIFICATION -- MAIN Time Zone Menu "*" indicates a menu 0* GMT 1* AFRICA 17) EST 33) IRAN 49) PORTUGAL 2* AMERICA 18) EST5EDT 34) ISRAEL 50) PRC 3* ANTARCTICA 19* ETC 35) JAMAICA 51) PST8PDT 4* ARCTIC 20* EUROPE 36) JAPAN 52) ROC 5* ASIA 21) FACTORY 37) KWAJALEIN 53) ROK 6* ATLANTIC 22) GB-EIRE 38) LIBYA 54) SINGAPORE 7* AUSTRALIA 23) GB 39) MET 55* SYSTEMV 8* BRAZIL 24) GMT-0 40* MEXICO 56) TURKEY 9* CANADA 25) GMT 41* MIDEAST 57) UCT 10) CET 26) GMT0 42) MST 58) UNIVERSAL 11* CHILE 27) GMTPLUS0 43) MST7MDT 59* US 12) CST6CDT 28) GREENWICH 44) NAVAJO 60) UTC 13) CUBA 29) HONGKONG 45) NZ-CHAT 61) W-SU 14) EET 30) HST 46) NZ 62) WET 15) EGYPT 31) ICELAND 47* PACIFIC 63) ZULU 16) EIRE 32* INDIAN 48) POLAND Press "Return" to redisplay, enter "=" to search or "?" for help, or Select the number above that best represents the desired time zone: 59 US Time Zone Menu "*" indicates a menu 7-44 Modifying a Current Configuration Modifying a Current Configuration 7.9 Configuring the Time Zone Differential Factor (DECdts) 0* RETURN TO MAIN TIME ZONE MENU 1) ALASKA 5) EAST-INDIANA 9) MICHIGAN 13) SAMOA 2) ALEUTIAN 6) EASTERN 10) MOUNTAIN 3) ARIZONA 7) HAWAII 11) PACIFIC-NEW 4) CENTRAL 8) INDIANA-STARKE 12) PACIFIC Press "Return" to redisplay, enter "=" to search or "?" for help, or Select the number above that best represents the desired time zone: 6 You selected US / EASTERN as your time zone. Is this correct? (Yes/No) [YES]: Enter the option (and, if necessary, the suboption) corresponding to the region where the system resides. In the example, the system is in the eastern United States. After you make a selection, the following actions occur: 1. The utc$time_setup procedure sets the SYS$LOCALTIME system logical name and returns control to the dtss$install_timezone_rule procedure. 2. Using the value in the SYS$LOCALTIME system logical name, the dtss$install_timezone_rule procedure creates the dtss$utc_startup.com procedure. This procedure defines the four SYS$TIMEZONE_xxx system logical names. The procedure is invoked each time the system reboots. The dtss$install_timezone_rule procedure returns control to the dtss$config procedure. 3. The dtss$config procedure invokes the newly-created dtss$utc_startup.com procedure to define the four SYS$TIMEZONE_xxx system logical names on the running system. 4. The procedure then sets the local clock. 5. Next, it executes the sys$startup:dtss$startup.com file to start DECdts. 6. After the DTSS entity is created, it sets the automatic tdf change characteristic (after first disabling the DTSS entity). 7. It then deletes the DTSS entity. 8. Finally, it restarts DECdts. Modifying a Current Configuration 7-45 Modifying a Current Configuration 7.9 Configuring the Time Zone Differential Factor (DECdts) These actions result in the following display: DTSS$CONFIG-I-LOGS Defining system timezone logicals DTSS-I-SETTDF DTSS$SERVICE set new timezone differential DTSS$CONFIG-I-SETLCL Setting Local Clock %RUN-S-PROC_ID, identification of created process is 00000059 Node 0 DTSS at 1995-02-25-08:17:29.520-05:00Iinf Node 0 DTSS at 1995-02-25-08:17:30.790-05:00Iinf Node 0 DTSS at 1995-02-25-08:17:39.978-05:00I0.327 Node 0 DTSS at 1995-02-25-08:17:45.868-05:00I0.328 Characteristics Automatic TDF Change = True Node 0 DTSS at 1995-02-25-08:17:51.898-05:00I0.328 DTSS$CONFIG-I-STARTDTS Restarting the DTSS Entity %RUN-S-PROC_ID, identification of created process is 0000006B Node 0 DTSS at 1995-02-25-08:18:06.138-05:00Iinf Node 0 DTSS at 1995-02-25-08:18:07.488-05:00Iinf ________________________ Note ________________________ If you are running on the console, several OPCOM messages are displayed during this sequence displaying entity status changes and clock synchronization events. ______________________________________________________ This completes changes to the DECdts configuration using option 1. The net$configure procedure returns to the main options menu. 7-46 Modifying a Current Configuration Modifying a Current Configuration 7.9 Configuring the Time Zone Differential Factor (DECdts) 7.9.4 Using Universal Coordinated Time (UTC) If your system is located in the GMT time zone or Antarctica, or if you do not want to make seasonal adjustments to the TDF, you may want to use UTC as your system's local time. You can also configure all network systems with UTC if you consider local time irrelevant for your applications. If you select UTC as the local time and later enter the NCL command show dtss current time, the local time displayed has a TDF of 0 (zero). To use UTC as your system's local time, select option 2: * Enter an option number [1] : 2 The subsequent actions are identical to those shown following the selection of a time zone in the previous section. This completes changes to the DECdts configuration using option 2. The net$configure procedure returns to the main options menu. 7.9.5 Defining Your Own Time Zone Rule The net$configure procedure no longer allows you to create a customized time zone rule. To create a customized time zone rule, refer to the additional documentation resources referenced in Section 7.9.2. In particular, the Compaq C Run-Time Library Utilities Reference Manual discusses using the Zone Information Compiler (ZIC) to create new binary time zone files. Once you have created a new file and moved it to the appropriate place in the time zones directory, you can select the time zone in the same manner you would select any other time zone. If you select option 3, the procedure displays a short description of the process used to create a custom time zone rule. 7.10 Configuring the Event Dispatcher To configure the Event Dispatcher, select option 6 from the main options menu: * Which configuration option to perform? [0] : 6 Modifying a Current Configuration 7-47 Modifying a Current Configuration 7.10 Configuring the Event Dispatcher The procedure asks if you want to replace the existing event dispatcher NCL startup script: %NETCONFIGURE-I-EVDFND, Event dispatcher NCL script already exists * Replace Event Dispatcher NCL script file? [NO] : If you want to create a new Event Dispatcher NCL startup script file, answer YES. If you want to keep the previously generated Event Dispatcher NCL startup script file, answer NO. BASIC If you answered YES, the BASIC option informs you that the procedure automatically creates the default Event Dispatcher configuration for you: %NET$CONFIGURE-I-EVDDEFAULT, providing default Event Dispatcher configuration ADVANCED If you answered YES, the ADVANCED option uses the same prompts used during the initial configuration. See Section 6.9 for the prompts used in this section and for information about how to respond to the prompts. BASIC and ADVANCED Once you have completed the Event Dispatcher dialog, the procedure displays a summary of the configuration and asks if you want to configure the new NCL startup scripts. Proceed to Section 7.17 for more information. 7.11 Configuring the Application Database When you configure the application database, you can either delete an existing application (including any of the default applications installed during the initial configuration), or you can include a new application. To configure the application database, select option 7 from the main options menu: * Which configuration option to perform? [1] : 7 The procedure begins by asking if you want to add or delete an application: * Do you want to ADD or DELETE an Application? [ADD] : 7-48 Modifying a Current Configuration Modifying a Current Configuration 7.11 Configuring the Application Database Answer ADD to create a new application entity on the local node, allocate resources for it, and open the service interface. Answer DELETE to delete an existing entity and reclaim associated resources. Next, the procedure asks for the applications's name: * What is the name of the Application? : NOTES If you are deleting an application, proceed to Section 7.11.1. If you are adding an application, proceed to Section 7.11.2. Once you have completed the applications dialog, the procedure asks if you want to configure the new NCL startup scripts. Proceed to Section 7.18 for more information. ________________________ Note ________________________ Each invocation of option 7 adds or deletes one application. If you wish to add or delete multiple applications, invoke option 7 again. ______________________________________________________ 7.11.1 Deleting an Application If you are deleting an application, the procedure displays the following prompt: * Are you sure you want to DELETE this application? [NO]: Answer YES if you want to delete the application. Answer NO if you want to keep the application. If you answer NO, the procedure informs you it has canceled the delete operation: %NET$CONFIGURE-I-DELETECAN, delete operation canceled 7.11.2 Adding an Application If you are adding an application, the configuration procedure asks a series of questions to define the application: 1. To add an application, the procedure must create one or more addresses (also known as end-user specifications) for the application. Incoming connections provide the application's address in the destination name field of the connection request. Table 7-2 lists the supported Modifying a Current Configuration 7-49 Modifying a Current Configuration 7.11 Configuring the Application Database types of end-user specifications (referred to in the dialog as destination types). Table_7-2_Application_End-User_Specification_Types_________ Type________Description____________________________________ NAME The local name of the application (for example, NOTES). The name must be 1 to 16 characters in length. NUMBER The unique number assigned to the application. Application numbers must be in the range of 1 to 255. Well-known applications such as MAIL and FAL have application numbers that are recognized throughout the network. See Table 7-3 for application number preassigned or reserved by HP. User-defined images can have unique object numbers; numbers between 128 and 255 are reserved for this purpose. In Phase IV terms, the application number was known as the application's object number. FULLNAME The DECdns full name assigned to the application (for example, IAF:.SALES.BOSTON.APP3). The full name must be 1 to 512 characters in length and in the format ____________NamespaceNickname:[.DirectoryPath].NodeObject._ Table 7-3 lists the application numbers used or reserved by HP. Table_7-3_Application_Numbers______________________________ Number____Mnemonic_Description_____________________________ 0 Task User program 1-16 Reserved for HP use 17 FAL File access listener for remote file and record access (continued on next page) 7-50 Modifying a Current Configuration Modifying a Current Configuration 7.11 Configuring the Application Database Table_7-3_(Cont.)_Application_Numbers______________________ Number____Mnemonic_Description_____________________________ 18 HLD Host loader for RSX-11S downline task loading requests 19 CML CMIP Management Listener object 20 RSTS/E media transfer program (NETCPY) 21-22 Reserved for HP use 23 REMACP Network terminal handler (host side) 24 Network terminal handler (terminal side) 25 MIRROR Loopback mirror 26 EVL Event receiver 27 MAIL OpenVMS Mail utility 28 Reserved for HP use 29 PHONE OpenVMS Phone utility and RSX-11M/M-PLUS Phone utility 30 Reserved for HP use 31 X.25 Server 32-35 Reserved for HP use 36 X.25 Client 37-41 Reserved for HP use 42 CTERM Network terminal handler 43 Reserved for HP use 44 DNSCLERK Used by DNS Server to receive connects from DNS clerks 45 DNSCLERK Used by DNS Server to receive connects from DNS servers 46-62 Reserved for HP use 63 DTR DECnet Test Receiver object 64-85 Reserved for HP use 86 Used by DNS$ADVER for remote-to-local cache transfers 87-127 Reserved for HP use (continued on next page) Modifying a Current Configuration 7-51 Modifying a Current Configuration 7.11 Configuring the Application Database Table_7-3_(Cont.)_Application_Numbers______________________ Number____Mnemonic_Description_____________________________ 128-255____________Reserved_for_customer_use_______________ The procedure begins by asking you for the application's destination type: * What is the destination type for 'notes'? [NAME] : Select NAME, NUMBER, FULLNAME, or UIC. The NOTES application is a well-known application with an HP- reserved application number. Therefore, enter NUMBER. Next, based on the value you entered for the destination type, the procedure asks you for the required value for that destination type: * What is the destination destination-type for 'notes'? : Enter the appropriate value based on the destination type you entered. You have the option of specifying multiple addresses for an application. The procedure asks if you want to assign another address to this application: * Do you want to specify another application address? [NO]: If the application has more than one application address, enter YES and the previous prompts are repeated. 2. The client name specifies the name of the local entity that you want activated upon receipt of the connect request containing a destination name matching one of the destination values you specified in Step 1. * What is the name of the Client for 'notes'? : 3. The image name specifies the file name of the program you want invoked upon receipt of a Connect Request containing a destination name matching one of the destination values you specified in Step 1. * What is the Image name for 'notes'? :sys$system:notes$server.exe Specify the full file name of the application's image. 7-52 Modifying a Current Configuration Modifying a Current Configuration 7.11 Configuring the Application Database 4. The answer to the following question specifies whether or not the application should respond to incoming connect requests directed to the alias node address. FALSE indicates that the application should not accept incoming connect requests that have been directed to the alias node address. TRUE indicates that the application should accept such requests. * Incoming Alias for 'notes' enabled? [TRUE] : Specify TRUE or FALSE. 5. The answer to the following question specifies whether or not incoming proxy requests for the application are honored. FALSE indicates that incoming proxy requests for the application are ignored. TRUE indicates that incoming proxy requests are allowed. This value overrides the global Session Control value. * Incoming Proxy for 'notes' enabled? [TRUE] : Specify TRUE or FALSE. 6. The answer to the following question specifies whether or not the application should use the alias node address in its outgoing connect requests. FALSE indicates that the application should not use the alias node address in its outgoing connect requests. TRUE indicates that the application should use the alias node address. * Outgoing Alias for 'notes' enabled? [TRUE] : Specify TRUE or FALSE. 7. The answer to the following question specifies whether or not the application should use a proxy by default if the application does indicate whether to use a proxy. FALSE indicates that, by default, this application does not use an outgoing proxy. TRUE indicates that, by default, this application uses an outgoing proxy. * Outgoing Proxy for 'notes' enabled? [TRUE] : Specify TRUE or FALSE. 8. The answer to the following question specifies whether or not the remote node name is passed to the application in synonym form. If a synonym is not available, the full name is always used. FALSE indicates that the Modifying a Current Configuration 7-53 Modifying a Current Configuration 7.11 Configuring the Application Database full name is passed to the application. TRUE indicates that the node synonym, if available, is passed to the application. * Require node synonym for 'notes' enabled? [TRUE] : Specify TRUE or FALSE. 9. The OSI TSEL is used for applications that do not use the DNA Session Control protocol. The TSEL is roughly equivalent to a DNA Session Control address. The TSEL must be a hexadecimal number of 2 to 64 digits and must contain an even number of digits. * What is the Incoming OSI TSEL for 'notes'? : ________________________ Note ________________________ This function is currently not implemented. Press Return to continue to the next prompt. ______________________________________________________ 10. You have the option of creating an OpenVMS account under which the application should run. To create the account, begin by entering the user name that you want to use when creating the account. If you do not want to create an account for the application, you can either enter NONE and press Return, or press the space bar and press Return. * What is the User Name for 'notes'? [NOTES$SERVER] : If you decide to create an account for the application (by providing an account name in the previous question), you must provide a UIC for the account and assign any rights identifiers associated with the account. Answer the following two questions to enter the UIC and any rights identifiers for the application: * What UIC should 'notes' use? [[200,200]] : [376,377] * Rights identifiers for 'NOTES$SERVER'? :net$examine, net$declareobject,net$decnetaccess If there are two or more rights identifiers, separate them with commas. 7-54 Modifying a Current Configuration Modifying a Current Configuration 7.11 Configuring the Application Database If you have entered account information in the previous three questions, the procedure then creates the account for the application and displays the following message: %NET$CONFIGURE-I-MAKEACCOUNT, this procedure creates user account NOTES$SERVER 7.12 Configuring the MOP Client Database To configure the MOP client database, select option 8 from the main options menu: * Which configuration option to perform? [1] : 8 The procedure begins by asking if you want to add or delete a MOP client: * Do you want to ADD or DELETE a MOP Client? [ADD] : Answer ADD to create a new MOP client entity on the local node, allocate resources for it, and open the service interface. Answer DELETE to delete an existing entity and reclaim associated resources. Next, the procedure asks for the MOP client's name: * Name of the MOP Client? : SUPERX Specify the simple name of the client (for example, SUPERX). If you are deleting a MOP client, proceed to Section 7.12.1. If you are adding a MOP client, proceed to Section 7.12.2. Once you have completed the MOP client dialog, the procedure asks if you want to configure the new NCL startup scripts. Proceed to Section 7.18 for more information. ________________________ Note ________________________ Each invocation of option 8 adds or deletes one MOP client. If you wish to add or delete multiple MOP clients, invoke option 8 again. ______________________________________________________ Modifying a Current Configuration 7-55 Modifying a Current Configuration 7.12 Configuring the MOP Client Database 7.12.1 Deleting a MOP Client If you want to delete a MOP client, the procedure displays the following prompt: * Are you sure you want to DELETE this client? : Answer YES if you want to delete the MOP client. Answer NO if you want to keep the MOP client. If you answer NO, the procedure informs you it has canceled the delete operation: %NET$CONFIGURE-I-DELETECAN, delete operation canceled 7.12.2 Adding a MOP Client If you are adding a MOP client, the configuration procedure asks a series of questions to define the MOP client: 1. The procedure begins by asking you for the MOP circuit to be used for all operations involving the client: * Circuit for 'superx'? : Specify a MOP circuit name. 2. For LAN circuits, you must also specify a set of LAN addresses for this client: * Physical addresses for 'superx'? : Specify a set of LAN addresses separated by commas. 3. The next three questions describe the files that are loaded onto the MOP client system during a downline load operation. The primary loader is assumed to be the resident code on the system that activates the client's network interface and prepares the system for downline loaded software. Depending on the system, you may need to specify a secondary loader and a tertiary loader that are loaded before the system image. All file specifications are complete file specifications for files on the local node. * Secondary Loader for 'superx'? : * Tertiary Loader for 'superx'? : * System Image for 'superx'? : Specify the files you want loaded when the client requests the various images. If necessary, you can specify multiple files for each question. 7-56 Modifying a Current Configuration Modifying a Current Configuration 7.12 Configuring the MOP Client Database 4. In addition to the system image file and its associated secondary and tertiary loaders, MOP has the capability to respond to downline load requests for special system images used for diagnostics and system management. System management images can take the form of system- specific management files or CMIP script files containing network management commands in CMIP form. All file specifications are complete file specifications for files on the local node. * Diagnostic Image for 'superx'? : * Management Image for 'superx'? : * Script File for 'superx'? : Specify the files you want loaded when the client requests diagnostic and management images. If necessary, you can specify multiple files for each question. 5. The next two questions control upline dump actions involving the client system. You can specify the file on the local system used to contain the upline dump and the memory address in the client system at which to begin the dump operation. * Dump File for 'superx'? : * Dump Address for 'superx'? [0] : Specify the dump file and the starting address. 6. You can specify a verification string you want sent in a boot message to the specified client: * Verification for 'superx'? [%X0000000000000000] : 7. The next four questions define Phase IV information that is passed to the client in a downline load operation. Some client software needs this information. You can specify the Phase IV client address and name and the Phase IV host address and name. The client information defines the client's own Phase IV identity; the host information identifies the client's load host Phase IV identity. * Phase IV Client Address (aa.nnn) for 'superx'? : * Phase IV Client Name for 'superx'? [] : * Phase IV Host Address for 'superx'? : * Phase IV Host Name for 'superx'? [] : Modifying a Current Configuration 7-57 Modifying a Current Configuration 7.12 Configuring the MOP Client Database Specify the Phase IV information appropriate for the software being loaded on the client system. 7.13 Configuring a Cluster Alias To configure a cluster alias, select option 9 from the main options menu: * Which configuration option to perform? [1] : 9 The procedure begins by asking if you want to add or delete an alias: * Do you want to ADD or DELETE an alias? [ADD] : Answer ADD to create an alias on the local node; answer DELETE to delete an existing alias. Next, the procedure asks for the full name of the alias: * Full name of Cluster Alias : Specify the full name of the alias (for example, IAF:.sales.boston). If you are deleting an alias, proceed to Section 7.13.1. If you are adding an alias, proceed to Section 7.13.2. Once you have completed the alias dialog, the procedure displays a summary of the configuration and asks if you want to configure the new NCL startup scripts. Proceed to Section 7.17 for more information. 7.13.1 Deleting an Alias If you are removing a node from the specified alias, the procedure displays the following prompt: * Are you sure you want to DELETE this alias? [NO]: Answer YES if you want to remove the system from this alias. Answer NO if you want the system to remain a member of this alias. If you answer NO, the procedure informs you it has canceled the delete operation: %NET$CONFIGURE-I-DELETECAN, delete operation canceled 7-58 Modifying a Current Configuration Modifying a Current Configuration 7.13 Configuring a Cluster Alias 7.13.2 Adding an Alias If you are adding a node to a cluster alias, the dialog for a configuration modification is identical to the initial dialog. See Section 6.12 for the entire alias dialog. 7.14 Replacing a MOP Client Configuration To replace a MOP Client Configuration, select option 10 from the main options menu: * Which configuration option to perform? [1] : 10 _______________________ Warning _______________________ Using this option deletes the existing MOP client NCL startup script file. In the initial configuration, this file contains two NCL commands: one to create MOP and one to enable MOP. If you have modified the initial configuration by using option 8 to add MOP client definitions, these definitions exist in the MOP Client NCL startup script file. Therefore, choosing to replace the existing MOP client file deletes all the MOP client information you added by using option 8. For information about how you can create a MOP client database not subject to this deletion, see Section 7.20.1. ______________________________________________________ By default, MOP is not started by net$startup. To make this system service MOP requests, the NET$STARTUP_MOP logical name must be defined to signal net$startup to load the MOP software. This symbol is normally defined in sys$startup:net$logicals.com. Based on your input, the procedure modifies net$logicals.com by adding or removing the definition of the NET$STARTUP_MOP logical name. This section of the procedure also generates a short NCL startup script file containing the NCL commands to create and enable the MOP entity. The procedure asks if you want MOP loaded: * Load MOP on this system? [YES] : Modifying a Current Configuration 7-59 Modifying a Current Configuration 7.14 Replacing a MOP Client Configuration Answer YES to enable MOP service on this system. Answer NO to disable MOP service on this system. Note that your answer will have no effect if the NET$STARTUP_MOP logical name is defined elsewhere. Regardless of your answer, the procedure displays the following message and asks it you want to replace the MOP client NCL startup script file: %NET$CONFIGURE-I-MOPCLIENTFND, MOP client NCL script already exists * Replace MOP Client script file? [NO] : yes Answer YES to create a new MOP Client NCL startup script file, otherwise press Return. Once you have completed the MOP dialog, the procedure displays a summary of the configuration and asks if you want to configure the new NCL startup scripts. Proceed to Section 7.17 for more information. 7-60 Modifying a Current Configuration Modifying a Current Configuration 7.15 Configuring Satellite Nodes 7.15 Configuring Satellite Nodes This section of the dialog allows you to configure satellite nodes that are members of your system's OpenVMS Cluster. Before using this feature, you must first fully configure the system on which you are now running the net$configure procedure. _______________________ Caution _______________________ If your cluster is running mixed versions of DECnet- Plus, you cannot use this feature. Instead, you must configure the nodes independently by running net$configure on each system. ______________________________________________________ BASIC This option is not available when using the BASIC option. ADVANCED To configure satellite nodes, select option 11 from the main options menu: * Which configuration option to perform? [1] : 11 The procedure displays a submenu: Configuration Options: [0] Return to main menu [1] Autoconfigure Phase IV cluster nodes [2] Configure cluster node scripts [3] Configure local node * Which configuration option to perform? [1] : Table 7-4 gives a brief description of the satellite configuration options. Modifying a Current Configuration 7-61 Modifying a Current Configuration 7.15 Configuring Satellite Nodes Table_7-4_Satellite_Configuration_Options__________________ Option___Description_______________________________________ 1 Autoconfigure Phase IV cluster nodes - Use this option to perform the initial configuration of a Phase IV cluster member. This option can be used only for cluster members that have not yet been configured (either by using this option or by running net$configure directly on the cluster member). 2 Configure cluster node scripts - Use this option to set up the configuration utility to reference a satellite node in all future configuration tasks. You can use this option to further refine the configuration automatically created by option 1. 3 Configure local node - Use this option to delete the satellite selection made in option 2 and return to configuring the local node in all future _________configuration_tasks.______________________________ 7-62 Modifying a Current Configuration Modifying a Current Configuration 7.15 Configuring Satellite Nodes 7.15.1 Autoconfiguring Phase IV Cluster Nodes To autoconfigure a Phase IV cluster member, select option 1 from the satellite options menu: * Which configuration option to perform? [1] : 1 If you select this option, the procedure creates a short command file that invokes net$configure with the parameters necessary to complete the initial configuration. This command file is invoked the next time that the satellite system is rebooted. Most of the parameters are derived from the defaults within the net$configure procedure. However, you must supply a small number of parameters directly. 1. The procedure begins by asking you to enter the full name of a cluster alias in which you want the cluster member to participate: * Fullname of cluster alias: : Supply the full node name of the cluster alias. If none is supplied, no cluster alias is configured for the systems being upgraded. 2. If you entered a cluster alias name in the previous question, the next two prompts ask for the address and selection weight for the alias: * Cluster Alias Phase IV Address (aa.nnnn OR AA-00-04-00-xx-xx) : * Selection weight for this cluster node [0 for satellites] : Enter a Phase IV address or a MAC address. For more information about these two questions, see the alias dialog in Section 6.12. 3. To configure the cluster satellite systems, the configuration procedure needs to know the system root directories from which the satellites boot. Normally, the system root directories are on sys$sysdevice. The device given in response to this question is searched for all system roots. Those found that do not contain a Phase V checksum database are assumed to be Phase IV nodes and are candidates for autoconfiguration. Enter the device containing the system roots for cluster members: * Device containing system roots [SYS$SYSDEVICE:] : Modifying a Current Configuration 7-63 Modifying a Current Configuration 7.15 Configuring Satellite Nodes The procedure displays the following message as it scans the indicated system root device for system root directories: Scanning SYS$SYSDEVICE: for Phase IV system root directories... If it finds a directory it does some additional checking to verify that it has found a valid system root directory. If the directory is valid, it uses the member's modparams.dat file to obtain the default values for some of the following questions. If no roots are found on the device supplied (or if all the roots found have already been autoconfigured), the procedure asks if it should scan any additional devices for system roots: * Are there any more disk devices containing system roots? [NO] : Answer YES if any additional devices contain system root directories. Answer NO to return to the satellite configuration menu. a. If a system root is found and the system has not been autoconfigured (that is, does not contain a DECnet- Plus checksum database), the procedure asks if you want to upgrade the cluster member: * Upgrade Phase IV cluster member FASTER? [Yes] : If you answer YES, net$configure creates the file sys$specific:[sys$startup]net$autoconfigure.com. If this file is present when the cluster member reboots, it causes the cluster member to automatically run net$configure using the information you supply in this section. Answer NO if you do not want the system autoconfigured. If the procedure finds a root that contains a net$autoconfigure.com file but has not yet been configured, it precedes the upgrade question with a message indicating that you have already created the autoconfiguration file: %NET$CONFIGURE-I-ALREADYMARKED, FASTER is already marked for upgrade 7-64 Modifying a Current Configuration Modifying a Current Configuration 7.15 Configuring Satellite Nodes b. In you answered YES to the upgrade question, the procedure needs to complete the information required for the net$autoconfigure.com file. The procedure asks you for the node's full name. The full name can be a name in the Local, DECdns, or Domain name service. See Section 6.4.1 and Section 6.4.2 for more information about name services and full names. Enter the full name of the satellite node: * Enter the full name [HP:.FASTER] : Enter the node's full name. The nickname you use determines the name service. If you fail to provide the nickname (or namespace name if specifying a Local or Domain full name), the procedure informs you that you must enter the nickname: NET$CONFIGURE-E-NONAMESPACENAME, namespace nickname required c. Next, enter the node synonym to use for the satellite: * What is the synonym name for this system? [FASTER] : Enter the node's synonym. See Section 6.4.3 for more information about node synonyms. The procedure resumes the scan of the system root device. If any more system roots are found, the procedure repeats the previous three questions for each satellite system root found. Once the procedure completes the scan of system roots on the device you indicated, it asks you if there are any other devices containing system roots: * Are there any more disk devices containing system roots? [No] : Answer YES if you wish to specify another device containing system roots. Answer NO if there are no more devices containing system roots. ________________________ Note ________________________ This dialog forces all satellites to join a common alias. If the cluster supports more than one alias you can select this option again and supply a different cluster alias. In this manner, you can configure Modifying a Current Configuration 7-65 Modifying a Current Configuration 7.15 Configuring Satellite Nodes some of the satellite nodes in one alias and other satellite nodes in a second alias. ______________________________________________________ After completing all requested autoconfigurations, the procedure returns to the satellite options menu. 7.15.2 Electing To Configure Cluster Node Scripts Normally, the configuration procedure is used to configure the local node. You can use the procedure to modify satellite nodes that have already been configured (either by using option 1 and rebooting the satellite or by running net$configure directly on the node). This option allows you to direct the configuration procedure to perform all future operations on a satellite node instead of the local node. Note that not all configuration options are available when configuring a satellite node. To direct the configuration procedure to perform all future operations on a satellite node, select option 2 from the satellite options menu: * Which configuration option to perform? [1] : 2 The procedure asks you for the name of the cluster member that you want to configure: * Cluster node name to be configured: : FASTER Enter the simple name of the cluster member you want to configure. ________________________ Note ________________________ The net$configure procedure attempts to find the system root for that cluster member (by scanning the net$mop_client_startup.ncl startup script file on the local system) to supply defaults for the two questions that follow. ______________________________________________________ The next two questions determine the location of the satellite's system root. The first question asks for the disk device on which the cluster member's system root resides. The default is either sys$sysdevice or the root 7-66 Modifying a Current Configuration Modifying a Current Configuration 7.15 Configuring Satellite Nodes device found for that system in the local system's net$mop_ client_startup.ncl script file. * Device for FASTER root: [SYS$SYSDEVICE] : Enter the device containing the system's root. Next, the procedure asks you for the system root directory from which the member loads: * Directory for FASTER root: : SYS2 Enter the system root directory in the form SYSxxxx, where xxxx is a hexadecimal number. The procedure verifies that the cluster member has been configured (either through the autoconfigure option discussed in suboption 1 or by running net$configure directly on the satellite). If the autoconfigure file created by suboption 1 is found but no other configuration files are found, the procedure displays the following message: ******************************************************************** This cluster member has been flagged for autoconfiguration of OSI/DECnet Phase V, but has not yet executed the autoconfiguration procedure. In order to do this, the system must be rebooted, or SYS$STARTUP:NET$STARTUP.COM must be executed. ******************************************************************** If the procedure finds no configuration files and no autoconfigure file, it displays the following message: ******************************************************************** This cluster member has not yet been configured for OSI/DECnet Phase V. You may either select option [1] to autoconfigure this system, or run NET$CONFIGURE on this system. ******************************************************************** If the proper configuration information is found, the procedure returns to the main options menu to allow you to modify the cluster member's configuration. Before net$configure returns to the main options menu, it warns you that all subsequent options will be applied to the cluster member you specified: %NET$CONFIGURE-I-VERCHECKSUM, verifying checksums All configuration options will be applied to cluster node FASTER Modifying a Current Configuration 7-67 Modifying a Current Configuration 7.15 Configuring Satellite Nodes Note that the following main menu options are not available when configuring satellite nodes: option 1 (Perform an entire configuration), option 3 (Configure Devices on this machine), and option 5 (Configure Timezone Differential Factor). 7.15.3 Electing to Configure the Local Node If you select option 3, it clears the action of option 2; that is, all subsequent net$configure modifications are made to the local system (as when net$configure was started). To direct the configuration procedure to perform all future operations on the local node, select option 3 from the satellite options menu: * Which configuration option to perform? [1] : 3 All subsequent configuration tasks now affect the local node. All options in the main options menu are again available. 7.15.4 Exiting the Satellite Options Menu To exit the satellite options menu, enter 0 and press Return. The procedure returns you to the main options menu. 7.16 Configuring Cluster-Common Script Locations If you did not already elect to do so, this option allows you to make the event, application, and MOP client NCL startup scripts (net$event_startup, net$application_ startup, and net$mop_client_startup) common for all cluster nodes. That is, a single copy of each script is shared by all systems in the cluster. This ensures that all systems have the same event logging, application, and MOP client configuration. The configuration procedure does this by moving the NCL startup scripts from the node's sys$specific directory to it's sys$common directory. ________________________ Note ________________________ The configuration procedure deletes the existing system-specific NCL startup scripts in sys$specific only on the node where net$configure is currently 7-68 Modifying a Current Configuration Modifying a Current Configuration 7.16 Configuring Cluster-Common Script Locations running. It does not delete the system-specific script files from the sys$specific directories of the other cluster members. You must do this explicitly by selecting this option (either after using suboption 2 of option 11 to select the cluster member or by running net$configure directly on the cluster member) on all cluster members where you want to delete the sys$specific scripts. ______________________________________________________ BASIC This option is not available when using the BASIC option. ADVANCED To select this option, you must have already configured the system using the ADVANCED configuration option, and net$configure must be executing on a cluster system. To manage the location of the cluster-common NCL startup script files, select option 12 from the main options menu: * Which configuration option to perform? [1] : 12 The remainder of this section contains an example of how this option can be used to manage the location of the scripts files for EVENT, APPLICATION, and MOP_CLIENT. This example assumes that you elect to create cluster-common script files for all three scripts. It is assumed that you previous elected to create system-specific scripts. These cluster-common scripts are created from the system- specific scripts on the currently selected system. (To make the dialogs in this section more clear, some additional formatting has been added to the example output.) 1. Begin by selecting option 12. * Which configuration option to perform? [1] : 12 2. For each script, the procedure asks if you want to move the script and then displays a message indicating that the script has been moved if you answer YES: Modifying a Current Configuration 7-69 Modifying a Current Configuration 7.16 Configuring Cluster-Common Script Locations * Move the APPLICATION startup script to the cluster common area? [YES] : %NET$CONFIGURE-I-MOVESCRIPT, created cluster common APPLICATION startup script from SYS$SPECIFIC:[SYSMGR]NET$APPLICATION_STARTUP.NCL; * Move the EVENT startup script to the cluster common area? [YES] : %NET$CONFIGURE-I-MOVESCRIPT, created cluster common EVENT startup script from SYS$SPECIFIC:[SYSMGR]NET$EVENT_STARTUP.NCL; * Move the MOP_CLIENT startup script to the cluster common area? [YES] : %NET$CONFIGURE-I-MOVESCRIPT, created cluster common MOP_CLIENT startup script from SYS$SPECIFIC:[SYSMGR]NET$MOP_CLIENT_STARTUP.NCL; ________________________ Note ________________________ Although the example shows all three scripts being moved, you do not have to treat all scripts in the same manner. ______________________________________________________ After moving the scripts, new checksums are created and the procedure returns to the main options menu (after informing you that it is using the cluster-common scripts): %NET$CONFIGURE-I-MODCHECKSUM, checksumming NCL management scripts modified by NET$CONFIGURE %NET$CONFIGURE-I-CONFIGCOMPLETED, DECnet-Plus for OpenVMS configuration completed %NET$CONFIGURE-I-USECOMMON, using cluster common APPLICATION script %NET$CONFIGURE-I-USECOMMON, using cluster common EVENT script %NET$CONFIGURE-I-USECOMMON, using cluster common MOP_CLIENT script 3. However, these cluster-common scripts will not be used by the satellite system FASTER because it still has system-specific copies. To change this, select option 11 to manage cluster nodes and then suboption 2 to manage the configuration for node FASTER: Configuration Options: [0] Exit this procedure 7-70 Modifying a Current Configuration Modifying a Current Configuration 7.16 Configuring Cluster-Common Script Locations [1] Perform an entire configuration . . . [11] Configure satellite nodes [12] Configure cluster script locations * Which configuration option to perform? [0] : 11 Configuration Options: [0] Return to main menu [1] Autoconfigure Phase IV cluster nodes [2] Full configuration of cluster node [3] Configure local node * Which configuration option to perform? [0] : 2 * Cluster node name to be configured: : FASTER * Device for FASTER root: [SYS$SYSDEVICE] : * Directory for FASTER root: : SYS10 The configuration procedure informs you that FASTER has system-specific versions of these scripts that override the cluster-common scripts: %NET$CONFIGURE-I-OVERRIDECOMMON, node specific APPLICATION script overrides the cluster common settings %NET$CONFIGURE-I-OVERRIDECOMMON, node specific EVENT script overrides the cluster common settings %NET$CONFIGURE-I-OVERRIDECOMMON, node specific MOP_CLIENT script overrides the cluster common settings All configuration options will be applied to cluster node FASTER 4. Select option 12 to delete the system-specific scripts so that FASTER will use the cluster-common versions: Configuration Options: [0] Exit this procedure [1] Perform an entire configuration . . . [11] Configure satellite nodes [12] Configure cluster script locations Modifying a Current Configuration 7-71 Modifying a Current Configuration 7.16 Configuring Cluster-Common Script Locations * Which configuration option to perform? [0] : 12 5. The procedure asks you if each system-specific script should be deleted and displays a message indicated that it is deleting the system-specific version when you answer YES: * Delete the local APPLICATION startup script? [NO] : yes %NET$CONFIGURE-I-DELETEDOVERRIDE, deleted system specific copy of the APPLICATION startup script * Delete the local EVENT startup script? [NO] : yes %NET$CONFIGURE-I-DELETEDOVERRIDE, deleted system specific copy of the EVENT startup script * Delete the local MOP_CLIENT startup script? [NO] : yes %NET$CONFIGURE-I-DELETEDOVERRIDE, deleted system specific copy of the MOP_CLIENT startup script After deleting the system-specific scripts, new checksums are created and the procedure returns to the main menu (after informing you that it is using the cluster-common scripts): %NET$CONFIGURE-I-MODCHECKSUM, checksumming NCL management scripts modified by NET$CONFIGURE %NET$CONFIGURE-I-CONFIGCOMPLETED, DECnet-Plus for OpenVMS configuration completed %NET$CONFIGURE-I-USECOMMON, using cluster common APPLICATION script %NET$CONFIGURE-I-USECOMMON, using cluster common EVENT script %NET$CONFIGURE-I-USECOMMON, using cluster common MOP_CLIENT script All configuration options will be applied to cluster node FASTER After the initial creation of cluster-common scripts, option 12 always allows you to alternate the status of the system-specific scripts. That is, if the system currently has system-specific scripts, you are given the opportunity to delete them. If the system does not currently have system-specific scripts, you are given the opportunity to create them. For example, if you now wanted to restore system-specific scripts to node FASTER, again select option 12 (this time to restore the system-specific scripts so that FASTER will use these scripts instead of the cluster-common versions): 7-72 Modifying a Current Configuration Modifying a Current Configuration 7.16 Configuring Cluster-Common Script Locations Configuration Options: [0] Exit this procedure [1] Perform an entire configuration . . . [11] Configure satellite nodes [12] Configure cluster script locations * Which configuration option to perform? [0] : 12 * Override the cluster common default APPLICATION startup script? [NO] : y %NET$CONFIGURE-I-CREATEDOVERRIDE, created system specific copy of the APPLICATION startup script * Override the cluster common default EVENT startup script? [NO] : y %NET$CONFIGURE-I-CREATEDOVERRIDE, created system specific copy of the EVENT startup script * Override the cluster common default MOP_CLIENT startup script? [NO] : y %NET$CONFIGURE-I-CREATEDOVERRIDE, created system specific copy of the MOP_CLIENT startup script After creating the system-specific scripts, new checksums are created and the procedure returns to the main menu (after informing you that it is using the system-specific scripts): %NET$CONFIGURE-I-MODCHECKSUM, checksumming NCL management scripts modified by NET$CONFIGURE %NET$CONFIGURE-I-CONFIGCOMPLETED, DECnet-Plus for OpenVMS configuration completed %NET$CONFIGURE-I-OVERRIDECOMMON, node specific APPLICATION script overrides the cluster common settings %NET$CONFIGURE-I-OVERRIDECOMMON, node specific EVENT script overrides the cluster common settings %NET$CONFIGURE-I-OVERRIDECOMMON, node specific MOP_CLIENT script overrides the cluster common settings If you choose not to delete the system-specific files, the procedure gives you the option to delete the cluster-common files instead: Modifying a Current Configuration 7-73 Modifying a Current Configuration 7.16 Configuring Cluster-Common Script Locations * Delete the local APPLICATION startup script? [NO] : * Delete the cluster common APPLICATION script? [NO] : yes %NET$CONFIGURE-I-DELETECOMMON, deleted the cluster common APPLICATION startup script * Delete the local EVENT startup script? [NO] : * Delete the cluster common EVENT script? [NO] : yes %NET$CONFIGURE-I-DELETECOMMON, deleted the cluster common EVENT startup script * Delete the local MOP_CLIENT startup script? [NO] : * Delete the cluster common MOP_CLIENT script? [NO] : yes %NET$CONFIGURE-I-DELETECOMMON, deleted the cluster common MOP_CLIENT startup script After deleting the cluster-common scripts, new checksums are created and the procedure returns to the main menu: %NET$CONFIGURE-I-MODCHECKSUM, checksumming NCL management scripts modified by NET$CONFIGURE %NET$CONFIGURE-I-CONFIGCOMPLETED, DECnet-Plus for OpenVMS configuration completed All configuration options will be applied to cluster node FASTER 7.17 Summary Display With the exceptions of options 5, 7, 8, 11, and 12, the configuration procedure displays an updated summary of the node's configuration. In the case of option 1 (Perform an entire configuration) or option 2 (Change naming information), the display includes an additional field entitled "DECdns Node Type" in the Node Information section. This field shows you whether the node has been configured as a DECdns server or clerk. A portion of the display is shown below (for the complete display, see Section 6.13): Summary of Configuration 7-74 Modifying a Current Configuration Modifying a Current Configuration 7.17 Summary Display 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:: DECdns Node Type: Server Session Control Address Update Interval: 10 Routing Node Type: ENDNODE Autoconfiguration of Network Addresses: Enabled Routing ESHello Timer: 600 Routing ES Cache Size: 512 Alias Name: ACME:.WABBIT.HELP . . . 7.18 Generating New NCL Startup Scripts With the exception of options 2 and 12, the procedure asks if you want generate new NCL startup scripts based on the new configuration information: * Do you want to generate NCL configuration scripts? [YES] : Answer YES to accept the new configuration you just specified. The procedure automatically generates any required NCL scripts in the sys$manager directory. ________________________ Note ________________________ Option 2 (Change naming information) does not ask if you want to generate new NCL scripts. It always generates new scripts. The naming operations are complex and are performed throughout the dialog. Therefore, if you need to retract a change, you must run the configuration dialog again with the old information. ______________________________________________________ Modifying a Current Configuration 7-75 Modifying a Current Configuration 7.18 Generating New NCL Startup Scripts The procedure performs a checksum process on the modified scripts to check if any of the scripts have changed when you run net$configure again. It displays a message indicating that the checksum process is in progress: %NET$CONFIGURE-I-MODCHECKSUM, checksumming NCL management scripts modified by NET$CONFIGURE If the procedure is unable to access the existing checksum file, it displays the following error messages: %NET$CONFIGURE-E-WRITECKERR, error writing checksum file . . . %NET$CONFIGURE-I-LASTTRANSABORT, last transaction aborted Exit the procedure (select option 0), determine why the configuration procedure was not able to write a new checksum file, and retry the operation. The LASTTRANSABORT message is also displayed whenever you cancel an option. The configuration procedure returns to the main menu. Under these circumstances, you can continue with other configuration options. 7.19 Starting the Network When modifying a configuration, the configuration procedure does not restart a running network. If you selected option 1 (Perform an entire configuration) and the network is not started, the procedure starts the network as discussed in Section 6.15. If you selected option 2 (Change naming information), the procedure also starts the network to enable it to make namespace modifications. See Section 7.6 for more information about processing that occurs during option 2 modifications. In the case of all other options that affect the local node, if the network is running when you modify the node's configuration, you can execute the modified NCL startup scripts in two ways: o Reboot the system. 7-76 Modifying a Current Configuration Modifying a Current Configuration 7.19 Starting the Network o Disable the entity to which the script applies and execute the modified script. To execute the NCL script, use the format ncl> do script-file. For example: ncl> do sys$manager:net$nsp_transport_startup.ncl ________________________ Note ________________________ Although, the net$configure procedure does not automatically execute the modified NCL scripts for you, it does execute the search path NCL script (net$searchpath_startup.ncl). ______________________________________________________ 7.20 Customizing the Network Configuration To customize your system beyond what the net$configure procedure provides, you must edit the NCL scripts produced by net$configure (refer to the HP DECnet-Plus for OpenVMS Network Management manual). HP recommends that you use the net$configure procedure for major modifications involving an entire entity. 7.20.1 Creating User-Defined Scripts You can use user-defined site-specific NCL scripts for the Event Dispatcher, MOP client, application, and search path entities. (See Section B.1.1 for further information about creating the site-specific search path script.) The network startup procedure (net$startup.com) calls four site-specific NCL scripts (if they exist) when the network is started. These scripts must be in sys$manager. They are called immediately after their net$configure generated counterparts are executed. The following table lists the scripts and their counterparts. Modifying a Current Configuration 7-77 Modifying a Current Configuration 7.20 Customizing the Network Configuration ___________________________________________________________ User-Defined Generated Site-Specific_Script____________Script_____________________ net$event_local.ncl net$event_startup.ncl net$application_local.ncl net$application_startup.ncl net$mop_client_local.ncl net$mop_client_startup.ncl net$searchpath_local.ncl________net$searchpath_startup.ncl_ Such user-defined scripts are user-maintained and thus are not overwritten or deleted by net$configure. HP recommends that, whenever possible, you place your site-specific changes in these user-defined NCL scripts. HP provides a template for the net$event_local.ncl file. The template is located in the sys$manager: directory with the file name net$event_local.template. Simply copy the file to net$event_local.ncl and make any changes for your system. ________________________ Note ________________________ If you invoke net$configure to edit a standard NCL script (net$entity_startup.ncl), the standard NCL script is superseded and renamed to net$entity_ startup.ncl-old (where entity is a particular entity name). ______________________________________________________ If you must make changes to the standard NCL scripts and you want to retain your modifications after invoking net$configure, you can either manually edit the NCL script to replace the user modifications or rename the appropriate net$entity_startup.ncl-old script back to net$entity_ startup.ncl. Be sure to incorporate any new changes as well. The net$configure procedure flags these modifications the next time it checksums the scripts. 7-78 Modifying a Current Configuration Part III _________________________________________________________________ Configuring X.25 Functionality on DECnet-Plus for OpenVMS VAX Systems Part III describes the steps necessary to configure X.25 functionality on DECnet-Plus for OpenVMS VAX systems. This functionality was previously a separate product known as VAX P.S.I. 8 _________________________________________________________________ Configuring X.25 for OpenVMS VAX This chapter describes how to configure X.25 functionality on DECnet-Plus for OpenVMS VAX systems (this functionality was formerly provided by a separate product known as VAX P.S.I.). The functionality formerly provided by VAX P.S.I. is now included with the DECnet-Plus for OpenVMS VAX software. ________________________ Note ________________________ You must elect to install this functionality during installation of the DECnet-Plus for OpenVMS VAX software (see Section 3.1.2). ______________________________________________________ 8.1 Terminology The terminology used in the VAX P.S.I. product has been replaced by the terminology used in the documentation for the separate X.25 for OpenVMS product used on OpenVMS I64 and OpenVMS Alpha systems. Table 8-1 shows the correlation between VAX P.S.I. terms and their X.25 for OpenVMS counterparts. Table_8-1_X.25_Terminology_________________________________ VAX_P.S.I.____________X.25_for_OpenVMS_____________________ VAX P.S.I. X.25 for OpenVMS VAX Access system X.25 Client system Native system X.25 Direct Connect system (continued on next page) Configuring X.25 for OpenVMS VAX 8-1 Configuring X.25 for OpenVMS VAX 8.1 Terminology Table_8-1_(Cont.)_X.25_Terminology_________________________ VAX_P.S.I.____________X.25_for_OpenVMS_____________________ Multihost system X.25 Connector system Gateway_system________X.25_Connector_system________________ 8.2 Steps in Configuring X.25 for OpenVMS VAX See Figure 8-1 and take the following steps to configure X.25 functionality on your OpenVMS VAX system: 1. Plan your configuration (see the DECnet-Plus Planning Guide manual and Section 8.3). 2. Make a list of the information you need during the configuration program, using Section 8.6. 3. Run the X.25 configuration program (see Section 8.4). 4. Run the net$configure program (in either BASIC or ADVANCED mode) to configure your network. 5. Carry out the postconfiguration tasks: starting X.25 and testing your configuration (see Section 8.7). 8.3 Planning the X.25 Configuration This section introduces the aspects of your proposed configuration that you need to consider before you run the configuration program. 8.3.1 Configuring Client, Direct Connect, and Connector Systems There are three types of X.25 for OpenVMS systems: o Client (formerly known as Access) o Direct Connect (formerly known as Native) o Connector (formerly known as Multihost) ________________________ Note ________________________ The older system type names are still used by the X.25 configuration utility. The newer terms are used here 8-2 Configuring X.25 for OpenVMS VAX Configuring X.25 for OpenVMS VAX 8.3 Planning the X.25 Configuration for compatibility with the remainder of the X.25 for OpenVMS documentation set. ______________________________________________________ Refer to the DECnet-Plus for OpenVMS Introduction and User's Guide manual for an explanation of X.25 fundamentals. The types of systems you can configure depend on the licenses that you have installed. Table 8-2 summarizes the various possible configurations. Table 8-2 X.25 for OpenVMS VAX Configurations and License __________Requirements_____________________________________ Licenses________Possible_X.25_Configurations_______________ DECnet-Plus Client system only X.25 Direct Connect system DECnet-Plus Client and X.25 Direct Connect Connector Client and Direct Connect ________________Client_and_Connector_______________________ Configuring X.25 for OpenVMS VAX 8-3 Configuring X.25 for OpenVMS VAX 8.4 Using the Configuration Program 8.4 Using the Configuration Program To configure X.25 functionality on your OpenVMS VAX system, you need to run the psi$configure.com command program. This program allows you to set up the permanent configuration database for X.25 functionality on an OpenVMS VAX system. 8.4.1 Invoking the Configuration Program To start the X.25 configuration program, log in to any account that has OPER and SYSPRV privileges and enter the command: $ @sys$manager:psi$configure 8.4.2 Common Operations The configuration program consists of a number of sections, each corresponding to a logical group of information. Each section consists of one or more screens on which you can enter data. All sections (with the exception of the X.29 and Mail support section) also have an introductory information screen. Most sections are optional. These sections begin with a question of the form: "Do you want to set up X?" If you select Yes, you go through the rest of the section. If you select No, you go directly to the next new section, although you can decide at a later stage to complete that section (See Section 8.4.5). 8.4.2.1 Entering Information The program prompts you for information in two ways: o For some questions, you choose your answer from a menu by using the arrow keys and pressing Return. o For other questions, you type data into a field and press Return. When you have entered all the required information on a screen, a new screen appears automatically. You cannot move forward until you have completed the required fields. 8-4 Configuring X.25 for OpenVMS VAX Configuring X.25 for OpenVMS VAX 8.4 Using the Configuration Program ________________________ Note ________________________ The configuration program indicates it is processing input by flashing the message working in the bottom left-hand corner of the screen. ______________________________________________________ Horizontal Scrolling Usually, when you type data into a field, you can see the entire field on the screen. However, in some cases, the maximum length of the data you are allowed to type is too long to fit into the field shown on the screen; for example, a node name, which may be up to 400 characters. In such cases, the field scrolls horizontally as you enter data. Note that horizontal scrolling works only if the keyboard is in Insert mode. Data Entry Mode By default, each data entry screen is invoked in Overstrike mode. In this mode, any characters entered overwrite any characters currently displayed in the data entry field. If required, a data entry screen can be placed in Insert mode. In this mode, any characters entered are inserted into the characters currently displayed; any previously entered characters are moved to the right. To change from one mode to the other, press . The current mode is displayed in the upper right-hand corner of the data entry screen. 8.4.2.2 Moving Within a Section To move backward within a section, press the key. You are allowed to move backward within a section whether you have finished it or not. However, you can move backward only as far as the first screen of the section. To reach another section, use the Sections Menu (see Section 8.4.5). If you have moved back to look at completed screens, you can move forward again by pressing the key. Do this until you reach an incomplete screen. Then complete the required fields on that screen before moving on. Configuring X.25 for OpenVMS VAX 8-5 Configuring X.25 for OpenVMS VAX 8.4 Using the Configuration Program 8.4.3 Moving Between Sections The methods available for moving between sections depend on whether you are creating or modifying a configuration. When creating a configuration, an Options Menu is displayed when you complete the last data entry screen in a section. This menu includes options that allow you to move to the next uncompleted section or to move to a previously completed section (via the Sections Menu): o To move to the next uncompleted section, select the option "Continue to a new section". o To move to a previously completed section, select the option "Go to Sections Menu". Full details of the Options Menu are provided in Section 8.4.5. When modifying a configuration, a specific section can be selected from the Sections Menu. The Sections Menu is displayed automatically after you select the option Modify an existing configuration script, or can be accessed from the Options Menu of the current section by selecting the option "Go to Sections Menu" (refer to Section 8.4.5). 8.4.4 Keys Used in the Configuration Program Table 8-3 lists the keys you can use when running the configuration program. Note that if your terminal does not support cursor keys, you cannot move between fields, and therefore you cannot run the configuration program from the terminal. To use the cursor keys, you must ensure that the terminal device type is set correctly so that it reflects the terminal being emulated. To set the terminal device type, enter the command: $ SET TERM/DEVICE=terminal_type where terminal_type is specified as VT300, VT200, and so on. 8-6 Configuring X.25 for OpenVMS VAX Configuring X.25 for OpenVMS VAX 8.4 Using the Configuration Program ________________________ Note ________________________ If you intend to run the configuration program in a DECterm window, the terminal type must be set to VT320. To set the correct terminal type: 1. Select the Options pull-down menu. 2. Select the General... option. 3. Select VT300 Mode, 7--Bit Control and Terminal ID VT320 ID. 4. Select OK. ______________________________________________________ Table 8-3 Available Keys Used by the X.25 Configuration __________Program__________________________________________ DEC Terminal (VT200 or higher)_Keys__________________Function_____________________ Movement Keys UP and DOWN arrow keys Moves cursor between fields LEFT and RIGHT arrow keys Moves cursor within a field Takes you to the previous screen in the current section Takes you to the next screen in the current section Moves cursor to end of input field Moves cursor to start of input field Edit Keys ,