![[Digital logo]](../../IMAGES/DIGITAL-LOGO.GIF){kind=logo}
![[HR]](../../IMAGES/REDBAR.GIF)
A DECnet-Plus network can use one name service exclusively, or it can have a mixture of systems using one or more of the name services. While configuring DECnet-Plus, you specify one or more of the three available name services to use on the node. To determine which name service(s) to use, check which name services are already being used by other nodes in your network. For example, if the other nodes in your network are already using DECdns, you will most likely want to use DECdns and join the existing namespace. The following sections include additional criteria and dependencies on the name services.
Choose the Local namespace if you have a small network and do not wish to use a distributed namespace. The Local namespace is similar to the permanent node database (NETNODE_REMOTE.DAT), used on DECnet Phase IV systems. With the Local namespace, name-to-address mapping information has to be administered separately on each node. To use the Local namespace, no additional software is required.
With DECdns, all node names in the network can be administered from one location. The mapping information is stored on two or more DECdns servers and kept up-to-date networkwide automatically. DECnet-Plus requires at least two DECdns servers in the network. DECdns server software must be installed and configured on these systems (the server software is optional software included with the DECnet-Plus for OpenVMS software kit). The DECnet-Plus Planning Guide describes planning considerations and the DECnet-Plus for OpenVMS Applications Installation and Advanced Configuration and DECnet-Plus DECdns Management guides include installation and configuration instructions.
DNS/BIND, the distributed name service for TCP/IP, supports the storage of IP addresses and the use of node synonyms. Node synonyms allow for backward compatibility with older applications that cannot use long domain names. (Note that DECnet-Plus also allows for node synonyms to provide backward compatibility with DECnet Phase IV node names.) DNS/BIND is needed if you want DECnet-Plus to run applications over TCP/IP. To use the DNS/BIND name service, DECnet-Plus requires one or more DNS/BIND servers in the network. DNS/BIND must be selected as one of the name services if you plan to use the DECnet over TCP/IP or OSI over TCP/IP features. See the appropriate TCP/IP documentation for more information on DNS/BIND.
The Digital Distributed Time Service (DECdts) synchronizes the system clocks in computers connected by a network. The DECnet-Plus for OpenVMS configuration procedure autoconfigures the DECdts clerk. If your network uses multiple DECdns servers, or if you need network clock sychronization, Digital recommends that you install at least three DECdts servers on each LAN. See the DECnet-Plus DECdts Management guide for more information.
In large networks and networks requiring high throughput, one or more dedicated routers are recommended for the network. Digital recommends using host-based routers to replace DECnet Phase IV host-based routers or in environments not requiring high throughput.
The DECnet-Plus for OpenVMS VAX systems license includes the right to use X.25 Access software (formerly known as VAX P.S.I. Access) or X.25 Native mode software (formerly known as VAX P.S.I.), which requires an additional license.
The X.25 software in DECnet-Plus for OpenVMS is backwards compatible with systems running the older VAX P.S.I. products. For further information on X.25, refer to Chapters 2 and 4.
On DECnet-Plus for OpenVMS Alpha systems, the following licenses are required:
To develop OSI applications, you need to use the OSI application development interfaces (API) installed with the base system. These tools allow you to build network applications that adhere to the OSI standards defined by the International Organization for Standardization (ISO).
You can use the following components in building OSI applications:
Where ISO standards exist, the APIs conform to these standards.
The following table shows the components available on Digital UNIX and OpenVMS platforms.
| Operating System | Components |
|---|---|
| Digital UNIX | FTAM, OSAK (Presentation and ACSE) |
| OpenVMS | FTAM, OSAK (Presentation and ACSE), ROSE (VAX only) |
A DECnet-Plus network can be viewed as a distributed processing system. The major functions of the network, such as network management and routing, are not centralized in a single system. Each system can manage both itself and remote systems. Adaptive routing eliminates the need to set up network data paths.
Some of the primary features of the DECnet-Plus distributed network are:
Networkwide capabilities include the optional use of distributed system services designed to make the network as transparent as possible to users and applications. The DECnet-Plus distributed computing environment provides the following services:
In the DECnet-Plus distributed processing environment, you can physically distribute multiple resources or tasks that perform various functions between systems on the network.
A distributed application is a collection of processes that use resources, such as processing elements, databases, and physical devices, located on other systems in the network. As a single logical application, the elements or tasks are physically divided. A task is a modular component of work that the application programmer defines within an application. The work of a distributed application is divided among tasks that can communicate with each other.
In an OpenVMS operating system, a task is executed within the context of a process. The process context defines the environment in which the task executes. OpenVMS software controls the access and allocates the resources required by the task, based on the process context.
In a distributed application, each task is distinct and can be placed in different locations in the network. The system interface for the application allows you to run the application locally or remotely without any apparent difference.
You can distribute an application so that each task is assigned to a system with appropriate resources. For instance, one task computes on a powerful processor while another stores the information in a database on a system with extensive disk storage capabilities. A common example of a distributed application is an implementation of the client/server model, such as DECdns, in which the client task (on the DECdns clerk system) requests service from the server task on a different system (the DECdns server).
Interprocess communication is the movement of data and control from one task running within a process to another task in the network. Interprocess communication allows the various tasks on the different processes to cooperate and communicate with each other, exchanging message packets over the connection established between the tasks.
Distributed applications can increase availability. You can design a distributed application to avoid a single point of failure by moving tasks to other processors if a processor fails. Other benefits of distributed applications include:
An OpenVMS cluster configuration is an organization of OpenVMS operating systems that communicate over a high-speed communications path and share processor resources as well as disk storage. DECnet connections are required for certain OpenVMS cluster tools and configurations. DECnet-Plus for OpenVMS software provides support for OpenVMS cluster systems.
DECnet-Plus for OpenVMS supports the use of multiple cluster aliases. The alias node identifier (a node name or node address) is common to some or all nodes in the cluster and permits users to address it as though it were one node.
For management purposes, the cluster alias is viewed by the DECnet-Plus software as a separate Node entity that is manageable through NCL commands. The Alias entity differs from a regular Node entity in some characteristics; for example, the Alias entity does not support a Circuit entity. The cluster alias appears to the network as a multicircuit end node, which is an end node with several active circuits. In an OpenVMS cluster system that consists of DECnet-Plus for OpenVMS systems on a LAN, the alias node appears as an end node with multiple points for attachment to the LAN.
DECnet-Plus for OpenVMS supports the ability to access nodes in an OpenVMS cluster using a separate alias node address, while retaining the ability to address each node in the cluster individually. Not all network objects may be accessed using this mechanism. The maximum number of nodes supported for a cluster alias is 96. The maximum number of cluster aliases for a single node is three.
The cluster_config.com command procedure for performing a OpenVMS cluster configuration invokes the DECnet-Plus for OpenVMS net$configure.com command procedure to perform any required modifications to NCL initialization scripts. Use cluster_config.com to create a configuration for each satellite node in the cluster.
DECnet-Plus for OpenVMS is an implementation of Phase V of the Digital Network Architecture (DNA) for the OpenVMS operating system.
DECnet-Plus integrates DECnet and OSI network protocols allowing both stacks to share integrated network functions up to the Transport layer. Upper layers have been implemented as separate "towers," allowing existing DECnet and OSI applications to share the integrated Transport layer. Existing DECnet Phase IV and new DECnet and OSI applications are supported by DECnet-Plus. In combination with TCP/IP protocol stacks, OpenVMS systems can participate in multivendor, multiprotocol networks adhering to Open Networking standards.
For details on specific upgrades and enhancements, refer to the DECnet-Plus for OpenVMS Release Notes.
Refer to Figure 2-1, which illustrates the integrated DNA Phase V Reference Model.
Figure 2-1 DNA Phase V DECnet-Plus for OpenVMS
DECnet-Plus for OpenVMS offers task-to-task communications, file management, and downline system and task loading. Network WAN connectivity is provided by WAN device drivers supporting host-based synchronous communications options for wide area networking.
DECnet-Plus for OpenVMS is available in two forms: End System and Extended Function. Extended Function provides all the features of End System plus the OSI application gateways (FTAM--DAP Gateway, VT-Telnet, LAT/VT and VT/LAT), the DECdns server (on VAX platforms), and host-based routing, and cluster alias.
The functions offered by OpenVMS are split into separate components. The entire base system installs automatically when you start the installation procedure, while the additional components are optionally installable. To support open, standards-based, multiprotocol communications, DECnet-Plus for OpenVMS is comprised of the DECnet-Plus base system (including DECdns and DECdts clerk software), and the following optional software:
Table 2-1 lists the functions of DECnet-Plus for OpenVMS matched with the specific software components that you need to install and/or configure during the DECnet-Plus for OpenVMS installation procedure. Other dependencies are also noted.
The DECnet-Plus for OpenVMS base system software allows an OpenVMS system to perform as both a DECnet end node and an OSI end system. It can communicate using ISO 8802-3 (CSMA-CD) or ISO 8802-5 (FDDI) broadcast lines, either Digital Data Communications Message Protocol (DDCMP) or point-to-point through HDLC lines.
The DECnet-Plus base software offers the following features:
The DECnet over TCP/IP feature allows users to run standard DECnet applications in an Internet Protocol (IP) routing environment.
When you are running DECnet over TCP/IP, you can connect using an IP address, for example:
$ set host node.site.company.com
The connection is made using the DNA CTERM application instead of the TCP application FTP. Note that both the source and target nodes must support DECnet over TCP/IP for this connection to work. The system can be configured to allow you to use synonyms (Phase IV-style names) instead of the IP host full name. If a system does not run DECnet and support DECnet over TCP/IP, you need to use COPY/FTP to access that system. For example:
$ COPY/FTP myfile *
For more information on running DECnet over TCP/IP, refer to the DECnet-Plus Network Management and the installation and configuration guides. This feature requires any valid DECnet license and a licensed and installed TCP/IP product that supports the PATHWORKS Internet Protocol (PWIP) interface.
A DECnet Phase IV "object" in DECnet-Plus is called an application. The DECnet-Plus for OpenVMS base system supplies the following session control applications, which are defined automatically at network startup:
The DECnet-Plus for OpenVMS base system offers the following programming interfaces.
A DECnet-Plus for OpenVMS system functions as an OSI end node if, during configuration, you configure OSI Transport. An application can set up a transport connection to another application on any other system, either Digital or multivendor, running software that implements the OSI Transport Protocol.
DECnet-Plus for OpenVMS software includes the Network Services Protocol (NSP) for DECnet Phase IV compatibility. You can use the proprietary NSP and the open OSI Transport Protocols simultaneously.
The ISO End-System-to-Intermediate-System (ES-IS) Routing Exchange Protocol provides the process by which end systems communicate with intermediate systems (routers), or with each other, to exchange configuration information.
INTRO_PROFILE_001.HTML OSSG Documentation 2-DEC-1996 12:54:18.00
Copyright © Digital Equipment Corporation 1996. All Rights Reserved.