Updated: 24 May 2001

DECnet-Plus for OpenVMS
Applications Installation and Advanced Configuration

The following questions determine if you want to set up and use a default account for application objects. You can create default accounts for the following applications: FAL, CML, MAIL, VPM, MIRROR, and PHONE.

* Do you want to use a default account for the 'FAL' application? [NO] :

File access listener (FAL) is an image that provides authorized access to the file system of a DECnet node on behalf of processes executing on any DECnet node in the network. FAL communicates with the initiating node by means of the Data Access Protocol (DAP). If you want an account set up or used for FAL, answer YES.

* Do you want to use a default account for the 'CML' application? [YES] :

CMIP Management Listener (CML) is the DECnet-Plus management module that implements the Common Management Information Protocol (CMIP). It is a utility that provides access to CMIP. If you want an account set up and used for CML, answer YES.

%NET$CONFIGURE-I-MAKEACCOUNT, this procedure creates user account CML$SERVER

* Do you want to use a default account for the 'MAIL' application? [YES] :

If you want to use the OpenVMS MAIL utility, answer YES.

%NET$CONFIGURE-I-MAKEACCOUNT, this procedure creates user account MAIL$SERVER

* Do you want to use a default account for the 'VPM' application? [YES] :

If you want the system to be an OpenVMS Cluster node, answer YES. The VMScluster Performance Monitor (VPM) needs an account on your system to support the OpenVMS Monitor utility command monitor cluster. Answer NO if the system is to be a non-cluster end system.

If you answer YES, you will see the following message:

%NET$CONFIGURE-I-MAKEACCOUNT, this procedure creates user account VPM$SERVER

* Do you want to use a default account for the 'MIRROR' application? [YES] :

MIRROR is used for some forms of loopback testing. If you want to use MIRROR, answer YES.

%NET$CONFIGURE-I-MAKEACCOUNT, this procedure creates user account MIRRO$SERVER

* Do you want to use a default account for the 'PHONE' application? [YES] :

The PHONE utility allows users on the same or different OpenVMS systems to communicate interactively. If you intend to use the OpenVMS PHONE utility, answer YES.

%NET$CONFIGURE-I-MAKEACCOUNT, this procedure creates user account PHONE$SERVER

1.8 Configuring a Cluster Alias

The following steps describe how to configure a cluster alias.

1. If the node is an OpenVMS Cluster member or if net$configure finds an alias NCL script on the system, the procedure prompts you to enter the full name of a cluster alias.

   * Full name of Cluster Alias : ACME:.WABBIT.HELP

   
   If you do not want the node to participate in a cluster alias, press Return.
   If you want the node to participate in a cluster alias, specify the full name that uniquely identifies the cluster alias node (for example, ACME:.WABBIT.HELP).

2. If you entered a cluster alias full name in response to the previous prompt, the procedure displays the following prompt:

   * Cluster Alias Phase IV Address (aa.nnnn OR AA-00-04-00-xx-xx) : 12.139

   
   Specify either the DECnet Phase IV node address or Ethernet physical address of the alias.
   The Phase IV node address has the format area-number.node-number (for example, 12.139).
   The Ethernet physical address has the format AA-00-04-00-xx-xx, where xx-xx is calculated from the Phase IV node address. To determine the Ethernet physical address, proceed as follows:

   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)

3. If you entered a cluster alias full name and a Phase IV address, the procedure displays the following prompt:

   * Selection weight for this cluster node [0 for satellites] :

   
   The selection weight determines the number of sequential incoming connects passed to this alias member node in the round-robin sequence before proceeding to the next member node in the sequence. A value of zero means this node is not eligible to receive incoming connections to this alias address. Selection weight apportions incoming alias connections according to the capacity of each alias member. For example, nodes with greater capacity should have larger values of selection weight, while OpenVMS Cluster satellites should generally have a value of zero. Specify a nonzero selection weight if this node is connected locally to a dual-ported disk, or if it will be serving any multihost disks, such as RFxx or HSC-connected disks, to other cluster members. DIGITAL recommends values between 0 and 10.

The following describes the configuration summary and the network startup.

