HP OpenVMS Systems Documentation

If you want your system to communicate with Phase IV nodes, you must specify a Phase IV address and a Phase IV prefix. These will be used to construct a DECnet Phase IV-compatible address.

A DECnet Phase IV-compatible address is a DECnet-Plus address (NSAP) that conforms to the Phase IV area and node limits; that is, the area number is from 1 to 63, and the node number is from 1 to 1023.

If there are no Phase IV systems on your network or you do not want to communicate with Phase IV systems, you do not need a Phase IV-compatible address. Entering a Phase IV address of 0.0 at configuration time indicates that this DECnet-Plus system will not have a Phase IV-compatible address, and will not communicate with Phase IV nodes.

* Enter PhaseIV Address                              [15.27] :

Enter the Phase IV address you want to use, or enter 0.0 if you do not want to communicate with Phase IV nodes.

1.2.10 Specifying a Phase IV Prefix

The default value for the Phase IV prefix is 49:: which represents the private network initial domain part (IDP). This is appropriate for a Phase IV DECnet network that contains some DECnet-Plus systems. All nodes within a single addressing domain contain the same IDP in their network addresses.

If you are using a Phase IV prefix other than 49::, it must be assigned by an authorized standards organization, such as ANSI, or you must construct a Phase IV prefix that you know will be globally unique (based on your telephone number, for instance). If your organization has allocated its own Phase IV prefix, you can enter that value instead of 49::. The DECnet-Plus Planning Guide contains a detailed description of how to construct an IDP and how to apply to a standards organization for an IDP.

1.2.11 Specifying End Node Information

This section applies only if your DECnet-Plus system is an end node.

1.2.11.1 Configuring Network Addresses

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. You can assign up to three network addresses to your system.

Having multiple addresses allows you to have both a DECnet-Plus extended 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 you to belong to more than one OSI network. This feature is particularly useful when you want to combine two (or more) networks. Rather than assign new addresses to all systems in both networks to reflect the new combined network, those systems that participate in both networks can have an address in each one.

Network addresses are sometimes referred to in OSI terminology as network entity titles (NETs). NETs are network service access points (NSAPs) with a selector of 00. There are two ways to configure NETs: by autoconfiguring addresses or by manually configuring addresses.

Choice 1: Autoconfiguring Addresses

If you want to have your network address autoconfigured for you, answer YES to the following question during network configuration when using the net$configure tool:

* Autoconfigure network addresses?                     [YES] :

Choice 2: Manually Configuring Addresses

You can assign a maximum of three network addresses to the system including the Phase IV network address.

To create a 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

For more information on how to construct DNA and OSI NETs, see the chapter on NSAPs in the DECnet-Plus Planning Guide.

1.2.11.2 DNA Address Format

You have the option of setting the value of the routing characteristic "DNA Address Format" to either TRUE or FALSE.

* DNA Address Format                                  [TRUE] :

The DIGITAL Network Architecture (DNA) Address Format attribute controls the interpretation of address structuring. It does not control autoconfiguration. To control autoconfiguration, you need to use the Manual Network Entity Titles attribute by manually adding or removing NETs.

1.2.11.3 Segregated Mode Routing and Integrated Mode Routing

You have the option of using integrated mode routing or segregated mode routing. If you answer NO to this question, you will default to integrated mode.

* Do you want to use segregated mode routing?           [NO] :

Integrated mode routing works in the following way: It sends DECnet Phase IV messages across the network using DECnet Phase V Network layer protocols. Routers receiving DECnet Phase IV packets translate them to OSI CLNP format before forwarding them. Messages destined for DECnet Phase IV systems are translated to Phase IV format only on the last hop of their journey. Integrated mode routing allows routers to route both DECnet Phase IV and Phase V traffic while storing a single network topology in their internal databases.

Under integrated mode, DECnet-Plus systems attempt to send packets in DECnet Phase V format unless one of the following is true:

• They are communicating directly to an adjacent DECnet Phase IV system.
• No DECnet Phase V routers exist on the network to forward the packets.

Integrated mode routing is the only mode supported on OpenVMS systems preceding DECnet/OSI for OpenVMS Version 6.0.

Segregated mode routing handles DECnet Phase IV and Phase V as independent protocols. Routers do not translate messages between DECnet Phase IV and Phase V formats. The routers must maintain separate network topologies in their internal databases to handle each type of protocol.

Under segregated mode, DECnet-Plus end systems transmit messages in the Phase IV address format if they have a DECnet Phase IV translatable destination address. All other messages are sent in DECnet Phase V format. If you use non-DIGITAL routers that do not support DIGITAL's technique of translating DECnet Phase V addresses to DECnet Phase IV, you may want to use segregated mode routing.

On OpenVMS systems, integrated mode is the default routing mode. Use integrated routing mode in an integrated routing environment where the routers can handle Phase-IV-to-Phase-V or Phase-V-to-Phase-IV packet format conversions. Use segregated routing mode when the adjacent router(s) cannot perform Phase-IV-to-Phase-V or Phase-V-to-Phase-IV packet conversions.

The default ESHello Timer attribute determines the interval, in seconds, when the end system (ES) sends out its hello. This interval multiplied by 3 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.

* Routing default ESHello Timer?                        [600] :

To select the default of 600, press Return. Otherwise, choose your own value and press Return.

1.3 Configuring Devices

The net$configure procedure checks for network devices on the system that are supported by net$configure and then configures them. If the procedure finds that you have WANDD or X.25 installed but not configured, you will see the following information:

You have installed wide area device support, but it has not been
configured.  You may configure it now if you want.

* Do you want to configure Wide Area devices?          [YES] : N
%NET$CONFIGURE-I-SCANCONFIG, scanning device configuration - please wait

Answer YES if you want to configure WANDD.

If you have installed and configured WANDD software on this system, you have the option of configuring it to support asynchronous connections.

* Do you want asynchronous datalink support?            [NO] :

For more information on configuring asynchronous connections, see Appendix A.

1.3.2 Configuring Data Links and Routing Circuits

You now need to supply names for the data links and routing circuits you have on your system. Specify the simple name that you want to use for each data link and routing circuit.

* Data Link name to use for ESA0 (DESVA)?         [CSMACD-0] :
* Routing Circuit Name for Data Link 'CSMACD-0'?  [CSMACD-0] :

The following applies only if your DECnet-Plus is a routing node.

For each data link and routing circuit pair entered, specify the circuit cost and router priority at level 1. If your node is also a level 2 router, you will be asked for level 2 cost and router priority.

Cost indicates the cost of traffic on a particular circuit. Priority refers to the priority for becoming a designated router on a LAN at level 1 or level 2.

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

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

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

If you have an FDDI-type circuit on your system, you have the option of enabling FDDI large packet support. (A large packet is 4 KB in size, where an Ethernet packet is 1500 bytes in size.) FDDI large packet support allows you to fully use the bandwidth of FDDI. (A DECnet-Plus router on the LAN, preferably on the FDDI, is required to enable large packet support.)

If you choose not to enable FDDI large packet support on the system, the FDDI circuit uses the bandwidth of Carrier Sense, Multiple Access with Collision Detection (CSMA-CD) instead.

If there is an FDDI-type circuit on the system, the procedure displays the following message:

An FDDI-type circuit has been found on the system.  You have the
option of enabling FDDI large packet support on the system.  Note
that a DECnet-Plus router on the LAN (preferably on the FDDI) is
required in order to use FDDI large packet support.

* Enable FDDI large packet support?                     [NO] :

If you want to enable FDDI large packet support, answer YES.

1.3.5 Configuring an Alpha System

