HP OpenVMS Systems Documentation

The net$configure.com procedure creates an Export/Import file to register your node in the appropriate namespace. If your node is already registered, the decnet_register Export/Import file is not created.

2.6.1 Export/Import File Format

The decnet_register Export/Import file is a text file that has the following format where <synonym> is the node synonym name you selected during configuration:

sys$manager:decnet_register_import_file_<synonym>.TXT

If you encounter problems registering your node in the Local namespace or in the DECdns namespace, you will see information similar to the following:

.
.
.
Updating nodes listed in SYS$MANAGER:DECNET_REGISTER_IMPORT_FILE_ELMER.TXT

 1) local:.elmer

Error - Node registration was unsuccessful
        Please correct any problems and re-register the node
    LOCAL:.elmer

  The specified node name is already in use as a synonym
        Used by node: LOCAL:.WABBIT.ELMER
        Synonym:      elmer

You can choose to stop processing this command, continue executing this
command until completion or until the next error, or ignore further errors
and continue to completion.


Number of nodes registered: 0
Number of nodes modified:   0
Number of update failures: 1

%NET$CONFIGURE-E-COULDNOTREG, could not automatically register node in the LOCAL
 directory service

     **********************************************************************
                                 WARNING

     This node could not be registered in one or more of the directory
     services you have chosen.  When this procedure completes you or your
     network manager will have to manually register this node in the directory
     service(s) for which the error occurred.  See the DECnet-Plus Installation
     and Configuration guide for more details, or contact your network manager.

     Once the problem has been rectified, you or your namespace manager can
     use the following DECNET_REGISTER command(s) to register your node in the
     appropriate directory service(s):

        For the LOCAL directory service:
        DECNET_REGISTER IMPORT DIRECTORY LOCAL FILE -
                SYS$MANAGER:DECNET_REGISTER_IMPORT_FILE_ELMER.TXT

     Once the node has been successfully registered in the appropriate
     directory service(s), invoke option 2 of NET$CONFIGURE.COM (Change
     node name/namespace name) to complete the node's network configuration
     and startup.

     **********************************************************************

If net$configure.com cannot access the DECdns namespace you have selected, it is most likely because:

• The namespace is not available at the moment.
• Your node does not have proper access to the DECdns namespace.
• The namespace you are using is new and the directories have not been created yet.

When this happens, you will see the following message (this example uses ACME: as the namespace that is not accessible):

     *************************************************************************
                                    WARNING
     NET$CONFIGURE.COM cannot access the ACME: namespace, either because
     the namespace is not available at the moment, your node does
     not have proper access to the namespace, or because the namespace
     you are using is new and the directories have not been created yet.
     Therefore, the DECNET_REGISTER tool cannot attempt to look up or register
     your node into the ACME: namespace.

     When the problem is rectified, please use the DECNET_REGISTER import file
     to register your node into the ACME: namespace.

     *************************************************************************

If you receive this message because the namespace you are using is new and the namespace directories have not been created yet, use the decnet_register manage command to invoke decnet_register_decdns.com (located in SYS$MANAGER:) to create the proper directories. For more details, refer to the DECnet-Plus for OpenVMS Network Management guide.

If you see the preceding warning messages, net$configure will display another message indicating how you or your namespace manager can attempt node registration once the problem is resolved. For example:

     **********************************************************************
                                 WARNING

     This node could not be registered in one or more of the directory
     services you have chosen.  When this procedure completes you or your
     network manager will have to manually register this node in the directory
     service(s) for which the error occurred.  See the DECnet-Plus Installation
     and Configuration guide for more details, or contact your network manager.

     Once the problem has been rectified, you or your namespace manager can
     use the following DECNET_REGISTER command(s) to register your node in the
     appropriate directory service(s):

        For the DECdns directory service:
        DECNET_REGISTER IMPORT DIRECTORY DECDNS FILE -
            DECNET_REGISTER_IMPORT_FILE_ELMER.TXT

        For the LOCAL directory service:
        DECNET_REGISTER IMPORT DIRECTORY LOCAL FILE -
            DECNET_REGISTER_IMPORT_FILE_ELMER.TXT

     Once the node has been successfully registered in the appropriate
     directory service(s), invoke option 2 of NET$CONFIGURE.COM (Change
     node name/namespace name) to complete the node's network configuration
     and startup.

     **********************************************************************

You may see the previous messages if the following exist:

• You enter LOCAL for the primary directory service and DECDNS for the secondary directory service and,
• Your primary Local node full name does not have the proper access necessary to look up or register your secondary DECdns node full name.
  If this is the case, you or your network manager need to perform the following steps on the node that has the DECdns server in order for your primary Local node to obtain this access to the DECdns namespace:
  1. Make sure the .WorldRead_Group is created on the DECdns server node. If the .WorldRead_Group has not been created yet, use the decnet_register manage command to invoke decnet_register_decdns.com (located in sys$manager:) to create the .WorldRead_Group. For more details, refer to the DECnet-Plus for OpenVMS Network Management guide.
  2. Once you or your namespace manager knows that the .WorldRead_Group has been created, invoke the dns$control utility on the node with the DECdns server and enter the following commands:

     $ mcr dns$control DNS>add group <ns>:.worldread_group member local:.*... DNS>add clear <ns>:.<ch_name> access <ns>:.worldread_group as group for r,t

     
     where ns is the DECdns namespace name to which you want your LOCAL node to have access and ch_name is the clearinghouse name of the DECdns namespace you are using.