1. The procedure then displays:

   Summary of Configuration Node Information Node Type: L2ROUTER Directory Services Chosen: DECDNS,LOCAL,DOMAIN Primary Directory Service: DECDNS DECdns Full name: ACME:.WABBIT.ELMER Local Full name: LOCAL:.ELMER Fully Qualified Host name: ELMER.WABBIT.ACME.EDU Node Synonym: ELMER Phase IV Address: 15.27 Phase IV Prefix: 49:: Autoconfiguration of Network Addresses: Disabled Session Control Address Update Interval: 10 Routing ESHello Timer: 600 Device Information: Device: ESA0 (DESVA): Data Link name: CSMACD-0 Routing Circuit Name: CSMACD-0 L1 circuit cost: 8 L2 circuit cost: 8 L1 router priority: 64 L2 router priority: 64 Transport Information: NSP Transport: Configured Maximum number of logical links: 200 Maximum Transmit and Receive Window: 20 Maximum Receive Buffers: 4000 OSI Transport: Configured Maximum number of logical links: 200 Maximum Transmit and Receive Window: 20 Maximum Receive Buffers: 4000 Congestion Avoidance Disabled Event Dispatcher Configuration: Sinks: local_sink Outbound Streams: local_stream Phase IV Relay: Enabled * Do you want to generate NCL configuration scripts? [YES] :

   
   Answer YES to accept the configuration you just specified. The procedure automatically generates the NCL scripts and then configures the system according to the information you supplied.

   %NET$CONFIGURE-I-CHECKSUM, checksumming NCL management scripts

   Note The net$configure procedure only provides checksums of those NCL management scripts it creates or modifies. It does not provide checksums of user-modified NCL scripts.

2. The procedure displays the following prompt:

   * Do you want to start the network? [YES] :

   
   Answer YES if you want to start the network and complete your system's network configuration.
   If you want to postpone starting the network, answer NO. When you answer NO, the procedure displays the following message:

   ******************************************************************** You have decided not to start the network. NET$CONFIGURE.COM cannot complete your system's network configuration since it needs the network to be partially started in order to perform certain operations. As a result, your system may be left in an inconsistent state if you try to startup the network manually or if you decide to reboot your system. Once you are ready to start the network, please invoke the NET$CONFIGURE.COM procedure, choose menu option 2 (Change node name/namespace name), and respond YES to starting the network so that the configuration procedure can finish your system's network configuration. ******************************************************************** Network Startup Incomplete

   
   DIGITAL recommends that you answer YES and start the network.

3. When you choose to start the network, the procedure displays information similar to the following:

   Copyright (c) Digital Equipment Corporation 1996. All rights reserved. . . . %NET$STARTUP-I-OPERSTATUS, DECnet-Plus for OpenVMS operational status is RUNNING-MAJOR sys$manager:net$dns_clerk_startup.ncl changed to use the new default namespac Your default namespace nickname is ACME. Your default namespace NSCTS is 08-00-2B-0D-2E-89-23-5B-15-9E-F1-85-95-00. Node 0 at 1996-01-26-14:12:24.170-04:00I0.404 %NET$CONFIGURE-I-NODERENAMED, node successfully renamed to ACME:.WABBIT.ELMER Directory Service: DECdns

4. You can ignore the Error - Node name lookup failure message during startup.

   Error - Node name lookup failure ACME:.WABBIT.ELMER Number of nodes reported on: 0 %NET$CONFIGURE-W-NODENOTREG, node is not completely registered yet in the DECdns directory service Directory Service: Local name file Error - Node name lookup failure LOCAL:.ELMER Number of nodes reported on: 0 %NET$CONFIGURE-W-NODENOTREG, node is not completely registered yet in the LOCAL directory service %NET$CONFIGURE-I-IMPORTFILECREATED, created the DECNET_REGISTER import file Directory Service: DECdns Updating nodes listed in SYS$MANAGER:DECNET_REGISTER_IMPORT_FILE_ELMER.TXT Number of nodes registered: 1 Number of nodes modified: 0 %NET$CONFIGURE-I-REGSUCCESS, node has been successfully registered in the DECdns directory service Directory Service: Local name file Updating nodes listed in SYS$MANAGER:DECNET_REGISTER_IMPORT_FILE_ELMER.TXT Number of nodes registered: 1 Number of nodes modified: 0 %NET$CONFIGURE-I-REGSUCCESS, node has been successfully registered in the LOCAL directory service Node 0 at 1996-01-26-14:13:25.980-04:00I0.411 %NET$CONFIGURE-I-NODERENAMED, node successfully renamed to ACME:.WABBIT.ELMER Node 0 Session Control Tower Maintenance ACME:.WABBIT.ELMER at 1996-01-26-14:13:35.360-04:00I0.411 %NET$CONFIGURE-I-TOWERSUPDATED, updated address towers for node Node 0 Session Control Backtranslation Softlink * at 1996-01-26-14:13:43.360-04:00I0.412 Node 0 Session Control Backtranslation Softlink * at 1996-01-26-14:13:43.370-04:00I0.412 %NET$CONFIGURE-I-BCKTRNUPDATED, updated backtranslation softlink for node %NET$CONFIGURE-I-CONFIGCOMPLETED, DECnet-Plus for OpenVMS configuration completed $

   
   You have just completed the initial configuration of a DECnet-Plus for OpenVMS system. It should now be operational on the network. You can now use the SET HOST command to connect to other network nodes.

