NET$CONFIGURE.COM V3.0 - for DECnet-Plus for OpenVMS
© Copyright 2003 Hewlett-Packard Development Company, L.P.
1 – DMU help
"Do you want to convert Phase IV databases?"
If you answer YES to this question, the NET$CONFIGURE procedure
uses the system's existing Phase IV database to generate NCL
scripts and configure the system. Depending on the content of the
database, NET$CONFIGURE will ask additional questions on some or
all of the following topics:
o Node's full name and synonym.
o Node's time zone.
o OSI Transport.
o Any standard applications that are not in the existing
database such as OpenVMS MAIL.
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
your node full name.
2 – Convert Node Names help
"Do you want to convert the Phase IV node name database?"
If you answer YES to this question, the NET$CONFIGURE procedure
uses the system's existing Phase IV node name database to generate
a local name database. This file is used to translate node names
if you include "LOCAL" in the list of directory services to be used
on this system.
This will provide a flat naming space that is populated with the node
names from the existing Phase IV permanent database. This is
unnecessary if you do not intend to include "LOCAL" in the list of
directory services to be used on this system.
3 – Node name help
"What is the full name of this node?"
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:.TomThumb
vbo:.afsg.comms.werner
XYZ_CORP:.sales.west_coast.WillyLoman
Europe:.Erin.County_Cork.Bantry.Glengarriff_Road.MACotter
The namespace nickname is terminated with a colon (:). If no
namespace nickname is given or if the namespace nickname "LOCAL"
is used, then the Local File 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. Please note
that the namespace nickname "LOCAL" is reserved, and indicates
that the Local File will be used on this system.
Enter the node full name you want to use. DECnet-Plus node full names
should be planned carefully and must be unique within the directory
service. If your network administrator has not assigned a unique
node full name for your system, be sure that you read DECnet-Plus for
OpenVMS Introduction, Planning, and Glossary before you do so.
This manual also contains guidelines for using the directory
services DECdns and the Local File.
4 – Node synonym help
"What is synonym name for this node?"
The node synonym is an alphanumeric character string between
1 and 6 characters long that contains at least one alphabetic
character. If this system had previously been running DECnet
Phase IV software, then the old node name should be used as the
synonym. If this system is joining a DECnet network for the first
time, any name can be used for the synonym, as long as it meets
the criteria listed above, and is unique within the network.
Enter the node synonym you want to use.
5 – PhaseIV address help
"Enter PhaseIV Address"
A DECnet-Plus system may or may not use a DECnet Phase IV style
node address. A node address of 0.0 indicates that this system
will be communicating with DECnet-Plus nodes only. If your network
contains some systems running DECnet Phase IV, you may want to
specify a compatible address in order to communicate with them.
If your network consists solely of DECnet-Plus and/or OSI systems,
this may not be required.
The DECnet Phase IV node address consists of an area number
(between 1 and 63), and a node number within the area (between
1 and 1023).
Enter the PhaseIV address you want to use, or enter 0.0 if you
want to communicate with DECnet-Plus nodes only.
6 – Phaseiv address prefix help
"Enter Phase IV prefix"
Having chosen a Phase IV compatible address for this system,
you may also specify a Phase IV Prefix, which together with the
node address forms the complete network address for this system.
All nodes within a single addressing domain contain the same IDP
in their network addresses. The default value of "49::" is the
"private network" IDP, which is appropriate for a Phase IV DECnet
network that contains some DECnet-Plus systems. Please contact
your network manager if you are in doubt as to your network's
Phase IV Prefix value, or indeed if you are unsure how to answer
this question at all.
DECnet-Plus systems reference all network addresses (including
Phase IV addresses) using OSI NSAP address formats. The Phase IV
prefix and the Phase IV node address are used to construct the
complete NSAP address. All DECnet-Plus systems within a single
routing domain use this Phase IV prefix to form the Phase IV-
compatible NSAP address. This prefix consists of the OSI address
initial domain part (IDP) and possibly the preDSP portion of
the domain specific part (DSP). DECnet-Plus for VMS Introduction,
Planning, and Glossary contains more information about NSAPs.
The default value for the prefix is the number 49::, which
specifies that your system will be part of a private local
network. This value is generally appropriate for networks that
will not be interconnected with other OSI networks. If your
network is going to be connected with other OSI networks, you
must enter a globally unique IDP.
NOTE
If you are using an IDP other than 49::, it must be assigned
by an authorized standards organization, such as ANSI, or
you must construct an IDP that you know will be globally
unique (based on your telephone number, for instance).
DECnet-Plus for VMS Introduction, Planning, and Glossary
contains a detailed description of how to construct an IDP
and how to apply to a standards organization for an IDP.
If you are in doubt about which prefix value to use, contact your
network manager.
Enter the Phase IV prefix you want to use.
7 – cdi_dirsvc_help
"Enter the directory services to use on the system"
You have the option of choosing the following directory services for
your system:
Local File (LOCAL) - A local namespace that uses flat naming.
DECdns - A distributed namespace.
Domain - A naming service that uses DNS/BIND.
The Local file has the capability to hold 100,000 nodes, and it can even
scale beyond that number. The actual number of nodes that the Local file
can hold depends on the space available on your system.
If you choose to enter more than one directory service for your
system, the ordering of this list is *very important*, as the first
directory service entered in this list will be 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 them by commas.
For example, if you enter "DECdns,Local,Domain" at the prompt, this
means that you want to use the directory services DECdns, Local, and
Domain, and that the primary directory service will be DECdns.
If you are configuring a DECdns server for the first time, your primary
naming service must be DECdns.
8 – cdi_fullname_help
"Enter the full name for directory service {DECDNS,LOCAL}"
"Enter the fully qualified host name"
Enter a node name for each directory service chosen.
For the directory service Domain, you will enter a fully qualified
host name. The fully qualified host name includes the host name and
the domain name. For example:
Domain - smilee.lkg.dec.com
For the directory services DECdns and Local file, you will enter a node
full name. 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 for the directory services DECdns and Local file include:
Local file - LOCAL:.TomThumb
DECdns - XYZ_CORP:.sales.west_coast.WillyLoman
For the Local file, the namespace nickname LOCAL is prepended to the
full name and is terminated with a colon (:). The namespace nickname
"LOCAL" means that the Local file 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. Please note that
the namespace nickname "LOCAL" is reserved, and indicates that the
Local file will be used on this system.
The Local file has the capability to hold 100,000 nodes, and it can even
scale beyond that number. The actual number of nodes that the Local file
can hold depends on the space available on your system.
Enter the node full name you want to use. DECnet-Plus node full names
should be planned carefully and must be unique within the directory
service. If your network administrator has not assigned a unique
node full name for your system, be sure that you read DECnet-Plus
for OpenVMS Introduction, Planning, and Glossary before you do so.
This manual also contains guidelines for using the directory services
DECdns and the Local File.
9 – Node synonym directory help
"Node Synonym Directory"
If you have a large network and would like to use an alternate
node synonym directory rather than using the default node synonym
directory of ".DNA_NodeSynonym", you may enter one at this
prompt. The value for the alternate node synonym directory must
be a DECdns directory full name(for example: .USA_Synonyms).
If you have the logical DECNET_MIGRATE_DIR_SYNONYM defined, the
default value for the node synonym directory will be the value
you defined. If you do not have the logical DECNET_MIGRATE_DIR_
SYNONYM defined, the default value is ".DNA_NodeSynonym".
10 – naming_cache_timeout_value_help
"Naming cache timeout value?"
A CDI naming cache is used to improve the performance of nodename
address resolution. This cache supersedes the DECdns cache and is
used when looking for addresses in the Domain and Local services, in
addition to DECdns. Note that other applications that use DECdns
directly continue to utilize the DECdns cache.
The CDI naming cache includes a mechanism to "timeout" old entries.
In this way, these entries are periodically refreshed to accurately
reflect the actual network environment.
For example, say that node FOO has address 1234. After DECnet-Plus has
looked up node FOO, it will store this address in its cache. If node FOO
were to change it address to 2345, the following events would occur:
- DECnet-Plus would retrieve address 1234 from the cache.
- a connection attempt would be made to address 1234.
- if the connection failed, DECnet-Plus would automatically look up
the address again, bypassing the naming cache. This new lookup
would find address 2345, update the cache, and connect
successfully.
However, if address 1234 had been reassigned to another node BAR, the
following would occur:
- DECnet-Plus would retrieve address 1234 from the cache.
- a connection attempt would be made to address 1234.
- the connection would succeed - DECnet-Plus cannot tell that
it has connected to the wrong node.
To prevent this scenario, network administrators should not reassign node
addresses until the naming cache timeout period has passed. This will
allow these addresses to be automatically flushed from the caches.
You have the option to set a value for the naming cache timeout interval.
Enter any legal OpenVMS delta time value (the default is 30 days).
11 – naming_cache_checkpoint_interval_help
"Naming cache checkpoint interval?"
A CDI naming cache is used to improve the performance of nodename
address resolution. This cache supersedes the DECdns cache and is
used when looking for addresses in the Domain and Local services, in
addition to DECdns. Note that other applications that use DECdns
directly continue to utilize the DECdns cache.
Periodically, DECnet-Plus saves a snapshot of the in-memory naming cache
to disk. This allows systems, during startup, to have a naming cache
that is already populated with entries. In other words, the contents
of the naming cache are preserved across system reboots.
The frequency of this checkpoint operation can be changed. For example,
$ MCR NCL Set Session Control Naming Cache Checkpoint Interval 12:00:00
changes this interval to every 12 hours.
You have the option of setting the naming cache checkpoint interval.
Enter any legal OpenVMS delta time value (the default is 8 hours).
12 – Autoconfigure network addresses help
"Autoconfigure network address?"
Your system must have at least one unique network address in
order to use DECnet-Plus communications features. DECnet-Plus
systems can be multihomed, that is, they can have more than one
network address, but no more than three.
If you answer YES to this prompt, the procedure supplies one
network address for you.
This method is the easiest way to configure a network address,
or Network Entity Title (NET), for your system. If you have a
WANrouter adjacent to your system (on the same LAN or connected
to your system by a point-to-point link), the router will
configure your network addresses for you.
NOTE
Do not choose autoconfiguration unless you know that the OSI
router adjacent to your system uses NETs with a selector of 00.
This restriction applies even if you have a WANrouter on the
LAN. OSI routers that specify NETs differently can cause you
to autoconfigure your network addresses incorrectly. If you
have such a router, you must choose to manually configure your
NETs by answering NO to the autoconfiguration question.
If you answer NO to the autoconfiguration question, you can
manually enter multiple addresses for your system. Your network
manager can supply them to you or you can construct them
yourself. Having multiple addresses allows your system to have
both an OSI address and a Phase IV-compatible address, so you can
communicate with both Phase IV and DECnet-Plus systems on the same
network. It also allows your system to belong to more than one
OSI network. This feature is particularly useful when you want to
combine two (or more) networks. Rather than have all the systems
in both networks get new addresses that reflect the new combined
network, those systems that need to participate in both networks
can have an address in each one.
If you choose not to autoconfigure your network addresses (also
known as Network Entity Titles [NETs]), the procedure displays
the following prompt:
* Enter Manual Network Entity Titles?
13 – Manual net help
"Enter Manual Network Entity Titles?"
You can assign a maximum of three network addresses to a system
including the Phase IV address (if you assigned one). If you
entered a Phase IV address and a Phase IV prefix in response to
the previous prompts, the Phase IV NET is automatically generated
and assigned for you.
If you know which NETs to use, enter them at this prompt. If
you are entering more than one NET, separate them with a comma.
You can obtain them from your network manager or construct them
yourself.
To create an NET manually, you need to know your system's Network
IDP, network local area, and Node ID.
For example, given the following information:
A network IDP of 41:45436192:
A network local area of 43
A node ID of 258
The NET is constructed as follows:
IDP and selector = 41:45436192:local-area:node-id:00
43 decimal = 2B hexadecimal (local area)
(43 * 1024) + 258 = 44290 decimal
44290 decimal = AD02 hexadecimal
AD02 swapped = 02AD hexadecimal (node ID)
The resulting NET is 41:45436192:00-2B:AA-00-04-00-02-AD:00
NOTE
NETs must be entered in DNA format, which uses colons to
separate fields and dashes to separate pairs of digits.
Make sure that you include the 00 selector when you manually
specify a NET.
14 – dna_address_format_help
"DNA Address Format?"
You have the option of setting the value of the Routing characteristic
"DNA Address Format" to either TRUE or FALSE. Answering YES indicates
that NSAP addresses are DNA structured. Enter TRUE if you want to set
the DNA Address Format to TRUE.
15 – Async support help
"Do you want Asynchronous datalink support?"
If you have installed and configured the VAX WAN Device Drivers
software on this system, you have the option of configuring it to
support asynchronous connections.
Support for asynchronous connections is provided by the VAX WAN
device driver software. This software gives you the option of
connecting your OpenVMS system to another system by means of a
low-cost, low-speed asynchronous line. Asynchronous connections
are implemented in software and can be run over any directly
connected terminal line that the OpenVMS system supports. The
asynchronous protocol provides for a full-duplex connection
and can be used for remote asynchronous communications over a
telephone line using a modem.
NOTE
Asynchronous connections are not supported for maintenance
operations or for controller loopback testing.
Normally, the OpenVMS operating system controls lines connected
to terminal ports, as in interactive login. You can, however,
switch the line so that the DECnet-Plus for OpenVMS software can
use the line for an asynchronous connection to another system.
Refer to the DECnet-Plus Network Management manual for information
on the OpenVMS DCL SET TERMINAL commands used to switch terminal
lines to DECnet lines.
You can establish two types of asynchronous DECnet connections:
o A static asynchronous connection, which creates a permanent
DECnet link to a single remote node. Two nodes are connected
by either a dialup line or by a physical line attached to
a terminal port at each end. Before the DECnet connection
is made, the terminal lines must be converted to static
asynchronous DDCMP lines.
o A dynamic asynchronous connection, which provides a temporary
DECnet link. This type of line is usually switched on for
network use only for the duration of a dialup connection
between two nodes. When the telephone is disconnected, the
line reverts to being a terminal line. The advantage of
this type of connection is that you can use a single line
to establish dynamic connections to different remote nodes at
different times.
Also, when creating a dynamic asynchronous connection, you are
given the option of creating an explicit dynamic connection
or a floating dynamic connection. The difference is that an
explicit line is tied to a specific terminal device while a
floating line is not. When using a dynamic connection, you
can have the terminal line switched automatically to a DECnet
line, or you can switch the line manually.
If you answer YES, the procedure asks the following question:
* Do you want to configure static lines? [YES] :
16 – Async static help
"Do you want to configure static lines?"
If you want to establish a static asynchronous connection, answer
YES. A static asynchronous connection creates a permanent DECnet
link to a single remote node. Two nodes are connected by either
a dialup line or by a physical line attached to a terminal port
at each end. Before the DECnet connection is made, the terminal
lines must be converted to static asynchronous DDCMP lines.
17 – Async static lines help
"Terminal device name(s) (ex:TXA0,TXA2...)?"
Specify the device name of the terminal port to be used for the
permanent DECnet link.
18 – Async dynamic help
"Do you want to configure dynamic lines?"
If you want to establish a dynamic asynchronous connection,
answer YES. A dynamic asynchronous connection provides a
temporary DECnet link. A dynamic asynchronous line is normally
switched on for network use only for the duration of a dialup
connection between two nodes. When the telephone is hung up,
the line reverts to being a terminal line. The advantage of this
type of connection is that you can use a single line to establish
dynamic connections to different remote nodes at different times.
19 – Async support more lines help
"Do you want to configure any more Asynch lines?"
If you want to establish lines for more asynchronous connections,
answer YES. If you answer YES, the procedure repeats the
questions regarding configuring static and dynamic lines.
20 – Async static lines yn help
"Do you want to continue configuring this line?"
This prompt is displayed if you failed to specify an appropriate
terminal device name at the previous prompt. If you want to
terminate the configuration of a static asynchronous line, answer
NO.
21 – Async dynamic setup help
"Do you want to configure explicit dynamic lines?"
If you want to configure a terminal port for use as a switched
DECnet link so that explicit Dynamic connections can be made,
answer YES.
22 – Async dynamic lines help
"Terminal device name(s) (ex:TXA0,TXA2... )?"
Specify the device name of terminal port to be used for the
dynamic DECnet link.
23 – Async dynamic lines yn help
"Do you want to continue Configuring this line?"
This prompt is displayed if you failed to specify an appropriate
terminal device name at the previous prompt. If you want to
terminate the configuration of an dynamic asynchronous line,
answer NO.
24 – Async floating lines number modem lines help
"Number of floating 'line speed' bps 'modem control type' modem
ctrl lines?"
This is the maximum number of terminal ports that can be used
as dynamically allocated full modem control asynchronous DECnet
links. It should not exceed the number of available terminal
ports.
25 – Async floating lines yn help
"Do you want to configure floating dynamic lines?"
If you want to configure a terminal port that can be dynamically
allocated for use as a switched DECnet link so that Dynamic
connections can be made, answer YES.
26 – Async floating lines configure more help
"Do you want to configure any more floating lines?"
If you want to configure more floating lines, answer YES.
27 – Async line speed help
"Line speed for 'terminal device name'?"
Specify the line speed in Bits per Second at which the
asynchronous link will run (for example, 2400 or 9600).
28 – Async modem control help
"Will this line require full modem control?"
If you want the full DEC Standard 52 Modem control to be used,
answer YES.
29 – Data link protocol help
"Data Link protocol for 'datalink name' ('device')?"
Specify either HDLC, DDCMP, or NONE for the point-to-point data
link protocol. The default is DDCMP.
o DDCMP (Digital Data Communications Message Protocol) provides
synchronous point-to-point connections and asynchronous static
or dynamic point-to-point connections.
o HDLC (High-Level Data Link Control protocol) conforms to the
ISO standards. HDLC provides synchronous point-to-point links
that function like DDCMP synchronous links.
o Enter NONE if either of the following statements is true.
- You do not want to run DECnet over this device
- You are using X.25 over this device
30 – Data link name help
"Data Link name to use for 'device'?"
This prompt allows you to specify a data link name for one of
the following data links depending on the type of device being
configured. If you do not want this device configured for
DECnet-Plus, enter NONE.
o CSMACD
o DDCMP
o HDLC
Ethernet devices can only be configured to run over CSMACD
datalinks. Synchronous devices can be configured to run over
DDCMP or HDLC datalinks. Asynchronous devices can only be
configured to run over DDCMP datalinks.
Specify the simple-name that you want to use for the data link or
accept the system-supplied default. HP recommends that you
take the default name even if you configure multiple data links
of the same type.
31 – fddi_large_packet_support_help
"FDDI Large Packet Support"
If an FDDI-type circuit has been found on the system, you have the
option of enabling FDDI large packet support. FDDI large packet
support allows you to fully utilize the bandwidth of FDDI.
If you choose not to enable FDDI large packet support on the system,
the FDDI circuit will use the bandwidth of CSMA-CD instead.
Note that a Phase V router on the LAN (preferably on the FDDI) is
required in order to enable the FDDI large packet support.
32 – segregated_mode_routing_help
"Segregated Mode Routing"
If you are using the ADVANCED configuration, you have the option
of using segregated mode routing or integrated mode routing
(integrated mode routing is the default).
Segregated mode routing works in the following way:
A special check is made on the packet to determine if the packet is
Phase IV translatable. If the packet is Phase IV translatable, it will
translate the packet. It will then send the translated Phase IV packet
(or the Phase V packet if it couldn't be translated) to the appropriate
router if the Phase IV or Phase V router is present. If no suitable
router is present, then the packet is sent directly to the destination
end system. (Essentially, Phase IV compatible packets are routed via
the Phase IV backbone, and extended address packets are routed via the
Phase V backbone.)
Integrated mode routing works in the following way:
If a Phase V router is present, then the packet will be sent to it.
If a Phase V router is not present, then a check will be made to
determine if the packet is Phase IV compatible.
If the packet is Phase IV compatible then it will check to see if a
Phase IV router is present and if it is then the packet will be sent
to the Phase IV router. If there is no Phase IV router present then
the packet will be sent directly in Phase IV format to the destination
end system and multicast to all end systems in Phase V format.
If the packet is not Phase IV compatible and a Phase V router is not
present, then the packet will be multicast to all end systems in
Phase V format.
33 – integrated_mode_routing_help
"Integrated Mode Routing"
If you are using the ADVANCED configuration, you have the option
of using segregated mode routing or integrated mode routing
(integrated mode routing is the default).
Integrated mode routing works in the following way:
If a Phase V router is present, then the packet will be sent to it.
If a Phase V router is not present, then a check will be made to
determine if the packet is Phase IV compatible.
If the packet is Phase IV compatible then it will check to see if a
Phase IV router is present and if it is then the packet will be sent
to the Phase IV router. If there is no Phase IV router present then
the packet will be sent directly in Phase IV format to the destination
end system and multicast to all end systems in Phase V format.
If the packet is not Phase IV compatible and a Phase V router is not
present, then the packet will be multicast to all end systems in
Phase V format.
34 – Routing circuit name help
"Routing Circuit Name for Data Link 'type'?"
Specify the simple-name that you want to use for the routing
circuit or accept the system-supplied default. HP recommends
that you take the default name even if you configure multiple
lines of the same type.
If you decide not to accept the default response, keep in mind
that the name you specify for the data link should reflect the
type of routing circuit you are configuring. The following types
may be configured:
o CSMACD
Carrier Sense, Multiple Access with Collision Detect (CSMA/CD)
protocol is the data link protocol used by Ethernet and ISO
8802-3 local area networks (LANs).
o DDCMP
Digital Data Communications Message Protocol (DDCMP) is
the data link protocol use by wide area networks (WANs).
It supports synchronous point-to-point connections and
asynchronous static or dynamic point-to-point connections.
DECnet software can use this protocol to make connections over
WANs.
o HDLC
High-level Data Link Control (HDLC) is an ISO, bit-oriented,
Data Link layer (OSI layer 2) protocol that operates over
synchronous, switched or unswitched communications links.
DECnet software can use this protocol to make connections over
WANs.
35 – X25 configure yes no help
"Do you want to configure DECnet over X.25?"
If you want to configure DECnet over X.25 (data link mapping),
answer YES. This question will only be asked if the X.25
software (or the VAX P.S.I. software) is installed on the system.
36 – X25 Routing circuit help
"Which type of X.25 circuit do you want to use?"
This prompt allows you to select the type of routing circuit you
want to use over X.25. The menu offers four choices:
o A dynamically assigned Routing circuit (menu option 1)
operates over a number of X.25 switched virtual circuits
(SVCs); both incoming and outgoing.
o A static incoming Routing circuit (menu option 2) operates
over a single incoming X.25 switched virtual circuit (SVC).
o A static outgoing Routing circuit (menu option 3) operates
over a single outgoing X.25 switched virtual circuit (SVC).
o A Permanent Routing circuit (menu option 4) simply uses a
Permanent Virtual Circuit (PVC) instead of an SVC.
37 – X25 routing circuit name help
"Routing Circuit Name to use?"
Specify the simple-name that you want to use for the routing
circuit. You can use the default or you can supply a name (for
example, X25-0).
38 – X25 template name help
"Template name?"
Specify the simple-name of an X25 Access template. A default
name is provided or you may enter your own name (for example,
X25-DA-1).
All X.25 Routing circuits use an X25 Access template to either
make or accept a network connection.
For a static outgoing circuit the X25 Access template must
specify DTE class, destination DTE address and call data. The
X25 Access template may also specify other call characteristics
to make the outbound network connection.
For a static incoming Routing circuit the X25 Access template
may specify call characteristics to accept the inbound network
connection.
For a dynamic assigned Routing circuit the X25 Access template
must specify DTE class and call data. The X25 Access template may
also specify other call characteristics to make the outbound or
accept the inbound network connections.
X25 Access templates are configured using the X.25
configuration program.
39 – X25 filter name help
"Filter name?"
If you chose to configure an X.25 Dynamic Assigned (DA)
circuit or an X.25 Static Incoming (IN) circuit, this prompt
is displayed. Specify the simple-name of an X25 Access filter.
You may accept the default or you may enter your own name (for
example, X25-IN-0).
Static incoming and dynamically assigned X.25 circuits use an X25
Access filter to receive inbound network connections.
For a static incoming circuit the X25 Access filter must specify
inbound DTE class, sending DTE address, call data value and call
data mask.
For a dynamic assigned circuit the X25 Access filter must specify
inbound DTE class, call data value and call data mask.
X25 Access filters are configured using the X.25
configuration program.
40 – X25 reachable address yn help
"Do you want to configure any reachable addresses?"
If you chose to configure an X.25 Dynamic Assigned (DA) circuit,
this prompt is displayed. If you want to configure any Reachable
Address sub-entities, answer YES. If you answer NO, the procedure
skips to the prompt "Configure another X.25 routing circuit for
DECnet?".
41 – X25 reachable address name help
"Reachable address name?"
Specify the simple-name of the reachable address sub-entity that
you want to create (for example, ACCOUNTS_DEPT).
42 – X25 reachable address prefix help
"Reachable address prefix?"
The reachable address sub-entity name is used to select the
remote DTE address to where a routing packet is sent. The
selection is done by finding a reachable address sub-entity that
has an address prefix that matches the beginning of the remote
NSAP in the routing packet.
Specify the address prefix for this reachable address entity.
The address prefix is a string of characters that is a valid
beginning of an NSAP (for example, 41:45436192:). The address
prefix will match all NSAPs.
43 – X25 reachable address dte list help
"Reachable address dte list?"
The reachable address sub-entity name is used to select the
remote DTE address to where a routing packet is sent. A reachable
address sub-entity may be configured with one or more DTE
addresses. If more than one DTE address is configured then only
one is selected each time a packet is sent. All the remote DTE
addresses must be accessible by the DTE class configured in the
X25 Access template already configured for the associated dynamic
assigned circuit.
Specify the list of remote DTE addresses for this reachable
address entity. A DTE address consists of 1 to 15 decimal
characters. The DTE addresses in the list should be separated
by commas (for example, 2,3,4).
44 – X25 reachable address again help
"Any more reachable addresses you want to configure?"
If you want to configure another reachable address sub-entity for
this circuit, answer YES.
45 – X25 configure another help
"Configure another X.25 routing circuit for DECnet?"
If you want to configure another X.25 routing circuit, answer
YES. If you answer YES, the procedure repeats the questions
regarding configuring another X.25 routing circuit.
46 – Transport NSP help
"Configure the NSP Transport?"
If you want the system to communicate with DECnet Phase IV nodes,
answer YES.
47 – Transport OSI help
"Configure the OSI Transport or run over TCP/IP?"
Answer YES if you want the system to communicate with Phase V nodes,
you want to run DECnet and/or OSI applications over TCP/IP (RFC1859
and/or RFC1006), or if you plan to install any OSI applications such
as OSAK, FTAM, or VT.
NOTE
If you answer NO to this question, the procedure still loads
the OSI transport images. However, OSI Transport is not
configured or usable until either you run the NET$CONFIGURE
procedure and answer YES to the OSI Transport question or
you create an NCL script for OSI Transport use.
48 – No transport help
"Are you sure?"
If this question is asked, it means that you elected not to
configure both the NSP Transport and the OSI Transport. This
is not recommended. If you plan to run over TCP/IP, then at
least the OSI Transport must be configured.
If you are sure that you do not want either transport configured,
answer YES. If you want to change your decision, answer NO. The
procedure will then repeat the NSP Transport and OSI Transport
questions, thus allowing you to select one or both transports.
49 – Config multi protocol network
"Is this system operating in a multi-protocol network?"
One feature of Transport is the ability to use the "Congestion
Experienced" field in the ConnectionLess Network Service (CLNS)
routing header, and to implement a "Congestion Avoidance" scheme in
heavily congested networks. The CLNS Congestion Experienced field is
used by routers that support this feature (such as DECnis) to give an
early indication of congestion. When Transport receives data that
passed through a network path where the "Congestion Experienced" bit
is set, Transport reduces the transmit rate of the sending end system
to help alieviate network congestion.
While this feature works well in networks where all network protocols
support "Congestion Avoidance" mechanisms, it has been noted that in
some heavily congested multi- protocol networks this feature can
negatively impact the performance of DECnet-Plus compared to other
protocols.
Therefore, HP recommends that Transport Congestion Avoidance be
disabled when using DECnet-Plus in heavily congested, multi-protocol
networks, if other network protocols do not implement a similar
mechanism.
Answering "Yes" to this question will disable the congestion
avoidance algorithm.
50 – Config nsp pt to pt line speed help
"Are the point-to-point lines utilizing line speeds less than
9600BPS?"
This question will only be asked if you have any point-to-point
lines (that is, any synchronous and/or asynchronous lines)
configured.
If you have any point-to-point lines running at low line speeds
(that is, lower than 9600 bps), answer YES. This will place
additional NSP NCL commands into the NSP Transport NCL script
in order to accommodate the lower line speeds. If you do not
have any point-to-point lines being utilized at low line speeds,
answer NO.
51 – Config OSI ivp applic username
"Username for OSI loopback test application to use?"
Press Return to accept the default user name for the application
loopback test account. A message will be displayed to indicate
that the default OSI templates have been created.
52 – Config OSI template create more help
"Do you want to create additional OSI templates?"
If you configure the OSI Transport, the NET$CONFIGURE procedure
automatically creates the default OSI templates that are required
by the OSAK and FTAM installation and verification procedures
(IVPs) to perform loopback testing. However, if you plan to use
OSI applications to make connections to other OSI systems, you
must create OSI templates in addition to those that are created
by default. The default OSI templates are used for loopback
testing only and cannot be used to make connections to other
OSI systems. Answer YES to create additional OSI templates.
53 – Config OSI template name help
"Name of the template?"
Press Return to accept the default OSI template name (do not type
"Return")
Enter the name you want to use for the OSI template (for example,
OSI_TEMPLATE_1) or press Return to accept the default OSI
template name (do not type "Return").
54 – Config OSI template net service help
"Type of network service (CLNS/CONS/RFC1006)?"
If you want to use Connectionless Network Service (CLNS), enter
CLNS. If you want to use Connection Oriented Network Service
(CONS), enter CONS. If you want to use RFC1006, enter RFC1006.
o CLNS NETWORK SERVICE
There are two forms of the CLNS network service. Both forms
support only one class of transport protocol: class 4.
1. CLNS with Internet/ES-IS
Any transport connection can use CLNS with Internet/ES-
IS. The communicating end systems may be on the same
subnetwork, or on different subnetworks. This network
service is provided by the implementation of the ES-IS (end
system to intermediate system) Internet routing protocols,
which route packets from the end system to an intermediate
system on the same subnetwork. The intermediate system will
ensure that packets reach their final destination. Two end
systems that implement ES-IS on the same subnetwork may
communicate without an intervening intermediate system.
2. CLNS with Null Internet
A transport connection may use CLNS with Null Internet only
when the two end systems are on the same 802.3 LAN. This
network service is provided by the inactive subset of the
Internet protocol. No intermediate system is involved in
the network connection.
o CONS NETWORK SERVICE
A transport connection can use CONS when the underlying
network connection is an X.25 connection. This type of network
service is provided by the X.25 software in the DECnet-Plus for
OpenVMS product.
CONS supports transport connections using any class of
transport protocol (that is, class 0, class 2, or class 4).
The underlying X.25 network connection can be:
- A connection between two systems attached to an X.25 Packet
Switching Data Network (PSDN), either directly or via an
X.25 gateway
- A point-to-point connection using the LAPB protocol as the
data link protocol
- A direct connection between two systems on the same IEEE
802.3 LAN, using the LLC2 protocol
In each of these cases the two end systems are on the same subnetwork.
o RFC1006 NETWORK SERVICE
The network service type RFC1006 tells the OSI transport to
run over the TCP/IP protocol stack. The network service type is
specified in an OSI Transport template.
When using DECnet applications over RFC1006 the OSI transport
template osit$rfc1006 is used for the inbound connection.
For outbound connections, the default template is used.
55 – Config OSI template classes help
"Transport Classes to support?"
Enter the number of the transport protocol class you want to
use for this template. DECnet-Plus for OpenVMS supports three
transport protocol classes: 0, 2, and 4. If you select CONS as
the network service type, the default is 0,2,4. If you select
CLNS, the default is 4. If you select RFC1006 as the network
service type, the default is 0,4. However, you can configure
multiple OSI templates.
The features of the transport service provided by each of these
protocol classes are as follows:
o Class 0
Class 0 is the most basic type of transport service, in which
there is no flow control, multiplexing, or error recovery.
o Class 2
A class 2 transport service provides all the functions of
a class 0 service, and also provides multiplexing and flow
control. The OSI Transport Service software always uses flow
control measures on class 2 connections, even though the
transport protocol standard defines this feature as being
optional within class 2.
o Class 4
A class 4 transport service provides all the functions of a
class 2 service and, in addition, provides error detection and
recovery.
56 – Config OSI template X25 template
"X25 template name?"
Enter the X.25 template name you want to use.
57 – Config OSI template x data help
"Allow use of expedited data?"
If you want to support the use of expedited data, answer YES.
58 – Config OSI template checksums help
"Allow use of Checksums?"
If you want to use the error correction feature, answer YES.
59 – Config OSI template routing protocol
"Use Full CLNP or Null Internet?"
A CLNS OSI Transport template can specify use of Internet/ES-IS
routing protocols or Null Internet routing protocol. The Null
Internet protocol only operates over LAN Routing circuits.
A CLNS OSI Transport template for use with Internet/ES-IS routing
protocols may use any Routing circuits configured; the Routing
module will determine the most suitable circuit to use. A
CLNS OSI Transport template for use with Null Internet routing
protocol can only use one Routing circuit; the Routing circuit is
selected based on its inactive area address.
60 – Config OSI template routing circuit name
"Which routing circuit is this Null Internet template for?"
Enter the routing circuit you want to use for the CLNS OSI
Transport template (for use with Null Internet routing protocol).
61 – Config OSI template inactive area help
"Which CLNS Inactive Area to use?"
A CLNS OSI Transport template specifying use of the Null Internet
routing protocol selects the Routing circuit to be used based on
the inactive area address of the Routing circuit.
If Null Internet routing is to be supported then an inactive area
address must be configured for the circuit. The inactive area
address for the circuit must be different to any area addresses
used by DECnet-Plus routers on the same LAN. If more than one
LAN Routing circuit is to be configured on this system and Null
Internet is required on each circuit, then each circuit should
have a different inactive area address.
The CLNS inactive area should be the same as the inactive area
set in routing, or else Null Internet cannot be used.
62 – CONFIG_OSI_TEMPLATE_INBOUND_PACKETS_HELP
"Will this template be used for inbound packets?"
If you want to use this template for inbound packets enter YES. If
you want to use this template for outbound packets, enter NO.
63 – CONFIG_OSI_TEMPLATE_CONS_TEMPLATE
"CONS template name?"
If the CONS template is being used for inbound or outbound packets,
the CONS template name should be the same as the name being used
for the X.25 Access template, or else you will not be able to
make any CONS connections.
Enter the name of the CONS template you want to use.
64 – CONFIG_OSI_TEMPLATE_CONS_FILTER
"CONS filter name?"
If the CONS template is being used for inbound packets, you
will be prompted for the CONS filter name. The CONS filter
name should be the same as the name being used for the X.25
Access filter, or else you will not be able to make any CONS
connections.
Enter the name of the CONS filter you want to use.
65 – CONFIG_OSI_TEMPLATE_RFC1006_LOCALPORT_HELP
"Local RFC1006 port number?"
Enter the outgoing port number to use when establishing a transport
connection at the TCP level.
66 – CONFIG_OSI_TEMPLATE_RFC1006_LISTENERPORT_HELP
"RFC1006 listener port number?"
If the RFC1006 template is being used for inbound packets, you
will be prompted for the RFC1006 listener port number. This number
should be the same as the Local RFC1006 port number, or else the
template will not be used for inbound traffic.
Enter the incoming port number used when establishing a transport
connection at the TCP level.
67 – EVD help
"Do you want to customize the Event Dispatcher?"
Answer YES, if you want to customize the Event Dispatcher
configuration. Answer NO, if you want the default Event
Dispatcher configuration only.
68 – Applic config help
"Do you want to use a default account for the 'application name'
application?"
The procedure creates the DECnet-Plus default application objects
to include in the application database. You have the option of
creating default user accounts for the following applications:
FAL, CML, MAIL, VPM, MIRROR, and PHONE.
This prompt is displayed for the standard OpenVMS applications
most commonly used. The applications are:
o File Access Listener
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.
o CMIP Management Listener
CMIP Management Listener (CML) is the DECnet-Plus management
module that implements the Common Management Information
Protocol (CMIP). It is a utility that enables the system to
respond to remote management commands. If you want an account
set up or used for CML, answer YES.
o MAIL
If you want to use the OpenVMS MAIL utility, answer YES.
o VMScluster Performance Monitor
If the system is to be a member of a VMScluster, you should
answer YES to this question. An account is needed for VPM
(VMScluster Performance Monitor) for your system to support
the OpenVMS Monitor Utility command MONITOR CLUSTER. Answer NO
if the system is to be a non-cluster end system.
o MIRROR
MIRROR is used for particular forms of loopback testing. If
you want to use MIRROR, answer YES.
o PHONE
The PHONE utility allows users on the same or different
OpenVMS systems to communicate interactively. Unlike MAIL,
where messages are received and held for your attention, PHONE
requires an immediate reply to a call (connection request).
The reply makes the connection and the interactive exchange
of messages begins. If you intend to use the OpenVMS PHONE
utility, answer YES.
69 – Start network help
"Do you want to start the network?"
Enter YES if you want to proceed to start the network and
complete your system's network configuration.
If for some reason you want to postpone starting the network,
answer NO. However, answering NO will prevent completion of
your network configuration and you will have to perform some
additional steps later when you are ready to complete your
system's network configuration. Answering NO 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 and choose menu option 2 (Change node name/namespace
name) so that the configuration procedure can finish your
system's network configuration before starting the network.
********************************************************************
Network Startup Incomplete
70 – Config basic adv help
"Do you want to continue?"
The two configuration options are BASIC and ADVANCED. Enter YES
if you want to continue with the particular configuration option
you have chosen. If you prefer at this time to choose the other
configuration option instead, enter NO and the configuration
procedure will exit.
71 – Config option help
"Which configuration option to perform?"
Choose the option you want to perform. Selecting an option allows
you to modify either the entire configuration or a particular
portion.
72 – Satisfied help
"Do you want to generate NCL configuration scripts"
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 you to the configuration
options menu. If you answer NO, the configuration procedure
returns you to the configuration options menu and does not
generate any modified NCL scripts.
73 – Applic supercede help
"Replace application script file?"
If you want to create a new NCL script file, answer YES.
74 – MOP supercede help
"Replace MOP Client script file?"
If you want to create a new MOP Client NCL script file, answer YES.
75 – Nodevice help
"Should devices be autoconfigured?"
If you answer YES, the NET$CONFIGURE procedure will
autoconfigure to find the devices. On VAX, this is done
using the SYSGEN AUTOCONFIGURE ALL command. On an Alpha,
this is done using the SYSMAN IO AUTO command. If you are
performing the initial configuration of your system and you
answer NO, then there will be no devices to configure. If you
are reconfiguring devices (that is, you selected Option 3 from
the NET$CONFIGURE main menu) and you answer NO, then there will
be no devices to configure and the procedure exits.
76 – Config osi template replace script help
"Do you want to replace the existing NSP or OSI Transport
script?"
If you reconfigure the NSP or OSI 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 or
OSI transport script.
77 – Event supercede help
"Replace Event Dispatcher NCL script file?"
If you want to create a new Event Dispatcher NCL script file,
answer YES. If you want to keep the previously generated Event
Dispatcher NCL script file, answer NO.
78 – evd_see_block_events_help
"Display the events logged to the console of this machine?"
You have the option of displaying the events that are logged to the
console of this machine. If you do not want to see the events logged
to the console of this machine, NET$CONFIGURE will block the events
for you.
Answer YES if you want to see the events that are logged to the
console of this machine. If you do no want to see the events
logged to the console of this machine, answer NO and NET$CONFIGURE
will block the events for you.
79 – EVD custom config sink help
"Configure a (or another) Sink?"
The first prompt displayed concerning sink configuration when you
select menu option 6 is "Configure a Sink?".
If you want to customize information pertinent to the sink,
answer YES (for example, the sink name and where you would like
to send the output: a terminal, a printer, or a file?).
After you have configured a sink, the procedure displays the
prompt "Configure another Sink?".
If you do not want to configure another sink, enter NO and
proceed to the next prompt. If you want to configure another
sink, enter YES. The procedure then returns you to the "Sink
name?" prompt and repeats the prompts required to configure
another sink.
80 – Evd sink name help
"Sink name?"
Specify the name of the sink you want to use for the local node
(for example, local_sink).
81 – Event sink maxbuff help
"Maximum buffer size?"
Specify the maximum number of octets that the sink allows to
process events (for example, 16384).
82 – Evd sink object name help
"Object name?"
Specify the full DECdns name of the object for which the
sink accepts incoming connections. Unless the value of this
characteristic is null, the sink employs the Session Control
layer's Keep me Here function to maintain the object name in the
namespace.
83 – Evd sink end user help
"End user specification?"
Specify the DNA session control local address for which the sink
accepts incoming connections (for example, number=82).
84 – Evd sink catch all filter help
"Catch all filter action?"
Specify the action to take if neither the specific filter setting
nor the global filter setting matches an event or if a filter
setting that does match an event is set to Ignore. The choices
are:
o BLOCK - Discard the event.
o PASS - Report the event.
85 – Event sink description help
"Description?"
Specify an informational string that can be used to describe the
sink.
86 – Event sink displayuids help
"Display UIDs?"
Answering YES displays the entity's unique identifier, which is
generated when the entity is created.
87 – Evd sink client help
"Client type?"
Specify how the application is to accept the events received by
the sink. The choices are:
o CONSOLE - Events go the operator's console (OPCOM).
o DEVICE - Events go to a device.
o FILE - Events go to a file.
88 – Evd sink file name help
"File name?"
Enter the file specification that you want to use to capture
events (for example, SYS$MANAGER:EVD_EVENTS.LOG).
89 – Evd sink device name help
"Device name?"
Enter the device that you want to use to capture events (for
example, TWA1:).
90 – Evd custom configure obs help
"Configure an (or another) Outbound Stream?"
The first prompt displayed concerning outbound stream
configuration when you select menu option 6 is "Configure an
Outbound Stream?". If you want to configure an outbound stream,
answer YES.
After you have configured an outbound stream, the procedure
displays the prompt "Configure another Outbound Stream?".
If you do not want to configure another outbound stream, enter NO
and proceed to the next prompt. If you want to configure another
outbound stream, enter YES. The procedure then returns you to the
"Outbound Stream name?" prompt and repeats the prompts required
to configure another outbound stream.
91 – Evd obs name help
"Outbound Stream name?"
Specify the outbound stream name that is to be managed by this
command (for example, local_stream).
92 – Evd sink maxbuff help
"Maximum buffer size?"
Specify the number of octets that the outbound stream allows
to process events. This value is derived from (but is not
necessarily equal to) the value specified in the MAXIMUM BUFFER
SIZE argument of the CREATE command (for example, 16384).
93 – Evd sink template help
"OSI transport template?"
Specify the transport template for this stream's connection.
94 – Evd obs connect retry timer help
"Connect retry timer?"
Specify the number of seconds to wait between connection
attempts. The connect retry timer operates continuously from
the time the outbound stream is enabled until the stream is
disabled or until the CONNECT TIMER ENABLED characteristic is
set to FALSE. If the outbound stream is already connected to the
sink when the timer expires, no connection is attempted at that
time. The timer resets and connection attempts continue whenever
the timer expires.
95 – Evd obs connect timer enabled help
"Connect timer enabled?"
Answer YES to have the connect retry timer operational. A NO
reply disables it.
96 – Evd obs disconnect timer help
"Disconnect timer?"
Specify the number of seconds to wait before shutting down an
idle connection. A 0 value indicates that the disconnect timer
is not operating and that connections are never automatically
disconnected.
97 – Evd obs catch all filter help
"Catch all filter action?"
Specify the action to take if neither the specific filter setting
nor the global filter setting matches an event or if a filter
setting that does match an event is set to Ignore. The choices
are:
o BLOCK - Discard the event.
o PASS - Report the event.
98 – Evd obs sink object help
"Sink object?"
Specify the full DECdns object name of the sink associated
with this outbound stream. This object name is used to make the
connection with the sink.
99 – Evd obs sink node help
"Sink node?"
Specify the full node name (DECdns namespace name included) of
the sink associated with outbound stream.
100 – Evd obs sink end user help
"Sink end user?"
Specify the sink session control end user specification of
the sink associated with this outbound stream (for example,
number=82).
101 – Evd obs sink address help
"Sink address?"
Specify the sink address tower of the sink associated with this
outbound stream.
102 – Event relay help
"Configure Phase IV Relay?"
Answer YES to use the Phase IV Relay. This allows you to record
and process events that occur on an OpenVMS VAX system running
DECnet-VAX Phase IV software. The Phase IV Relay entity receives
the events from a Phase IV node, encapsulates them and posts them
in the DECnet-Plus system event dispatcher.
103 – Applic add delete help
"Do you want to ADD or DELETE an Application?"
Answer ADD to create the application entity on the local node,
allocate resources for it, and open the service interface. Answer
DELETE to delete the entity and reclaim associated resources.
104 – Applic name help
"What is the name of the Application?"
When defining an application, you must identify the name of the
object. DECnet object names are descriptive alphanumeric strings
of up to twelve characters.
105 – Applic areyousure help
"Are you sure you want to DELETE this application?"
If you want to delete the application, answer YES.
106 – Applic destination type help
"What is the destination type for 'application'?"
The destination type can be either NAME or NUMBER. To select
NAME, simply press Return. To select NUMBER, enter NUMBER and
press Return.
107 – Applic destination name help
"What is the destination name (or number) for 'application'?"
The destination type can be either a name or a number.
If you selected name as the destination type in response to
the previous prompt, your reply to this prompt can be either
the application name (for example, NOTES), or a destination
object name (for example, IAF:.SALES.BOSTON). The destination
object name is the DECdns full name of the node that provides the
application.
The application name can be from 1 to 16 characters. The
destination object name can be a maximum of 512 characters and
is entered in this format:
NamespaceNickname:.DirectoryPath.NodeObject
If you selected number as the destination type in response to
the previous prompt, your reply to this prompt must be an object
number.
DECnet software uses object numbers as unique object identifiers.
Object numbers have a range of 1 to 255. Generic objects such as
MAIL and FAL have object numbers that are recognized throughout
the network. User-defined images may have unique object numbers;
numbers between 128 and 255 are reserved for this purpose.
If you are adding a user-defined application, pick a number from
128 to 255. If you are adding an application defined by HP,
select the appropriate number from Object Type Numbers.
Table 1 Object Type Numbers
Number Mnemonic Description
0 Task User program
1-16 Reserved for HP use
17 FAL File Access Listener for remote file and
record access
18 HLD Host loader for RSX-11S downline task
loading requests
19 NML Network Management Listener Object
20 RSTS/E media transfer program (NETCPY)
21-22 Reserved for HP use
23 REMACP Network terminal handler (host side)
24 Network terminal handler (terminal side)
25 MIRROR Loopback mirror
26 EVL Event receiver
27 MAIL OpenVMS Mail Utility
28 Reserved for HP use
29 PHONE OpenVMS Phone Utility and RSX-11M/M-PLUS
Phone Utility
30-41 Reserved for HP use
42 CTERM Network terminal handler
43-62 Reserved for HP use
63 DTR DECnet Test Receiver object
64-127 Reserved for HP use
128-255 Reserved for customer use
108 – Applic another address yn help
"Do you want to specify another application address?"
If a node has more than one application address, enter YES and
the previous prompts will be repeated.
109 – Applic client help
"What is the name of the Client for 'application'?"
Specify the name of the local user that will be activated upon
receipt of the connect request containing the destination name
matching one of the values in the destination names attribute.
110 – Applic image name help
"What is the Image name for 'application'?"
Specify the filename of the program to be invoked upon receipt
of a Connect Request containing a DestinationName matching one of
the values in the DestinationNames: attribute.
111 – Applic incoming alias help
"Incoming Alias for 'application' enabled?"
Specify how the specified application responds to incoming
connect requests directed to the alias node address. If you
specify FALSE, the application does not allow a specified
application to receive incoming connect requests that have been
directed to the alias node address.
112 – Applic incoming proxy help
"Incoming Proxy for 'application' enabled?"
Controls whether incoming proxy requests are honored. If you
specify FALSE, requests to invoke proxies on incoming requests
will be ignored.
113 – Applic outgoing alias help
"Outgoing Alias for 'application' enabled?"
Specify whether a particular object uses the alias node
identifier in its outgoing connect requests. If you specify
FALSE, the specified object is not allowed to use the alias node
address in its outgoing connect requests.
114 – Applic outgoing proxy help
"Outgoing Proxy for 'application' enabled?"
Specify the default action to execute when a user does not
explicitly specify whether or not to invoke a proxy. If you
specify FALSE, there will be no default action.
115 – Applic require synonym help
"Require node synonym for 'application' enabled?"
If you specify TRUE, then by default the remote node name is
passed to the application in synonym form. If a synonym is not
available, then the full name is used. If you specify FALSE, then
the full name is passed to the application by default.
116 – Applic osi tsel help
"What is the Incoming OSI TSEL for 'application'?"
Specify the transport service access point (TSAP) identifier for
which the specified application will accept connections.
NOTE
This function is currently not implemented. Press Return to
continue to the next prompt.
117 – Applic config user name help
"What is the User Name for 'application'?"
Enter the user name that you want to use when creating the
account for the application you are configuring.
If you do not want to create an account for that application, you
can either enter NONE and press Return or press the space bar and
press Return.
118 – Applic UIC help
"What UIC should 'application' use?"
Specify the UIC allocated upon creation of this application
entity instance.
119 – Applic rights id help
"Rights identifiers for 'application'?"
Specify the rights identifiers (if any) needed by the
application. If there are two or more rights identifiers,
separate them with commas.
120 – Mop add delete help
"Do you want to ADD or DELETE a MOP Client?"
Answer ADD to create an entity on the specified node, allocate
resources for it, and open the service interface. Answer
DELETE to delete the entity from the specified node and reclaim
associated resources.
121 – Mop client name help
"Name of the MOP Client?"
Specify the simple-name of the client (for example, SUPERX).
122 – Mop client areyousure
"Are you sure you want to DELETE this client?"
If you want to delete this client, answer YES.
123 – Mop circuit help
"Circuit for 'client name'?"
Specify the name of the MOP circuit to be used for this client.
124 – Mop address help
"Physical addresses for 'client name'?"
Specify the set of LAN addresses for the specified client on the
circuit specified by the CIRCUIT characteristic.
125 – Mop secondary loader help
"Secondary Loader for 'client name'?"
Specify the files to be loaded when the client requests a
secondary loader during a downline load operation. File
identifications are interpreted according to the file system
of the local system.
126 – Mop tertiary loader help
"Tertiary Loader for 'client name'?"
Specify the files to be loaded when the client requests
a tertiary loader during a downline load operation. File
identifications are interpreted according to the file system
of the local system.
127 – Mop system image help
"System Image for 'client name'?"
Specify the files to be loaded when the client requests
a tertiary loader during a downline load operation. File
identifications are interpreted according to the file system
of the local system.
128 – Mop diagnostic image help
"Diagnostic Image for 'client name'?"
Specify the files to be loaded when the client requests a
diagnostic image during a downline load operation. File
identifications are interpreted according to the file system
of the local system.
129 – Mop management image help
"Management Image for 'client name'?"
Specify the files to be loaded when the client requests a
management image during a downline load operation. File
identifications are interpreted according to the file system
of the local system.
130 – Mop script file help
"Script File for 'client name'?"
Specify the files to be loaded when the client requests a CMIP
initialization script during a downline load operation. File
identifications are interpreted according to the file system of
the local system.
131 – Mop dump file help
"Dump File for 'client name'?"
Specify the files to write to when the client is upline dumped.
132 – Mop dump address help
"Dump Address for 'client name'?"
Specify the address of the files to write to when the client is
upline dumped.
133 – Mop verification help
"Verification for 'Client name'?"
Specify the verification string to be sent in a boot message to
the specified client.
134 – Mop iv client address help
"Phase IV Client Address (aa.nnnn) for 'mop client name'?"
Specify the Phase IV node address to be given to the client
system when it is loaded. This address is passed in a load
characteristics message; whether it is needed depends on the
software being loaded.
135 – Mop iv client name help
"Phase IV Client Name for 'mop client name'?"
Specify the Phase IV node name to be given to the client system
when it is loaded. This name is passed in a load characteristics
message; whether it is needed depends on the software being
loaded.
136 – Mop iv host address help
"Phase IV Host Address for 'mop client name'?"
Specify the Phase IV node address to be passed as the host node
address when a client is loaded. This address is passed in a
load characteristics message; whether it is needed depends on the
software being loaded.
137 – Mop iv host name help
"Phase IV Host Name for 'mop client name'?"
Specify the Phase IV node name to be passed as the host node
name when a client is loaded. This name is passed in a load
characteristics message; whether it is needed depends on the
software being loaded.
138 – Alias add delete help
"Do you want to ADD or DELETE an alias?"
Answer ADD to add the specified node to the cluster. Answer
DELETE to remove the specified node from the cluster.
139 – Alias name help
"Full name of Cluster Alias"
Specify the full name that uniquely identifies the cluster
alias (for example, IAF:.SALES.BOSTON).
140 – Alias areyousure
"Are you sure you want to DELETE this alias?"
If you answer YES to this prompt, the node is removed from the
cluster.
141 – Alias address help
"Cluster Alias Phase IV Address (aa.nnnn OR AA-00-04-00-xx-xx)"
Specify either the system's DECnet Phase IV node address or
physical address.
o The Phase IV node address has the format
are_-number.node_number (for example, 63.171).
o The 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 physical address:
1. Convert the Phase IV node address to its decimal equivalent
follows:
(area-number * 1024) + node-number = decimal equivalent
(For example, (63 * 1024) + 171 = 64683 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, 64683 decimal = FCAB hexadecimal, reversed =
ABFC hexnodeaddress)
3. Incorporate the hexadecimal node address in the following
format:
AA-00-04-00-hexnodeaddress (For example, AA-00-04-00-AB-
FC)
142 – Selection weight help
"Selection weight for this cluster node [0 for satellites]"
The selection weight determines the number of sequential incoming
connects to be 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 is used to apportion 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 VMScluster satellites should generally have a value of zero.
Specify a nonzero selection weight if this node is locally
connected to a dual-ported disk, or if it will be serving any
multihost disks to other cluster members. Values between 5 and
10 are suggested.
143 – Pwdlck help
"Do you want to continue with the Configuration?"
Password generation is not allowed on your system. If you answer
YES, the configuration will continue and null passwords will be
used. If you answer NO, the configuration procedure will end.
144 – Script Common help
Create a cluster common startup script?
There is no startup script found for the component being configured,
meaning that NET$CONFIGURE will create one. Because this script
does not contain node specific information, it may be created to
be common to all systems in this cluster, or specific to this
cluster member only. If you answer YES to this question, the
script will be made common to all systems in the cluster, and all
further configuration of this component will affect all members of
the cluster.
145 – Script MoveCommon help
Move the startup script to the cluster common area?
The component being configured has a startup script that is used only
by this cluster node. Since this component's startup script contains
no system specific information, it may be made common to all systems
in this cluster, so that all systems in the cluster may use a common
script. If you answer YES to this question, the existing script file
will be moved to the cluster common directory, and all further
configuration of this component will affect all members of the
cluster.
146 – Script OverrideCommon help
Override the cluster common default startup script?
The component being configured uses a startup script that is common
to all systems in this cluster. You may create a copy of this script
which is specific to this system only. All further configuration of
this component will affect only this system. If you answer YES to
this question, a copy of the startup script will be created that
overrides the cluster common startup script.
147 – Script DeleteOverride help
Delete the local startup script?
The component being configured has a system specific startup script
that overrides the cluster's default startup script. If you answer
YES to this question, all further configuration of this component
will affect all members of the cluster.
148 – Script DeleteCommon help
Delete the cluster common startup script?
The component being configured has a system specific startup script
that overrides the cluster's default startup script. Answering YES
to this question will delete the cluster common startup script. This
should not be done unless all members of the cluster have also
created system specific startup scripts for this component.
149 – Autoconfig RootDevice help
Device containing system roots:
Configuring cluster satellites involves finding the system root from
which the satellite boots. Normally, this is SYS$SYSDEVICE:,
although it is possible to install system roots to a different
volume.
The device given in response to this question will be searched for
all system roots. Those that are found which do not contain a
checksum database are assumed to be Phase IV nodes, and are
candidates for being flagged for Phase V autoconfiguration.
150 – Autoconfigure Satellite help
Upgrade Phase IV satellite?
A system root was found that does not contain a Phase V checksum
database, and is therefore assumed to be a Phase IV system.
Answering Yes to this question will cause that cluster node to be
flagged to run a Phase V autoconfiguration on its next reboot.
151 – Autoconfigure FullName help
Enter the full name
Enter the node full name you want to use. DECnet-Plus node full names
should be planned carefully and must be unique within the directory
service. If your network administrator has not assigned a unique
node full name for your system, be sure that you read DECnet-Plus
for OpenVMS Introduction, Planning, and Glossary before you do so.
This manual also contains guidelines for using the directory services
DECdns and the Local File.
152 – Root Device help
Device for node root:
In configuring a cluster member other than the system on which
NET$CONFIGURE executes, the location of the member's system root must
be specified. The answer to this question is the disk device on
which the cluster member's system root resides.
153 – Root Directory Help
Directory for node root:
In configuring a cluster member other than the system on which
NET$CONFIGURE executes, the system root directory name must be
specified. The system root directory is of the form "SYSxxxx", where
"xxxx" is the hexadecimal root number from which that member loads.
154 – MOP Run Help
Load MOP on this system?
By default, MOP is not started by NET$STARTUP. In order to make this
system service MOP requests, NET$STARTUP_MOP must be defined to
signal NET$STARTUP to load the MOP software. This symbol is normally
defined in SYS$STARTUP:NET$LOGICALS.COM.
Answering YES to this question will modify SYS$STARTUP:
NET$LOGICALS.COM for you, to enable MOP service on this system.
Answering NO will remove the logical name definition from
SYS$STARTUP:NET$LOGICALS.COM. Note that this will have no effect if
the NET$STARTUP_MOP is defined elsewhere.
155 – enable_phaseiv_addressing_help
Enable Phase-IV Addressing on Routing Circuit?
This allows Phase IV addressing to be enabled on a broadcast circuit.
There should be only one such circuit enabled for each LAN connected
to the system. If the system is connected to only one LAN, this
should be enabled for only one circuit.
By default, NET$CONFIGURE will only enable Phase IV addressing on the
first broadcast circuit it configures.
156 – max_tran_connects
Maximum Logical Links
The maximum number of active transport connections allowed at one
time.
157 – max_tran_rcv_win
Transmit/Receive Windows and Receive Buffer count
HP recommends setting a value of 20 for "Maximum Transmit and
Receive Window" and the value of "Maximum Receive Buffers" to be set
to no more than ("Maximum Window" * "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, 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" * "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" / "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.
158 – eshello_timer
The Default ESHello Timer attribute determines the interval, in
seconds, when the ES sends out its hello.
This interval multiplied by three is the amount of time the other end
of a routing adjacency will wait before determining that this system
is no longer able to accept connections.
159 – addr_update_int
Session Control Address Update Interval?
This sets the Session Control Address Update Interval characteristic.
This characteristic specifies the minimum time (in seconds) allowed
between updates of address information. This prevents modifications
to the set of local towers to be updated more frequently than the
value given by this parameter.
160 – routing_circuit_cost_help
Level n Cost for Routing Circuit?
This sets the Routing Circuit cost for Level 1 or Level 2 traffic.
This question is relevant only to systems that are configured as
L1ROUTER or L2ROUTER. This cost is used in the computation of the
optimum network routing of packets originating from the system, or
forwarded by the system.
161 – routing_circuit_priority_help
Level n Router Priority for Routing Circuit?
This sets the priority for becoming a LAN designated router. This
attribute is supported only if the circuit's characteristic type is
CSMA-CD, and if the system is configured as L1ROUTER or L2ROUTER.
162 – routing_type_help
What type of node (Endnode or Router)?
This sets the routing type for the node; whether the node will be an
end system, or whether it will be capable of routing network traffic
that originates elsewhere. Answer "Endnode" if the system only has
one connection to the network, or if there are other dedicated
routers accessible to the system. Answer "Router" only if you indend
this system to route network traffic.
If you answer "Router," you must have the proper license for the host
based routing software to function.
163 – router_type_help
Type of routing node (L1 or L2)?
A routing node may route traffic at two levels; Level 1 refers to the
traffic in the portion of the network that is local to the routing
node. Level 2 refers to traffic between major network segments.
164 – maximum_path_splits
Maximum path splits?
A routing node may use multiple paths of equal cost to route traffic.
The answer to this question will be the maximum number of these paths
that traffic will be split between.
165 – phaseiv_max_address
Phase IV Maximum Address?
When forwarding Phase IV packets, a routing system will refuse to
forward any packets for node addresses higher than the routing
Phase IV Maximum Address. The answer to this question will be the
maximum Phase IV address that the router will consider; a value of
1023 is recommended.
166 – phaseiv_max_area
Phase IV Maximum Area?
When forwarding Phase IV packets, a level 2 router will refuse to
forward any packets for node area addresses higher than the routing
Phase IV Maximum Area parameter. The answer to this question will be
the maximum Phase IV area number that the router will consider; a
value of 63 is recommended.
167 – nsp_flow_policy
"NSP flow control policy (SEGMENT, NO)?"
The NSP flow control policy to be used on this system. The allowed
options are SEGMENT FLOW CONTROL (the default) and NO FLOW CONTROL.
168 – escache_size
The Routing ES Cache Size attribute specifies the maximum number of
entries in the ES Cache. This parameter may take values from 1 to
4096; the default value is 512.
169 – phasev_not_loaded
HP advises that you reboot before invoking net$configure because
the Phase V software is not yet properly loaded.
170 – osi_over_tcpip
If you wish to run OSI applications such as OSAK, VT, FTAM, or
X.25 over TCP/IP using RFC1006, answer YES to this question.
This will cause net$configure to include port 102 in the set of
osi transport rfc1006 listener ports attribute of your
SYS$MANAGER:NET$OSI_TRANSPORT_STARTUP.NCL script. Execution of
this script will enable OSI over TCP/IP on the local node.
However, in order to establish RFC1006 connections, you must also
ensure that:
o TCP/IP for OpenVMS and PWIP software is configured and running
on both the local and remote nodes; and
o The remote node also has OSI over TCP/IP enabled (i.e., it
must also be listening on port 102).
171 – decnet_over_tcpip
If you wish to run DECnet applications such as CTERM, MAIL, FAL,
etc., over TCP/IP using RFC1859, answer YES to this question.
This will cause net$configure to include port 399 in the set of
osi transport rfc1006 listener ports attribute of your
SYS$MANAGER:NET$OSI_TRANSPORT_STARTUP.NCL script. Execution of
this script will enable DECnet over TCP/IP on the local node.
However, in order to establish RFC1859 connections, you must also
ensure that:
o TCP/IP for OpenVMS and PWIP software is configured and running
on both the local and remote nodes; and
o The remote node also has DECnet over TCP/IP enabled (i.e., it
must also be listening on port 399).
172 – decnet_interfaces_help
If you wish to run DECnet applications such as CTERM, MAIL, FAL,
etc., over TCP/IP using RFC1006/RFC1859, you can select the
IP-configured interfaces that should be used to receive inbound
RFC1006 connection requests.
You can either answer ALL to this question, or you can give a
list of comma-separated IP addresses on which the inbound
connections should be received.
Note: Currently this feature works for static IP addresses only.
Hence if the IP address(es) of the interfaces change then
a re-configuration is required.
This will cause net$configure to include the IP addresses in the
set of osi transport rfc1006 listener ipaddresses attribute of
your SYS$MANAGER:NET$OSI_TRANSPORT_STARTUP.NCL script. However,
in order to receive inbound RFC1006/RFC1859 connections, you must
also ensure that:
o TCP/IP for OpenVMS and PWIP software is configured and running
on both the local and remote nodes; and
o The local node has DECnet/OSI over TCP/IP enabled (i.e., it
must be listening on port 399/102 on at least one IP-configured
interface).
173 – new_server_not_dns
The presence of the SYS$SYSTARTUP:DNS$SERVER_STARTUP.COM procedure
indicates that you want to configure this node to be a DNS server.
The SYS$MANAGER:DNS_FILES.TXT file either is not present or does not
point to a valid directory. Therefore, it appears that you are in
the process of configuring this node as a DNS server for the first
time.
If you do not wish to enable the DECdns server software at this time,
answer NO to this question. This will cause your node to be
configured as a DNS Clerk, and the list of the directory services
that you just provided will be used.
If you do wish to configure this node as a server, answer YES to be
prompted for a new list of directory services. The list that you
provide must begin with DECdns so that the initial DECdns server
configuration can be established. Although HP recommends that
DECdns servers always use DECdns as their primary naming service,
you may later choose to reconfigure the DNS server to use a primary
naming service other than DECdns by running net$configure again and
selecting Option 2.
174 – old_server_not_dns
Answer YES to be prompted for a different list of naming services
which includes DECdns as the first entry.
Answer NO if you wish to ignore the recommendation to use DECdns
as the primary naming service on this previously configured DNS
server. If you do this, net$configure will automatically attempt
to set up access control so that your server can still access its
DECdns namespace. However, it may still be necessary for you to
manually perform some access control adjustments.
175 – fully_qualified_host_name
A fully qualified host name is the host name as specified in
DNS/Bind. It consists of a series of simple names starting with
the most specific simple name, for example:
mynode.hp.com
Alternatively, you may enter the domain fullname at this prompt.
The domain fullname consists of the DOMAIN namespace nickname,
followed by a colon, and the fully qualified host name, for example:
DOMAIN:mynode.hp.com
176 – decdns_or_local_fullname
Fullnames in the DECdns or Local namespaces will contain a
namespace nickname, followed by a colon, then one or more
simplenames each preceded by a period. The initial period
signifies the root directory. These ordered simplenames
specify the node's position within the naming heirarchy from
least specific to most specific. The rightmost simplename
represents the node itself. Here are examples of DECdns and
LOCAL fullnames:
THIS_NS:.branch.office.mynode
LOCAL:.loc.mynode
Local fullnames always start with the reserved namespace
nickname "local". DECdns namespace nicknames will vary.
177 – found_server_disabled
Answer YES to configure this node as a DNS Server. This
will rename SYS$STARTUP:DNS$SERVER_STARTUP.COM-DISABLED
to .COM. If this node was configured at one time to be a
DNS Server, then that previous configuration will be used.
If it has never been configured as a DNS Server, then a new
configuration will be created.
Answer NO to this question if you wish to remain a DNS
Clerk.
178 – found_old_server
If you answer NO to this question, the system will use
the pre-existing DNS server configuration.
Answer YES to this question if you wish to instead bring
this node up as a DNS clerk.
179 – confirm_new_server
This node has not yet been configured as a DNS server;
however, the DNS server software has been installed.
If you do not wish to configure the server software at
this time, answer YES to this question to disable the
startup of the server.