HP OpenVMS Systems Documentation

Order Number: AA--QPSVB--TE

This book explains how to install and configure the layered application products on the DECnet-Plus for OpenVMS software.

Revision/Update Information: This is a revised manual.

Operating Systems: OpenVMS Alpha Version 7.1
OpenVMS VAX Version 7.1

Software Versions: DECnet-Plus for OpenVMS Version 7.1
X.25 for OpenVMS Alpha Version 7.1

Digital Equipment Corporation Maynard, Massachusetts

Digital Equipment Corporation makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description.

Possession, use, or copying of the software described in this publication is authorized only pursuant to a valid written license from DIGITAL or an authorized sublicensor.

DIGITAL conducts its business in a manner that conserves the environment and protects the safety and health of its employees, customers, and the community.

© Digital Equipment Corporation 1996. All rights reserved.

The following are trademarks of Digital Equipment Corporation: Bookreader, DDCMP, DEC, DECdirect, DECnet, DECNIS, DECserver, DECsystem, DECwindows, DIGITAL, DNA, InfoServer, OpenVMS, PATHWORKS, ULTRIX, VAX, VAX DOCUMENT, VAXcluster, VAXstation, VMS, VMScluster, and the DIGITAL logo.

The following are third party trademarks:

Macintosh is a registered trademark of Apple Computer, Inc.
MS-DOS is a registered trademark of Microsoft Corporation.
Multinet is a registered trademark of TGV, Inc.
OS/2 is a registered trademark of International Business Machines Corporation.
OSF/1 is a registered trademark of Open Software Foundation, Inc.
PATHways is a registered trademark of The Wollongong Group.
SCO is a trademark of Santa Cruz Operations, Inc.
TCPware is a registered trademark of Process Software Corporation.
UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Co. Ltd.

All other trademarks and registered trademarks are the property of their respective holders.

This document was prepared using VAX DOCUMENT, Version V3.2m.

This is the second book you should read in order to successfully install and configure:

• X.25 for OpenVMS Alpha
• VAX P.S.I. and VAX P.S.I. Access for OpenVMS VAX
• OSI layered software applications
  • File Transfer, Access, and Management (FTAM)
  • Virtual Terminal (VT)
  • OSI Applications Kernel (OSAK)

It also describes how to configure DECnet-Plus for OpenVMS using the ADVANCED configuration option and information about name services.

Intended Audience

This book is written for:

• Network planners and managers
• OpenVMS system managers
• DECnet-Plus software installers

Structure of This Book

This book has five parts:

Terminology

The following terms are used interchangeably in this book.

• Alpha and AXP
• Transition and migration
• Phase IV and DECnet Phase IV
• End system and end node
• Intermediate system and router
• DECnet-Plus and Phase V

Related Documents

The following books provide additional information.

• DECnet-Plus for OpenVMS Installation and Basic Configuration
  The first book to read in order to successfully install DECnet-Plus for OpenVMS. It also includes how to configure DECnet-Plus using the BASIC configuration and information about name services.
• DECnet-Plus for OpenVMS Introduction and User's Guide
  Introduces the DECnet-Plus for OpenVMS features and tools, and how to use and manage a DECnet-Plus for OpenVMS end system. Also provides a comprehensive glossary of DECnet-Plus terminology.
• DECnet-Plus Planning Guide
  Explains in detail the transition from DECnet Phase IV to DECnet-Plus, providing configuration guidelines and planning tasks.
• DECnet-Plus DECdns Management
• DECnet-Plus DECdts Management
• DECnet-Plus for OpenVMS Network Management
• X.25 for OpenVMS Configuration Guide
• DECnet-Plus FTAM and Virtual Terminal Use and Management
• OpenVMS License Management Utility Manual
• OpenVMS System Management Utilities

For additional information on the DECnet-Plus products and services, access the DIGITAL OpenVMS World Wide Web site. Use the following URL:

http://www.openvms.digital.com

Reader's Comments

DIGITAL welcomes your comments on this manual or any of the DECnet-Plus documents. Send us your comments through any of the following channels:

How To Order Additional Documentation

Use the following table to order additional documentation or information. If you need help deciding which documentation best meets your needs, call (800-282-6672).

Conventions

The following conventions are used in this book.

Part I describes the steps necessary to use the ADVANCED configuration option for DECnet-Plus for OpenVMS. It includes the following chapters:

• Chapter 1 --- Using the ADVANCED Configuration Option
• Chapter 2 --- Managing Name Services
• Chapter 3 --- Modifying a Current Configuration

This chapter describes how to configure the DECnet-Plus for OpenVMS base components using the ADVANCED configuration option so that the system becomes a DECnet-Plus end system on a network. The ADVANCED configuration option allows you to customize your system's network configuration.

If you have already configured the DECnet-Plus for OpenVMS software and you want to modify the configuration, see Chapter 3.

1.1 Invoking the ADVANCED Configuration Option

To invoke the net$configure.com procedure using the ADVANCED configuration option, enter the following command:

$ @sys$manager:net$configure advanced

The procedure starts:

Copyright (c) Digital Equipment Corporation 1993, 1996. All rights reserved.

   DECnet-Plus for OpenVMS ADVANCED network configuration procedure

This procedure will help you create or modify the management scripts
needed to operate DECnet on this machine. You may receive help about
most questions by answering with a question mark '?'.

You have chosen the ADVANCED configuration option.  This option enables
you to do some specific tailoring of your system's network configuration
by answering some specific questions.  If you do not want to do specific
tailoring of your system's network configuration but instead want to
quickly configure your system using most of the default answers, you
should invoke NET$CONFIGURE.COM with the BASIC configuration option, ie:
               @SYS$MANAGER:NET$CONFIGURE BASIC

* Do you want to continue?                             [YES] :

Press Return to continue with the net$configure ADVANCED configuration option.

The following illustrates the main menu options from which you can choose:

        Configuration Options:

        [0]     Exit this procedure

        [1]     Perform an entire configuration
        [2]     Change naming information
        [3]     Configure Devices on this machine
        [4]     Configure Transports
        [5]     Configure Timezone Differential Factor
        [6]     Configure Event Dispatcher
        [7]     Configure Application database
        [8]     Configure MOP Client database
        [9]     Configure Cluster Alias
        [10]    Replace MOP Client configuration
        [11]    Configure satellite nodes
        [12]    Configure cluster script locations

* Which configuration option to perform?                 [1] : 1

If you select Option 1, the procedure informs you that this is the first time you are configuring your system to use DECnet-Plus for OpenVMS:

%NET$CONFIGURE-I-SETUPNEW, setting up for new configuration

If a Phase IV database exists on the system, the following message displays:

%NET$CONFIGURE-I-PHASEIVDATA, Phase IV DECnet database found

You have the option of using the existing Phase IV database to generate the Network Control Language (NCL) scripts and configure the system. If you do not want to use the existing Phase IV database to generate the NCL scripts and configure the system, then net$configure configures the system based on your answers to the configuration questions.

* Do you want to convert Phase IV databases?             [NO] : yes

If you answer YES, the procedure prompts you for the Phase IV prefix (see Section 1.2.10 for more information):

* Enter Phase IV Prefix                                [49::] :

The net$configure procedure uses the system's existing Phase IV database to generate NCL scripts and configure the system.

If you answer NO, the net$configure procedure does not use the system's existing Phase IV database to generate NCL scripts and proceeds to ask all the configuration questions. If you need more information to answer a question, you can type a question mark (?) at the prompts. To configure DECnet, you need to know your node's full name and network address or addresses.

1.2 Directory Name Services

DECnet-Plus provides access to the node name and addressing information stored in one or more name services. DECnet-Plus supports the following directory name services:

• Local namespace --- A discrete, nondistributed namespace that stores name and address information locally in database files, the Local namespace replaces the DECdns Local Naming Option (LNO). It also has the ability to hold 100,000 nodes, and can scale beyond that number. The actual number of nodes that the Local namespace can hold depends on the space available on your system. For more detailed information on namespaces, see Section 2.1.
• DECdns distributed namespace --- DIGITAL's Distributed Name Service, DECdns is a distributed, global name service. For more information, see Section 2.1.2.
• Domain Name System --- The Domain Name System (DNS/BIND) is supported for storage of IP addresses. For more information see Section 2.1.3.

If you choose to enter more than one directory name service for your system, enter them in order of priority. The ordering of this list is very important: the first directory service entered in this list is considered the primary directory service to use on the system. The primary directory service is considered the first choice to use when looking up naming information for the system.

Enter an ordered list of the directory services you want to use on the system. If you enter more than one directory service, separate each service with a comma.

* Enter the directory services to use on the system [LOCAL,DECDNS,DOMAIN] :