1. For an Alpha system, the procedure displays the following information:

   DEC X.25 software has been installed on this system. You have the option of configuring DECnet to run over X.25. * Do you want to configure DECnet over X.25? [NO] :

   
   Answer YES if you want to configure DECnet over X.25.
   If you answer YES, you will see a list of choices for the type of X.25 circuit to use:

   Types of X.25 circuits: [1] - X.25 Dynamic Assigned (DA) [2] - X.25 Static Incoming (IN) [3] - X.25 Static Outgoing (OUT) [4] - X.25 Permanent (PVC) * Which type of X.25 circuit do you want to use? : 4

   
   This prompt allows you to select the type of routing circuit you want to use over X.25. The menu offers four choices:
   • A dynamically assigned routing circuit (menu option 1) operates over a number of X.25 switched virtual circuits (SVCs), both incoming and outgoing.
   • A static incoming routing circuit (menu option 2) operates over a single incoming X.25 switched virtual circuit (SVC).
   • A static outgoing routing circuit (menu option 3) operates over a single outgoing X.25 switched virtual circuit (SVC).
   • A permanent routing circuit (menu option 4) uses a permanent virtual circuit (PVC) instead of an SVC.
   
   Enter the number for the type of circuit you want.
2. The procedure then asks for information about the routing circuit.

   * Routing Circuit Name to use? [X25-PVC-0] :

   
   Specify the simple name you want to use for the routing circuit. You can use the default or you can supply a name (for example, X25-PSI-0).
3. The procedure then asks for a template name to use for the circuit you just specified.

   * Template name? [X25-PVC-0] :

   
   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 (OUT) circuit, the X25 Access template must specify DTE class, destination DTE address, and call data. The X25 Access template can also specify other call characteristics to make the outbound network connection.
   • For a static incoming (IN) routing circuit, the X25 Access template can specify call characteristics to accept the inbound network connection.
   • For a dynamically assigned (DA) routing circuit, the X25 Access template must specify DTE class and call data. The X25 Access template can also specify other call characteristics to make the outbound or accept the inbound network connections.
   
   Use the X.25 configuration program to configure X25 Access templates.
4. If you chose to configure an X.25 dynamically assigned (DA) circuit or an X.25 static incoming (IN) circuit, the procedure asks for a filter name.

   * Filter name? [X25-DA-0] :

   
   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 dynamically assigned circuit, the X25 Access filter must specify inbound DTE class, call data value, and call data mask.
   Use the X.25 configuration program to configure X25 Access filters.
5. If you choose to configure an X.25 dynamic assigned (DA) circuit, the procedure displays this prompt:

   * Do you want to configure any reachable addresses? [NO] :

   
   If you answer NO, the procedure skips to the question, "Configure another PSI routing circuit for DECnet?".
   If you want to configure any reachable address subentities, answer YES. The procedure displays the following prompt:

   * Reachable address name? :

   
   Specify the simple name of the reachable address subentity that you want to create (for example, ACCOUNTS_DEPT).
6. The procedure then asks for the reachable address prefix:

   * Reachable address prefix :

   
   The reachable address subentity 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 subentity that has an address prefix matching 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 matches all NSAPs.
7. The procedure then prompts for the reachable address data terminal equipment (DTE) list:

   * Reachable address dte list? :

   
   You can configure a reachable address subentity 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).
8. The procedure then prompts for additional reachable addresses:

   * Any more reachable addresses you wish to configure? [NO] :

   
   If you want to configure another reachable address subentity for this circuit, answer YES.
9. When you have entered the circuit, template, and filter names and you have specified the appropriate reachable address information, the procedure asks if you want to configure any other circuits.

   * Configure another PSI routing circuit for DECnet? [NO] :

   
   If you do not want to configure any other PSI routing circuits, press Return for the default ([NO]). The configuration procedure continues with the next series of questions (such as FDDI large packet support or transports, for example).
10. If no devices are found on the Alpha system, the procedure displays the following prompt:

    * Should a SYSMAN IO AUTO be executed? :

    
    If you answer YES, the net$configure procedure invokes the SYSMAN IO AUTO command to find devices on the system. If you answer NO, there are no devices to configure.