If this is the first time you are configuring the DECnet-Plus for OpenVMS software on your system, the information in this chapter further explains some of the topics that appear as you run the configuration procedure.

2.1 Names Services Overview

While configuring DECnet-Plus, the system administrator specifies one or more of the following directory name services to use on the node: the Local namespace, DECdns, or Domain Name System (for DNS/BIND).

• Local namespace --- A discrete, nondistributed namespace that stores name and address information locally in database files. DECnet-Plus includes a Local namespace.
• DECdns --- DIGITAL's Distributed Name Service, a distributed, global name service.
• Domain Name System --- The Domain Name System (DNS/BIND) supported for storage of IP addresses.

For more information on name services, refer to the DECnet-Plus Planning Guide.

2.1.1 The Local Namespace

DECnet-Plus includes a Local namespace, independent of DECdns, that is designed to scale to at least 100,000 nodes.

The Local namespace is a discrete, nondistributed namespace that exists on a single node and provides that node with a local database of name and address information. The prefix LOCAL: (or local:) is reserved to indicate that the information for the node is stored in the Local namespace.

DECnet-Plus recognizes that when a node full name begins with LOCAL:, information for that node is stored in a Local namespace.

Unlike DECdns, the Local namespace does not employ backtranslation directories for address-to-node-name translation.

2.1.1.1 Creating a Local Namespace

If you want to create a Local namespace, enter LOCAL:.DirectoryPath.NodeObject at the following prompt:

* Enter the full name for directory service LOCAL:

The directory path identifies the namespace subdirectory (if any). The node object is the system's node name. The following are typical node full names properly formatted for the Local namespace: LOCAL:.xyz.abc and local:.maximum.

2.1.1.2 Managing the Local Namespace

The DECdns distributed namespace is not a requirement for DECnet-Plus, and the Local namespace does not depend on DECdns. However, the DECdns clerk software is still required on each node. You cannot use the DECdns Control Program (DNSCP) to manage information stored in the Local namespace. Instead, use decnet_register. The decnet_register tool is described in the DECnet-Plus for OpenVMS Network Management guide.

2.1.2 The DIGITAL Distributed Name Service (DECdns)

DECdns is a networkwide service that makes it possible to use network resources without knowing their physical location. Users and applications can assign DECnet-Plus names to resources such as nodes. The creator of a name also supplies other relevant information for DECdns to store, such as the resource's network address. Users then need to remember only the name, and DECdns acts as a lookup service, providing the rest of the data when necessary.

2.1.2.1 Creating a New Namespace

You need to create a new DECdns namespace only if you are configuring the first DECdns server for the network or if you are creating an additional namespace. If you already have a DECdns namespace, you do not need to create a new namespace to be able to run DECnet-Plus. However, if this is the first system in a network where no namespace exists and you do not intend to use the Local namespace, you must create (and populate) a DECdns namespace.

If you are unsure whether you need to create a new namespace or configure your system as a server, see your network manager. For information about namespace planning, refer to the DECnet-Plus Planning Guide.

To create a new namespace while configuring a DECnet-Plus for OpenVMS system:

• The DECdns server software must be installed on the system.
• DECdns must be specified as one of the naming services configured on the system.

When you create a namespace, you need a namespace nickname and clearinghouse name. The namespace nickname is part of the full name of every subsequent system in the network and should be unique to your network. The namespace nickname that you specify becomes the actual name of the namespace. A clearinghouse is a collection of directory replicas that contains the names and addresses of objects (for example, servers, clerks, files).

DIGITAL recommends that you create namespace directories before using the configuration procedure (net$configure.com) to create the namespace. Follow these steps to create namespace directories:

1. Invoke decnet_register and select option 10 ("Manage the directory service").
2. Follow directions. Be sure to specify DECdns as the directory service to manage (the Local namespace is the default). The decnet_register procedure invokes sys$manager:decnet_register_decdns.com to create the namespace directories.
3. When finished, invoke the configuration procedure to create the new namespace.

For more information on decnet_register, refer to DECnet-Plus for OpenVMS Network Management.

2.1.2.2 Creating a DECdns Namespace