For example, if you enter LOCAL,DECDNS,DOMAIN at the prompt, this means the following:

• You want to use the name services DECdns, Local, and DNS/BIND.
• The primary name service is DECdns.
• The secondary name services are Local and DNS/BIND, in that order.

Enter a node full name for each directory service chosen. The node full name is the name of your system's node object in the directory service. It includes the namespace nickname and the full list of directories leading to the node object name. Examples of node full names include:

 Local namespace -  LOCAL:.TomThumb
 DECdns          -  ACME:.wabbit.Elmer
 Domain          -  elmer.wabbit.acme.edu

For the Local namespace, the namespace nickname LOCAL is prepended to the full name and is terminated with a colon (:). The namespace nickname LOCAL means that the Local namespace is used. The node object name must begin with a dot (.), and no element of the name (namespace name, directory, or node object name) can be a null string. Note that the namespace nickname LOCAL is reserved, and indicates that the Local namespace is used on this system. For example, if you enter "Local, DECdns, Domain" at the previous prompt, you will be asked for a DECdns full name, a Local full name, and a fully qualified host name for DNS/BIND.

* 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

The node synonym is an alphanumeric character string between one and six characters long. The first character must be an alphabetic character; after the first character, the string can contain either alphabetic or numeric characters.

If this system had previously been running DECnet Phase IV software, then you should use the old Phase IV node name as the synonym. If this system is joining a DECnet network for the first time, you can use any name for the synonym, as long as it meets the criteria listed above, and is unique within the network.

* What is the synonym name for this node?            [ELMER] :

For more information on node synonym directories, see Section 2.4.

1.2.3 Naming Cache Timeout Value

A naming cache is used to improve the performance of node name address resolution. This cache supersedes the existing DECdns cache and is used when looking for addresses in the Domain and Local services, in addition to DECdns. Note that other applications that directly use DECdns continue to use the DECdns cache.

The naming cache includes a mechanism to "time out" old entries. In this way, these entries are refreshed periodically to accurately reflect the actual network environment.

* Naming cache timeout value?                  [30-00:00:00] :

You have the option to set a value for the naming cache timeout interval. Enter any legal OpenVMS delta time value (the default is 30 days).

1.2.4 Session Control Address Update Interval

The session control address update interval is the time, in seconds, between updates of local tower address information.

* Session Control Address Update Interval ?       [10] :

To choose a ten second interval, press Return. Otherwise, enter your own interval and press Return.

1.2.5 Naming Cache Checkpoint Interval

Periodically, DECnet-Plus saves a snapshot of the in-memory naming cache to disk. This allows systems, during startup, to have a naming cache that is already populated with entries, thereby preserving the contents of the naming cache across system reboots.

* Naming cache checkpoint interval?               [08:00:00] :

You have the option of setting the naming cache checkpoint interval. Enter any legal OpenVMS delta time value (the default is 8 hours).

1.2.6 Specifying the Node Type

Prior to DECnet-Plus Version 7.1, DECnet-Plus systems were end nodes. Dedicated routers on the network performed routing functions for the end nodes as necessary. With the Version 7.1 release, DECnet-Plus allows a system to run Integrated IS-IS, thus providing host-based routing functionality. The default is to be an end node.

* What type of node (Endnode or Router)?           [ENDNODE] :

The UTC (Coordinated Universal Time) is calculated automatically by using the OpenVMS UTC. The procedure displays the following message:

Determining DTSS timezone rules from OpenVMS information...

After the initial system configuration, you can choose to reconfigure the system's time zone rule (TZR) by selecting Option 5 in the top-level net$configure menu in either the BASIC or ADVANCED configuration procedure.

1.2.8 Specifying Routing Information

This section only applies if your DECnet-Plus system is a router.

* Type of routing node (L1 or L2)?                      [L1] :

Enter L1 if your DECnet-Plus system will provide intra-area level 1 routing capability. Enter L2 if your DECnet-Plus system will provide inter-area level 2 routing capability. The default is to be a level 1 router.

* Maximum path splits                                    [2] :

This specifies the maximum number of equal cost paths to split between.

* PhaseIV Maximum Address                             [1023] :

Specifies the maximum node number within a Phase IV area.

* PhaseIV Maximum Area                                  [63] :

This question only applies if your DECnet-Plus system is a level 2 router. It indicates the maximum Phase IV area number.