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.
Note
If you use DECDNS for the primary directory service and LOCAL for the secondary directory service, these steps are not necessary.
This chapter describes the steps necessary to modify a current 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.
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 a cluster. | |
You are running the configuration procedure for the first time. | |
BASIC | The node is in a cluster. |
You are upgrading or reconfiguring DECnet-Plus. | |
You need to access a DECdns server for network addresses. | |
You want to run DECnet over TCP/IP (RFC 1859) and/or OSI applications over TCP/IP (RFC 1006). | |
You only have 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 both DECnet over TCP/IP or OSI applications over TCP/IP. | |
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 (this attribute controls 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. | |
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 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. |
Changing your DECnet-Plus for OpenVMS configuration with the ADVANCED option involves the following steps:
$ @sys$manager:net$configure advanced
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] :
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] :
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.
* Do you want to generate NCL configuration scripts [YES] :
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:
To execute the NCL script, use the format ncl> do script-file. For example:
ncl> do sys$manager:net$nsp_transport_startup.ncl
Note
The net$configure procedure does not automatically execute the modified NCL scripts for you. However, it will execute the search path NCL script (NET$SEARCHPATH_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.
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.
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:.
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.
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
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.
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.
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.
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, Digital 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.
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.
Note
Phase-IV addressing can be enabled on only one routing circuit. If you are using large packet support with FDDI, you must ensure that Phase-IV addressing is enabled on an FDDI routing 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.
PROFILE_004.HTML OSSG Documentation 2-DEC-1996 12:33:27.28
Copyright © Digital Equipment Corporation 1996. All Rights Reserved.