If you select DECdns as a directory service, net$configure prompts you for the full name you want to use:

* Enter the full name for directory service DECDNS: new_ns:.mrv042 [Return]

If this is a new DECdns namespace, net$configure prompts you for more information once the configuration procedure completes and you have started the network. The startup information will be similar to the following:

%NET$STARTUP-I-OPERSTATUS, DECnet-Plus for OpenVMS operational status is RUNNING- MAJOR The namespace you specified was NEW_NS. %DNS-E-NOMATNS, The specified namespace is not being served on your LAN. please choose from the following list [ 1] BB_NS [ 2] DOMAIN [ 3] LOCAL [ 4] X500 [ 0] - Reject this list - Pick a number from the list: 0 [Return]

Because you are creating a new namespace, the namespace you specified at the prompt, "What is the full name of this node ?" does not appear in the list. To continue, enter 0 and press Return to reject the list.

If you are installing DECnet-Plus for VMS 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 [Return]

At this point, the configuration procedure needs to determine whether you intend to configure your system as a clerk on a WAN (connect to an off-LAN server), or create a new namespace. Since you cannot create a new namespace unless you have installed DECdns server software on the system, the procedure first verifies that the server software has been installed.

If you want to create a new namespace, type YES at the prompt and press Return. The procedure continues prompting you for information necessary to create the namespace and the appropriate directories. The procedure displays information about the namespace, the directories, and other network parameters, then tells you when the configuration is complete.

Your next input will determine the name of the clearinghouse in your namespace new_ns. Enter the clearinghouse name as alphanumeric and/or underscore characters. Enter a simple name for the clearinghouse: .mrv042_new_ns_ch [Return] Node 0 at 1995-04-06-15:49:35.420-04:00Iinf Creating DECdns Server process ... %RUN-S-PROC_ID, identification of created process is 00000122 Your default namespace nickname is new_ns. Node 0 at 1995-04-06-15:49:42.100-04:00Iinf %NET$CONFIGURE-I-FLUSHCACHE, flushing selected cache entries Node 0 at 1995-04-06-15:49:47.180-04:00Iinf %NET$CONFIGURE-I-NODERENAMED, node successfully renamed to new_ns:.mrv042 %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=47:0027:]: [Return] * Maximum Phase IV area to use [1-63, Def=63]: 2 [Return] The DECdns namespace groups and directories will now be created. This might take up to 6 minutes or more, depending on the speed of the DECdns server system and the amount of traffic on the network. Creating the NEW_NS:.DNA_Registrar group. Creating the NEW_NS:.DNA_BackTranslation directory. Creating the NEW_NS:.DNA_BackTranslation.%X470027 directory. Creating the NEW_NS:.DNA_BackTranslation.%X470027.%X0001 directory. Creating the NEW_NS:.DNA_BackTranslation.%X470027.%X0002 directory. Creating the NEW_NS:.DNA_NodeSynonym directory. Creating the NEW_NS:.DTSS_GlobalTimeServers directory. DECdns namespace initialization for DECnet use is complete. If this is the first time you have initialized the namespace for DECnet use, use SYS$SYSTEM:DECNET_REGISTER.EXE to: - 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. - 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 PhaseIV 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 NEW_NS:.DNA_Registrar access control group. 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: NEW_NS:.DNA_Registrar Directory: NEW_NS:.DNA_BackTranslation Directory: NEW_NS:.DNA_BackTranslation.%X470027 Directories: NEW_NS:.DNA_BackTranslation.%X470027.* Directory: NEW_NS:.DNA_NodeSynonym Directory: NEW_NS:.DTSS_GlobalTimeServers %NET$CONFIGURE-I-CREATEINITDIR, created initial namespace directories Registering the node NEW_NS:.mrv042 Type is DECnet-Plus Synonym is MRV042 %NET$CONFIGURE-I-REGSUCCESS, node has been successfully registered in the !NEW_NS directory service Node 0 at 1995-04-06-15:50:29.390-04:00Iinf %NET$CONFIGURE-I-NODERENAMED, node successfully renamed to new_ns:.mrv042 . . . . . . . . . . . . . . . %NET-I-LOADED, executive image NET$LOOP_APPLICATION.EXE loaded %NET$STARTUP-I-OPERSTATUS, DECnet-Plus for OpenVMS operational status is RUNNING- ALL %NET$CONFIGURE-I-CONFIGCOMPLETED, DECnet-Plus for OpenVMS configuration completed

Copyright © Compaq Computer Corporation 1998. All rights reserved. Legal

6497PRO_003.HTML