HP OpenVMS Systems Documentation

Next you will be prompted for the node synonym:

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

The synonym name is a Phase IV-compatible node name. It can be one to six alphanumeric characters long, must not start with a number, and must be unique within the namespace. It is required for Phase IV nodes using the namespace and DECnet-Plus nodes that need to communicate with Phase IV nodes.

The following display shows the system response to a node name change.

.
.
.
 %NET$CONFIGURE-I-NODERENAMED, node successfully renamed to
 PHASEV:.ENG.SSG.TEST.ELMER1
 Update Node 0 Session Control Tower Maintenance
 PHASEV:.ENG.SSG.TEST.ELMER1
  at 1995-04-13-14:44:14.821-04:00I0.532
.
.
.
 %NET$CONFIGURE-I-TOWERSUPDATED, updated address towers for node

        Summary of Configuration

 Node Information:
        Directory services chosen:       DECDNS,LOCAL,DOMAIN
        Primary directory service:       DECdns
        DECdns full name:       PHASEV:.ENG.SSG.TEST.ELMER1
        Local full name:        LOCAL:.ELMER1
        Fully Qualified
        Host name:              ELMER1.WABBIT.ACME.EDU
        Node Synonym:           ELMER1
        Phase IV Address:       15.27
        Phase IV Prefix:        49::
        Autoconfiguration of Network Addresses: Enabled
        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

 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

The configuration program uses the information you entered to automatically modify the system's configuration. The program then returns you to the Configuration Options menu.

3.4.4 Configuring a DECdns Clerk System to Use a WAN DECdns Server

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 as shown below:

  The namespace you specified was IAF2.

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

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 with the WAN configuration process.

   Attempts to configure DECdns via a LAN connection 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 Phase IV-compatible address (if it has one) or its network service access point (NSAP). The NSAP is the network entity title (NET) with a valid transport selector. To find this information, contact the 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 of the server
 you want to connect to:

After you enter the server's address (for example, 4.456), your system connects to the server.

You then receive a confirmation message listing your namespace nickname and its namespace creation timestamp (NSCTS), as in the following:

Getting server data, please wait...


sys$manager:net$dns_clerk_startup.ncl changed to use the new default namespace.

Your default namespace nickname is XYZ_CORP

Your default namespace NSCTS is 00-12-34-56-77-A0-A1-A2-A3-A4-A5-A6-A7-B0

If you cannot connect to the remote server, the procedure displays the following message:

%DNS-E-NOCONFIG, DECdns clerk is not configured.

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 DECnet-Plus DECdns Management guide for DECdns access control information and for complete information about using the DECdns configuration program to configure a DECdns server into an existing namespace.

3.4.5.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 2.5). For complete information on how to prepare a DNS Version 1 namespace for use by DECnet-Plus, refer to the DECnet-Plus DECdns Management guide for DECdns access control information.

To reconfigure the devices, proceed as follows from the Configuration Options menu:

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

Select Option 3 and press Return.

Before proceeding with this menu option, the procedure determines whether the system has network devices that are supported by net$configure.

%NET$CONFIGURE-I-SCANCONFIG  scanning device configuration - please wait

If no supported network devices are found or new devices are found that were not detected the last time you ran the net$configure procedure on this system, the procedure displays the following prompt for Alpha systems:

* Should a SYSMAN IO AUTO be executed?                       :

For VAX systems, you will see the following prompt:

* Should a SYSGEN AUTOCONFIGURE ALL be executed?       :

If you answer YES, the net$configure procedure invokes the SYSMAN IO AUTO or the SYSGEN AUTOCONFIGURE ALL command to find devices. If you answer NO, then there will be no devices to configure and the procedure exits.

The BASIC configuration automatically configures your devices and asks no further questions concerning device configuration. If you choose the ADVANCED configuration, the procedure prompts you for data link names and routing circuit names to use for each device.

* Data Link name to use for ESA0 (DESVA)            [CSMACD-0] :

Specify the simple name you want to use for the data link device or accept the system-supplied default. If you do not want this device configured for DECnet-Plus, enter NONE.

* Routing Circuit Name for Data Link 'CSMACD-0'     [CSMACD-0] :

Specify the simple name you want to use for the routing circuit or accept the system-supplied default. DIGITAL recommends that you use the default name even if you configure multiple lines of the same type.