These commands will give your primary Local full name the proper access it needs to look up information regarding the secondary DECdns full name you have chosen.

This chapter describes the steps necessary to modify a current configuration.

3.1 Steps for Changing the Configuration

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 3-1 provides some guidelines for making your configuration choice.

If you prefer to use the BASIC configuration option, refer to the DECnet-Plus for OpenVMS Installation and Basic Configuration guide, Chapter 6. If you want to customize your system's network configuration with the ADVANCED configuration option, continue to Section 3.2.

Changing your DECnet-Plus for OpenVMS configuration with the ADVANCED option involves the following steps:

1. Run net$configure procedure using the ADVANCED configuration option with the following command:

   $ @sys$manager:net$configure advanced

   
   The procedure starts:

   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] :

2. Answer YES if you want to continue. You will now see the date that the checksum file was last modified:

   Checksum file updated last by SYSTEM on 18-SEP-1995 16:04:24.19 %NETCONFIGURE-I-VERCHECKSUM, verifying checksums

   Note If this is the first time you are invoking the net$configure procedure, or if you have deleted the checksum file, the following menu is not displayed. Instead, the prompts shown in Section 6.1 of the DECnet-Plus for OpenVMS Installation and Basic Configuration guide appear for the BASIC option, and the prompts shown in Section 1.1 in this book appear for the ADVANCED option.

   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] :

3. Choose the option you want. Selecting an option allows you to modify either the entire configuration or a particular portion.

   Note To select Options 10 or 11, you must have already configured the system using the ADVANCED configuration option, and net$configure is executing on a cluster system. See Section 3.14 and Section 3.15 for more information.

4. After you have completed the configuration dialog, the system displays the following question:

   * Do you want to generate NCL configuration scripts [YES] :

   
   If you answer YES, the configuration program uses the information you entered to generate modified NCL scripts and, in some cases, automatically modify the system's configuration. The configuration program then returns to the Configuration Options menu. If you answer NO, the configuration procedure returns to the Configuration Options menu and does not generate any modified NCL scripts.

You can use the net$configure procedure to modify the current configuration. Depending upon which menu option you select, net$configure either modifies the configuration automatically or produces modified NCL scripts which you can use to modify the system's configuration.

You can execute modified NCL scripts in two ways:

• Rebooting the system
• Disabling the entity to which the script applies and executing 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

To customize your system beyond what the net$configure procedure provides, you must edit the NCL scripts produced by net$configure.com (refer to the DECnet-Plus for OpenVMS Network Management guide). DIGITAL recommends that you use the net$configure procedure for major modifications involving an entire entity.

3.3 Changing an Entire Configuration

To make changes to the entire configuration, proceed as follows:

* Which configuration option to perform?             [1] :

Select Option 1.

The system displays the same prompts that were displayed for the initial configuration. The prompts show the current configuration values as the default. If you do not want to change the current values, accept the default value. Refer to Section 1.1 for an explanation of the prompts shown for a net$configure ADVANCED configuration. Refer to the DECnet-Plus for OpenVMS Installation and Basic Configuration guide, Chapter 6, for an explanation of the prompts shown for a net$configure BASIC configuration.

At the end of the procedure, you see the following prompt:

* Do you want to generate NCL configuration scripts? [YES] :

If you answer YES, the configuration program uses the information you entered to generate modified NCL scripts. If you answer NO, the configuration procedure does not generate NCL scripts.

If you generate NCL scripts, the procedure displays another prompt:

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

Answer YES to start the network and to complete the network configuration. To implement the NCL scripts, reboot the system.

3.4 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, the namespace that the system uses, or the system's node synonym, proceed as follows:

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

Select Option 2 and press Return.

If you are using either the BASIC or ADVANCED configuration option, you will see the following prompt:

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

Enter the directory name services you want to use. (The first service you enter is considered your primary name service; the default is the name service you entered for the previous configuration.)

Depending on the directory services you choose, you may see one or more of the following prompts:

* Enter the full name for directory service LOCAL:
* Enter the full name for directory service DECDNS:
* Enter the fully qualified host name for DNS/BIND:

To change the node name or the namespace that it uses, enter the node's new full name. The format is:

NamespaceNickname:.DirectoryPath.NodeObject

For DECdns, the namespace nickname is the name that a DECdns manager assigns to a namespace when installing and configuring DECdns server software. If the namespace has a nickname, you must enter the nickname as part of the node's full name. However, not all namespaces have nicknames. Namespaces are required to have nicknames only if there is more than one namespace on the network.

If you use the Local namespace, the namespace nickname is LOCAL:.