|
HP OpenVMS Systems Documentation |
|
DECnet-Plus for OpenVMS
|
| Previous | Contents | Index |
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 answer 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 1.3.5 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.
1.4 Configuring the Network Service Protocol (NSP) Transport
If you want the system to communicate with DECnet Phase IV nodes, answer YES to the following question.
* Configure the NSP Transport? [YES] : |
If you answer NO, the procedure still loads the NSP Transport image. However, NSP Transport is not configured or usable until you run the net$configure procedure and answer YES to the question, "Configure the NSP Transport?"
To determine the maximum number of active transport connections allowed at any one time to this transport, the procedure displays the following prompt:
* Maximum number of logical links? [200] : |
You are then prompted to set the following values:
* Maximum transmit and receive window? [20] : |
* Maximum receive buffers? [4000] : |
DIGITAL recommends setting a value of 20 for the maximum transmit and receive window option. The recommended value to set the maximum receive buffers is no more than maximum window multiplied by maximum transport connections for normal network operation in a typical network environment.
Selecting other values than these can significantly alter the behavior of your system and network and should only be done after a thorough analysis of your network traffic and application requirements.
High values of maximum receive buffers may require considerable buffering capacity on your node; therefore, a non-paged pool should be allocated accordingly. If your node does not have enough non-paged pool, maximum receive buffers should be set to a smaller value than maximum window multiplied by maximum transport connections.
The transport receiver's window is determined by a combination of maximum transport connections, maximum receive buffers, and maximum window. During the life of the connection, the receiver quota fluctuates according to the value of maximum receive buffers divided by currently active connections. The credit window sent to the remote transmitter may or may not be this quota value, depending on the value of maximum window. If maximum window is set to less than the determined receiver quota, this value is used instead for the credit granted to the remote transmitter.
The transmitter of a transport connection uses the credit sent by the
remote receiver as its transmit window, unless its maximum window is a
lower value. In that case, maximum window is used for the transmitter
window.
1.5 Configuring the OSI Transport
If you want the system to communicate with DECnet-Plus nodes, OSI nodes of other vendors, or if you plan to install the OSAK, FTAM, or VT software, answer YES. If you want to use the DECnet over TCP/IP and/or OSI applications over TCP/IP, answer YES.
* Configure the OSI Transport? [YES] : |
If you answer NO, the procedure still loads the OSI transport images. However, OSI transport is not configured or usable until you run the net$configure procedure and answer YES to the OSI transport question.
To determine the maximum number of active transport connections allowed at any one time to this transport, the procedure displays the following prompt:
* Maximum number of logical links? [200] : |
You are then prompted to set the following values:
* Maximum transmit and receive window? [20] : |
* Maximum receive buffers? [4000] : |
DIGITAL recommends setting a value of 20 for the maximum transmit and receive window option. The recommended value to set the maximum receive buffers is no more than maximum window multiplied by maximum transport connections for normal network operation in a typical network environment.
Selecting other values than these can significantly alter the behavior of your system and network and should only be done after a thorough analysis of your network traffic and application requirements.
High values of maximum receive buffers may require considerable buffering capacity on your node; therefore, a non-paged pool should be allocated accordingly. If your node does not have enough non-paged pool, maximum receive buffers should be set to a smaller value than maximum window multiplied by maximum transport connections.
The transport receiver's window is determined by a combination of maximum transport connections, maximum receive buffers, and maximum window. During the life of the connection, the receiver quota fluctuates according to the value of maximum receive buffers divided currently active connections. The credit window sent to the remote transmitter may or may not be this quota value, depending on the value of maximum window. If maximum window is set to less than the determined receiver quota, this value is used instead for the credit granted to the remote transmitter.
The transmitter of a transport connection uses the credit sent by the remote receiver as its transmit window, unless its maximum window is a lower value. In that case, maximum window is used for the transmitter window.
You are then prompted:
* Run OSI Applications over TCP/IP? [YES] : |
Answer YES to this question if you want to run any of your OSI applications over TCP/IP. This causes the configuration utility to build the appropriate RFC 1006 template and establish a listener port for port 102.
* Run DECnet over TCP/IP? [YES] : |
Answering YES to this question enables DECnet-Plus to run over a TCP/IP
network to any system that has enabled this same feature. The
configuration utility builds the appropriate RFC 1859 template and
establishes a listener port for Port 399. (The default name for the RFC
1859 template is osit$rfc1006plus.)
1.5.1 Congestion Avoidance
One feature of OSI transport is the ability to use the Congestion Experienced field in the Connectionless-mode 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 OSI transport receives data that passed through a network path where the Congestion Experienced bit is set, OSI transport reduces the transmit rate of the sending end system to help alleviate network congestion.
This feature works well in networks where all protocols support Congestion Avoidance mechanisms. However, it has been noted that in some heavily congested multi-protocol networks, this feature can negatively impact the performance of DECnet compared to other protocols.
DIGITAL recognizes that most of its customers have multi-protocol networks. In this environment, not all network protocols have Congestion Avoidance mechanisms. Therefore, the default of this characteristic is disabled.
If you operate in an environment where you can take advantage of Congestion Avoidance mechanisms, DIGITAL recommends that you enable the feature again.
You are asked a new question about multi-protocol networks:
* Is this system operating in a multi-protocol network? [YES] : |
If you take the default answer of YES, then the OSI transport Congestion Avoidance characteristic is set to FALSE.
A NO answer to this question sets the characteristic to TRUE.
To change transport Congestion Avoidance values, you must invoke
net$configure in ADVANCED mode and use Option 4 (Configure
Transports) and answer NO to the question.
1.5.2 Setting Up the OSI Loopback Test Application Account
If you answered YES to the "Configure the OSI Transport?" question described earlier, the procedure displays the following prompt:
* Username for OSI loopback test application to use? [SYSTEST] : |
Press Return to accept the default user name for the application loopback test account. The procedure displays a message stating that the default OSI templates have been created.
%NET$CONFIGURE-I-CREDEFOSITEMPLATE, created default OSI templates |
If you configure OSI transport, net$configure automatically creates the default OSI templates required by the OSAK and FTAM installation and verification procedures (IVPs).
* Do you want to create additional OSI templates? [NO] : yes |
If you answer YES to the previous prompt, the procedure displays prompts to obtain the information required to configure the OSI template; otherwise, the procedure skips to the Event Dispatcher question (see Section 1.6).
* Type of network service (CLNS/CONS/RFC1006)? [CLNS] : |
If you want to use Connectionless-mode Network Service (CLNS), press Return. If you want to use Connection Oriented Network Service (CONS), enter CONS. If you want to use DECnet over TCP/IP and/or OSI applications over TCP/IP enter RFC1006.
For more information about types of network service, refer to the DECnet-Plus for OpenVMS Network Management guide or type a question mark (?) at the prompt.
Depending on which network service you select, you will see one of the following prompts:
* Name of the OSI template? [OSIT$CLNS_Default0] : |
* Name of the OSI template? [OSIT$CONS_Default0] : |
* Name of the OSI template? [OSIT$RFC1006_Default0] : |
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.
* Will this template be used for inbound packets? : |
If you want this template to be used for inbound connections, enter YES. If you want this template to be used for outbound connections, enter NO.
* Transport Classes to support? [4] : |
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 RFC 1006, the default is 0, 2. You can also
configure multiple OSI templates. For more information about transport
protocol classes, refer to the DECnet-Plus for OpenVMS Network Management guide or type a question
mark (?) at the prompt.
1.5.3.1 CLNS Network Service
If you select the network service CLNS, you will see the following prompt:
* Use full CLNP or Null Internet? [Full CLNP] : |
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 can use any routing circuits configured; the Routing module determines the most suitable circuit to use. A CLNS OSI transport template for use with Null Internet routing protocol can only use one routing circuit; routing circuit selection is based on its inactive area address.
If you want to create additional OSI templates and you answer Null Internet to the "Use full CLNP or Null Internet?" prompt, the procedure displays the following prompt:
* Which routing circuit is this Null Internet template for? [CSMACD-0] : |
Enter the routing circuit you want to use for the CLNS OSI transport template (for use with Null Internet routing protocol).
* Which CLNS Inactive Area to use? [49::FF-00] : |
A CLNS OSI transport template that specifies the Null Internet routing protocol selects the routing circuit based on the inactive area address of the routing circuit.
If you plan to support Null Internet routing, you must configure an inactive area address for the circuit. The inactive area address for the circuit must be different than any area addresses used by DECnet-Plus routers on the same LAN. If you plan to configure more than one LAN routing circuit on this system, and you need Null Internet on each circuit, then each circuit should have a different inactive area address.
The CLNS inactive area must be the same as the inactive area set in
routing for Null Internet to be used.
1.5.3.2 CONS Network Service
If you selected CONS as the network service type, the procedure displays the following prompt:
* CONS template name? : |
Enter the CONS template name you want to use.
The CONS template name must be the same as the name used for the X25 Access template for you to make any CONS connections.
If the CONS template is used for inbound packets, you will see the following prompt:
* CONS filter name? : |
Enter the CONS filter name you want to use. The CONS filter name should be the same as the name being used for the X25 Access filter. If it is not, you will not be able to make any CONS connections.
For the network services CLNS, CONS, and RFC 1006, the following prompts are displayed:
* Allow use of expedited data? [YES] : |
If you want to support the use of expedited data, answer YES.
* Allow use of Checksums? [YES] : |
If you want to use the error correction feature, answer YES.
1.5.3.3 RFC 1006 Network Service
If you select the network service RFC 1006, you will see the following prompt:
* Local RFC1006 port number? [102] : |
Enter the outgoing port number to use when establishing a transport connection at the TCP level. For pure RFC 1006, use 102 as the port number. If you want to use DECnet over TCP/IP, use 399 as the port number.
If the RFC 1006 template is used for inbound packets, you will see the following prompt:
* RFC1006 listener port number? [102] : |
Enter the incoming port number to use when establishing a transport connection at the TCP level. This number must be the same as the local RFC 1006 port number for the template to be used for inbound traffic.
* Do you want to create additional OSI templates? [NO] : |
This prompt allows you to create additional customized OSI templates. If you answer YES to this prompt, the template questions are repeated. If you answer NO, the procedure proceeds to the Event Dispatcher question.
For more information on configuring DECnet-Plus over TCP/IP, and the
OSI applications over TCP/IP, refer to Section B.5.1.
1.6 Configuring an Event Dispatcher
The Event Dispatcher is a utility to receive and display event messages. You can either take the default Event Dispatcher configuration, or you can choose to customize the Event Dispatcher configuration.
* Do you want to customize the Event Dispatcher? [NO] : |
Answer YES if you want to customize the Event Dispatcher configuration. Answer NO if you want the default Event Dispatcher configuration only.
If you answer YES, the procedure displays prompts that allow you to customize the Event Dispatcher. The specific prompts are listed and explained in Section 3.8.
If you answer NO, the procedure displays:
%NET$CONFIGURE-I-EVDDEFAULT, providing default Event Dispatcher configuration |
If you chose the default Event Dispatcher configuration, 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.
* Display the events logged to the console of this machine? [YES] : |
| Previous | Next | Contents | Index |