* Level 1 Cost for Routing Circuit 'CSMACD-0'?           [8] :
* Level 1 Router Priority for Routing Circuit 'CSMACD-0'? [64] :

If your DECnet-Plus system is a router, then you will be asked for this information for the routing levels supported.

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.

* Enable Phase-IV Addressing on Routing Circuit 'CSMACD-0'? [YES] :

If you previously specified a Phase IV-compatible address in order to communicate with Phase IV nodes (as in Section 1.2.6), entering YES to the question above allows Phase IV messages to be transmitted on the circuit. Answering NO to this question means that no Phase IV messages will be transmitted on the circuit.

To reconfigure the NSP, OSI transports, or both, select Option 4 from the Configuration Options menu and press Return.

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

The BASIC configuration automatically configures the NSP and OSI transports. If you choose the ADVANCED configuration option, the procedure asks if you want to configure the NSP and OSI transports.

For more information on configuring NSP and OSI transports, see also Appendix B.

The following sections describe the prompts that are required to reconfigure the transports.

* Configure the NSP Transport?                         [YES] :
*   Maximum number of logical links ?                  [200] :
*   Maximum Transmit and Receive Window ?               [20] :
*   Maximum Receive Buffers  ?                        [4000] :
* Configure the OSI Transport?                         [YES] :
*   Maximum number of logical links ?                  [200] :
*   Maximum Transmit and Receive Window ?               [20] :
*   Maximum Receive Buffers  ?                        [4000] :
*   Run OSI Applications over TCP/IP ?                 [YES] :
*   Run DECnet over TCP/IP ?                           [YES] :
* Is this system operating in a multi-protocol network? [YES] :
* Do you want to replace the existing NSP transport script? [NO] :
* Are the point-to-point lines utilizing line speeds less than 9600 BPS? [NO]
* Do you want to replace the existing OSI transport script? [NO] :

* Configure the NSP Transport?                         [YES] :

If you want to communicate with any DECnet Phase IV nodes, answer YES.

To determine the maximum number of active NSP transport connections allowed at any one time to this transport, the procedure displays the following prompt:

* Maximum number of logical links?                     [200] :

You are then prompted to set the following values:

* Maximum transmit and receive window?                  [20] :

* Maximum receive buffers?                            [4000] :

DIGITAL recommends setting a value of 20 for the maximum transmit and receive window option. The recommended value to set the maximum receive buffers is no more than maximum window multiplied by maximum transport connection for normal network operation in a typical network environment.

Selecting other values than these 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.

High values of maximum receive buffers may require considerable buffering capacity on your node; therefore, a non-paged pool should be allocated accordingly. If your node does not have enough non-paged pool, maximum receive buffers should be set to a smaller value than maximum window multiplied by maximum transport connections.

The transport receiver's window is determined by a combination of maximum transport connections, maximum receive buffers, and maximum window. During the life of the connection, the receiver quota fluctuates according to the value of maximum receive buffers divided by currently active connections. The credit window sent to the remote transmitter may or may not be this quota value, depending on the value of maximum window. If maximum window is set to less than the determined receiver quota, this value is used instead for the credit granted to the remote transmitter.

The transmitter of a transport connection uses the credit sent by the remote receiver as its transmit window, unless its maximum window is a lower value. In that case, maximum window is used for the transmitter window.

* Configure the OSI Transport?                         [YES] :

If you want the system to communicate with DECnet-Plus nodes or if you plan to install the OSAK, FTAM, or VT software, answer YES. If you want to use the DECnet over TCP/IP and/or OSI applications over TCP/IP, answer YES.

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 OSI transport question.

To determine the maximum number of active OSI transport connections allowed at any one time to this transport, the procedure displays the following prompt:

* Maximum number of logical links?                     [200] :

You are then prompted to set the following values:

* Maximum transmit and receive window?                 [20] :

* Maximum receive buffers?                           [4000] :

DIGITAL recommends setting a value of 20 for the maximum transmit and receive window option. The recommended value to set the maximum receive buffers is no more than maximum window multiplied by maximum transport connections for normal network operation in a typical network environment.

Selecting other values than these 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.

High values of maximum receive buffers may require considerable buffering capacity on your node; therefore, a non-paged pool should be allocated accordingly. If your node does not have enough non-paged pool, maximum receive buffers should be set to a smaller value than maximum window multiplied by maximum transport connections.

