![[Digital logo]](../../IMAGES/DIGITAL-LOGO.GIF){kind=logo}
![[HR]](../../IMAGES/REDBAR.GIF)
The BASIC configuration option allows you to configure your system by answering a few questions and using the default answers on others.
If you have already configured the DECnet-Plus for OpenVMS software and you want to customize the configuration, see Chapter 4 to determine if you want to use the BASIC or ADVANCED option.
To invoke the net$configure.com procedure using the BASIC configuration option, enter the following command:
$ @sys$manager:net$configure basic
The procedure starts:
Copyright (c) Digital Equipment Corporation 1993, 1996. All rights reserved.
DECnet-Plus for OpenVMS BASIC 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 BASIC configuration option. This option enables
you to quickly configure your system by answering a few questions and
using most of the default answers. If you would rather do some specific
tailoring of your system's network configuration, you should invoke
NET$CONFIGURE.COM with the ADVANCED configuration option, ie:
@SYS$MANAGER:NET$CONFIGURE ADVANCED
* Do you want to continue? [YES] :
Press Return to continue with the BASIC configuration option.
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 procedure displays the following message:
%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 database? [YES] :
If you answer YES, 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, starting with the directory services to use on the system. If you need more information to answer a question, you can type a question mark (?) at the prompts. Review the installation planning checklist in Chapter 2 before continuing.
DECnet-Plus provides access to the node name and addressing information stored in one or more name services. This release of DECnet-Plus supports the following directory name services:
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] :
The DECnet-Plus for OpenVMS configuration procedure net$configure.com prompts you for the system's full name. You can enter a DECdns full name, a Local namespace full name, a fully qualified host name for the Domain Name System (DNS/BIND), or all three. For DECdns and Local namespace full names, you must specify a node full name that includes a namespace nickname (this complies with DECdns distributed namespace requirements). The full name format is the same for distributed namespaces and Local namespaces.
The full name uses the following form:
NamespaceNickname:.DirectoryPath.NodeObject
The following are the guidelines for selecting a full name:
The following are some examples of suitable node full names:
AU:.chemistry$lab.Sunil$Sethi XYZ_CORP:.sales.east_coast.BrianMacKrill Mbi:.MIS.Europe.Monaco_headquarters.F_Riviera local:.bryan smilee.mass.acme.edu
Note
If you plan to use a Local namespace and you are converting a Phase IV system to DECnet-Plus, Digital recommends that you use the system's Phase IV node name in the DECnet-Plus full name (for example, LOCAL:.PASTRY).
You should plan node full names carefully and make sure they are unique within the namespace. If your network administrator has not assigned a unique node full name for your system, be sure to read the DECnet-Plus Planning Guide before you assign a node name for your system. For more information on name services, see Chapter 7.
At the prompt, 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
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] :
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.
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.
The node synonym is primarily a transition tool that allows you to use a Phase IV-style node name for your DECnet-Plus node. Other users can then find your node by using this synonym rather than your full name. If you were using DECnet Phase IV, consider using your Phase IV node name as your synonym. The synonym is required for Phase IV applications that can only handle Phase IV-style node names. If your network has only DECnet-Plus or OSI (Open Systems Interconnection) systems, you may not need a node synonym.
The default node synonym is the first six characters of the system's last simple name. The last simple name is the string that follows the last period of your full name. For example, if you specify XYZ_CORP:.sales.east_coast.BrianMacKrill as a node full name, the default node synonym is BrianM.
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 7.4.
If you want your system to communicate with Phase IV nodes, you must specify a Phase IV address and a Phase IV prefix. These will be used to construct a DECnet Phase IV-compatible address.
A DECnet Phase IV-compatible address is a DECnet-Plus address (NSAP - network service access point) that conforms to the Phase IV area and node limits; that is, the area number is from 1 to 63, and the node number is from 1 to 1023.
If there are no Phase IV systems on your network or you do not want to communicate with Phase IV systems, you do not need a Phase IV-compatible address. Entering a Phase IV address of 0.0 at configuration time indicates that this DECnet-Plus system will not have a Phase IV-compatible address, and will not communicate with Phase IV nodes.
* Enter PhaseIV Address [15.27] :
Enter the Phase IV address you want to use, or enter 0.0 if you do not want to communicate with Phase IV nodes.
The net$configure basic configuration option provides 49:: as the default value for the Phase IV prefix. If you do not enter a Phase IV-compatible address, you will not have a Phase IV prefix.
The net$configure basic configuration option autoconfigures one network address for you.
The net$configure basic configuration sets the routing characteristic DNA address format to TRUE.
The net$configure procedure checks for network devices on the system that are supported by net$configure and then configures them. If the procedure finds that you have WANDD or X.25 installed but not configured, you will see the following information:
You have installed wide area device support, but it has not been configured. You may configure it now if you want. * Do you want to configure Wide Area devices? [YES] : N %NET$CONFIGURE-I-SCANCONFIG, scanning device configuration - please wait
For an Alpha system, the procedure displays the following information:
DEC X.25 software has been installed on this system. You have the option of configuring DECnet to run over X.25. * Do you want to configure DECnet over X.25? [NO] :
Answer YES if you want to configure DECnet over X.25.
If you answer YES, you will see a list of choices for the type of X.25 circuit to use:
Types of X.25 circuits:
[1] - X.25 Dynamic Assigned (DA)
[2] - X.25 Static Incoming (IN)
[3] - X.25 Static Outgoing (OUT)
[4] - X.25 Permanent (PVC)
* Which type of X.25 circuit do you want to use? : 4
* Routing Circuit Name to use? [X25-PVC-0] :
* Template name? [X25-PVC-0] :
* Configure another X.25 routing circuit for DECnet? [NO] :
Enter the number for the type of circuit you want, then enter a routing circuit name and a template name to use for that circuit. If you do not want to configure any other X.25 routing circuits, press Return for the default. The configuration procedure continues with the next series of questions (such as time zone or transports, for example).
If no devices are found on the Alpha system, the procedure displays the following prompt:
* Should a SYSMAN IO AUTO be executed? :
If you answer YES, the net$configure procedure invokes the SYSMAN IO AUTO command to find devices on the system. If you answer NO, there are no devices to configure.
If you answer YES to the question, "Do you want to configure Wide Area devices?" and you are using a VAX system, the procedure displays the following information:
* Do you want to configure Wide Area devices? [YES] :
Answer YES if you want to configure DECnet over P.S.I.
If you anwer YES, the procedure displays the following:
This is the Configuration Procedure for the
===========================================
VAX Wan Device Drivers for DECnet/OSI for VMS
=============================================
The Wide Area Network Datalinks and Drivers are a prerequisite
for DECnet/OSI. They also provide synchronous datalinks in
systems that do not use DECnet/OSI for networking.
Access to DECnet/OSI datalinks (created by NCL) is possible via
the QIO interface to the WAN pseudo-driver, WANDRIVER. Layered
products that use synchronous devices do not normally require
programming access to WANDRIVER. For further information, see
the "DECnet/OSI for VMS WANDD Programming" guide.
Do you wish to use WANDRIVER [N] ? y
Will you use DEC HDLC [Y] ?
Will you use LAPB/E (VAX P.S.I. requires LAPB/E) [Y] ?
The DSV11 (Q-bus), DIV32 (Q-bus), DSB32 (BI-bus), DSF32 (MI-bus) and
DSW devices are soft-loadable. The WANDD startup procedure will load
the microcode for these devices if required.
Do you have any soft-loadable microcode devices on this system [N] ?
Will you use the VAXft DSF32 device driver [N] ? y
The VAXft DSF32 software supports the pairing of physical
controllers to provide a fault-tolerant configuration. Such a
pairing is called a Failover Set. The DSF32 device does not
automatically create the failover sets, so you will need to pair
controllers using the Failover Set Manager software.
This management software can be invoked during system startup
from within the command procedure WANDD$STARTUP_SF.COM, which is
placed in the SYS$STARTUP directory by the kit installation
procedure. If you want to have these Failover Sets automatically
configured when the system starts up you will need to modify
WANDD$STARTUP_SF.COM to include Failover Set Manager commands
that you require.
Are you satisfied with the answers you have given [Y] ?
If you have already started up the WAN Drivers and Datalinks
(that is, if you have already successfully run
SYS$STARTUP:WANDD$STARTUP.COM since your system was last
booted), then you will need to reboot your system for your new
configuration to take effect.
%NET$CONFIGURE-I-SCANCONFIG, scanning device configuration - please wait
* Do you want to configure DECnet over X.25? [NO] : yes
Types of X.25 circuits:
[1] - X.25 Dynamic Assigned (DA)
[2] - X.25 Static Incoming (IN)
[3] - X.25 Static Outgoing (OUT)
[4] - X.25 Permanent (PVC)
* Which type of X.25 circuit do you want to use? : 1
* Routing Circuit Name to use? [X25-DA-0] :
* Template name? [X25-DA-0] :
* Filter name? [X25-DA-0] :
* Do you want to configure any reachable addresses? [NO] :
* Configure another X.25 routing circuit for DECnet? [NO] :
The procedure continues to ask for information. See Section 6.3.1 for the types of questions you will see and possible responses you can enter.
If no devices are found on the VAX system, the procedure displays the following prompt:
* Should a SYSGEN AUTOCONFIGURE ALL be executed? :
If you answer YES, the net$configure procedure invokes the SYSGEN AUTOCONFIGURE ALL command to find devices on the system. If you answer NO, there are no devices to configure.
Next, the NSP transport and the OSI transport are configured.
The procedure displays the following message to indicate that the default OSI templates have been created:
%NET$CONFIGURE-I-CREDEFOSITEMPLATE, created default OSI templates
The default OSI templates are used by the OSAK and FTAM installation verification procedures (IVPs) for loopback testing. You will not be able to use OSI applications to make connections to other OSI systems unless you use the net$configure advanced configuration option to create additional OSI templates. You can do this at a later time.
The UTC (Coordinated Universal Time) is calculated automatically by using the OpenVMS UTC, and 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.
The procedure then provides the default Event Dispatcher configuration:
%NET$CONFIGURE-I-EVDDEFAULT, providing default Event Dispatcher configuration
The procedure creates the DECnet-Plus default applications to include in the application database. The procedure creates default user accounts for the CML, MAIL, VPM, MIRROR, and PHONE applications (no account is created for FAL):
%NET$CONFIGURE-I-MAKEACCOUNT, this procedure creates user account CML$SERVER %NET$CONFIGURE-I-MAKEACCOUNT, this procedure creates user account MAIL$SERVER %NET$CONFIGURE-I-MAKEACCOUNT, this procedure creates user account VPM$SERVER %NET$CONFIGURE-I-MAKEACCOUNT, this procedure creates user account MIRRO$SERVER %NET$CONFIGURE-I-MAKEACCOUNT, this procedure creates user account PHONE$SERVER
The following steps describe how to configure a cluster alias.
* Full name of Cluster Alias : ACME:.WABBIT.HELP
* Cluster Alias Phase IV Address (aa.nnnn OR AA-00-04-00-xx-xx) : 12.139
(area-number * 1024) + node-number = decimal equivalent (For example, (12 * 1024) + 139 = 12427 decimal)
(12427 decimal = 308B hex, reversed = 8B30 hexnodeaddress)
AA-00-04-00-hexnodeaddress (For example, AA-00-04-00-8B-30)
* Selection weight for this cluster node [0 for satellites] :
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
Phase IV Address: 15.27
Phase IV Prefix: 49::
Autoconfiguration of Network Addresses: Enabled
Alias Name: ACME:.WABBIT.HELP
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
* Do you want to generate NCL configuration scripts? [YES] :
%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.
* Do you want to start the network? [YES] :
******************************************************************** 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
Copyright (c) Digital Equipment Corporation 1995. 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 namespace. 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 1995-05-26-14:12:24.170-04:00I0.404 %NET$CONFIGURE-I-NODERENAMED, node successfully renamed to ACME:.WABBIT.ELMER Directory Service: DECdns
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 1995-05-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 1995-05-26-14:13:35.360-04:00I0.411
%NET$CONFIGURE-I-TOWERSUPDATED, updated address towers for node
Node 0 Session Control Backtranslation Softlink *
at 1995-05-26-14:13:43.360-04:00I0.412
Node 0 Session Control Backtranslation Softlink *
at 1995-05-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
$
PROFILE_002.HTML OSSG Documentation 2-DEC-1996 13:01:39.36
Copyright © Digital Equipment Corporation 1996. All Rights Reserved.