The transport receiver's window is determined by a combination of maximum transport connections, maximum receive buffers, and maximum window. During the life of the connection, the receiver quota fluctuates according to the value of maximum receive buffers divided by currently active connections. The credit window sent to the remote transmitter may or may not be this quota value, depending on the value of maximum window. If maximum window is set to less than the determined receiver quota, this value is used instead for the credit granted to the remote transmitter.

The transmitter of a transport connection uses the credit sent by the remote receiver as its transmit window, unless its maximum window is a lower value. In that case, maximum window is used for the transmitter window.

You are then prompted:

* Run OSI Applications over TCP/IP?                    [YES] :

Answer YES to this question if you want to run any of your OSI applications over TCP/IP. This causes the configuration utility to build the appropriate RFC 1006 template and establish a listener port for port 102.

* Run DECnet over TCP/IP?                              [YES] :

Answering YES to this question enables DECnet-Plus to run over a TCP/IP network to any system that has enabled this same feature. The configuration utility builds appropriate RFC 1859 template and establishes a listener port for port 399.

You are then prompted about multi-protocol networks:

* Is this system operating in a multi-protocol network?  [YES] :

If you take the default answer of YES, then the OSI transport and NSP Congestion Avoidance characteristic are set to FALSE. Note that currently NSP does not support the Congestion Avoidance attribute.

A NO answer to this question sets the characteristic to TRUE.

If an NCL script already exists for an NSP transport and you answer YES to the "Configure the NSP Transport?" prompt, the procedure displays the following prompt:

* Do you want to replace the existing NSP transport script? [NO] :

If you reconfigure the NSP transport, you have the option of accepting the existing transport script or replacing it with a new one. Answer YES if you want to replace the existing NSP transport script.

* Are the point-to-point lines utilizing line speeds less than 9600 BPS? [NO]

You will be prompted only if you have any point-to-point lines (i.e., any synchronous and/or asynchronous lines) configured. If you have any point-to-point lines running at low line speeds (lower than 9600 bits/s), answer YES. This places additional NSP NCL commands into the NSP transport NCL script to accommodate the lower line speeds. If you do not have any point-to-point lines being utilized at low line speeds, answer NO.

* Do you want to replace the existing OSI transport script? [NO] :

Answer YES if you want to replace the existing OSI transport script.

If you answer YES to the "Configure OSI Transport?" prompt and you want to replace the existing OSI transport NCL script, the procedure displays the following prompt (ADVANCED configuration option only):

* Username for OSI loopback test application to use? [SYSTEST] :

Press Return to accept the default user name for the application loopback test account.

The procedure displays:

%NET$CONFIGURE-I-CREDEFOSITEMPLATE, created default OSI templates

If you use the ADVANCED configuration option, you will see the following prompts:

* Do you want to create additional OSI templates?       [NO] :

This prompt allows you to create additional customized OSI templates. If you answer YES, the template questions are repeated.

If you answer NO, the procedure displays:

                   Summary of Configuration


 Node Information:
      Directory services chosen:      DECDNS,LOCAL,DOMAIN
      Primary directory service:      DECDNS
      DECdns Full Name:       ACME:.WABBIT.ELMER
      Local Full name:        LOCAL:.ELMER
      Fully Qualified
      Host name:              ELMER.WABBIT.ACME.EDU
      Node Synonym:           ELMER
        .       .
        .       .


 Device Information:
     Device: ESA0 (DESVA):
               Data Link name:       csmacd-0
               Routing Circuit Name: csmacd-0


 Transport Information:
        NSP Transport:                          Configured
          Maximum number of logical links:         200
          Maximum Transmit and Receive Window:     20
          Maximum Receive Buffers:                 4000

        OSI Transport:                          Configured
          Maximum number of logical links:         200
          Maximum Transmit and Receive Window:     20
          Maximum Receive Buffers:                 4000

        Congestion Avoidance Disabled
               .               .
               .               .
* Do you want to generate NCL configuration scripts?   [YES] :

If you answer YES, the configuration program uses the information you have entered to create the Transport NCL scripts. The configuration program then returns to the Configuration Options menu. To implement the modified NCL scripts, reboot the system or disable the transport entities and execute the scripts.

If you answer NO, the configuration procedure returns to the Configuration Options menu and does not generate NCL scripts.