Understanding DECnet-Plus for OpenVMS Networking
Software
DECnet-Plus
for OpenVMS provides the means for various HP operating
systems to communicate with each other and with systems provided
by other vendors. The DECnet-Plus network supports remote system communication,
resource sharing, and distributed processing. Network users can
access resources on any system in the network. Each system participating
in the network is known as a network node.
DECnet-Plus is the implementation of the fifth phase of the
Digital Netowrk Architecture (DNA). DNA Phase V integrates the OSI
protocols with DECnet protocols. In addition, DECnet-Plus includes
support for the Internet standard RFC 1006 and the Internet draft
RFC 1859, allowing OSI and DECnet applications to run over TCP/IP.
Thus, using DECnet-Plus, applications can communicate with peer
OSI and DECnet applications on any DECnet Phase IV-based system
or OSI-based system, whether from HP or from other vendors.
The
support of the non-proprietary protocols is the primary difference
between DECnet (Phase IV) and DECnet-Plus.
DECnet-Plus provides many features designed to enhance networking
capabilities. These features include:
Global name/directory services that
allow large networks to easily store, manage, and access addressing information
for (potentially) millions of network objects, such as end systems,
users, printers, files, and disks.
Optional local name/directory services for smaller
networks that do not have as critical a need for global directory
services.
Expanded network management capabilities with the
Network Control Language (NCL).
Host-based routing that allows an OpenVMS system
to operate as a DECnet-Plus intermediate system in a routing domain. This feature is especially useful for those configurations
where you need to route from a LAN to a WAN and want to use an existing
system to do the routing rather than investing in a dedicated router. Host-based
routing is not intended for use in network configurations that have
high-throughput requirements.
Increased addressing capacity with the OSI standard
address format, making possible unique addressing for virtually
an unlimited number of nodes. Existing Phase IV addresses can continue
to be used for systems upgraded to DECnet-Plus. The Phase IV address
is automatically converted by the configuration procedure to the
OSI address format (as a DECnet Phase IV compatible address).
Address autoconfiguration that enables an adjacent
router to configure the node address for the local node.
Single configuration for OSI components. X.25 (on VAX systems), wide area device drivers (WANDD), File
Transfer, Access, and Management (FTAM), and Virtual Terminal (VT)
applications are included with DECnet-Plus software. (On Alpha or I64
systems, X.25 support is separate from DECnet-Plus software.)
DECnet-Plus Node Names Naming conventions
for DECnet node names correspond to the two types of DECnet functionality:
DECnet-Plus full names Full names are hierarchically structured
DECnet node names that can be stored in a DECdns name service. Full
names can be a maximum of 255 bytes long.
DECnet Phase IV node names, called node synonyms
in DECnet-Plus These names are the shorter names used by DECnet Phase IV,
restricted to six or fewer characters. Using these names enables
DECnet-Plus to be backward compatible with DECnet Phase IV systems
in the same network.
Full names have the following
general syntax: namespace:.directory ... .directory.node-name
where:
namespace
Identifies the global name
service
directory
... .directory
Defines the hierarchical
directory path within the name service
node-name
Is the specific object defining the DECnet
node
The following examples show node full names for the Local
namespace, DECdns, and DNS/BIND, respectively:
Local namespace - LOCAL:.CPlace
DECdns - ACME:.warren.CPlace
Domain - CPlace.warren.acme.com
The system stores a full name as you enter it, preserving
uppercase and lowercase entries. However, when matching an entry
with a stored full name, the system is case insensitive; in other
words, if the user enters Acme, the system recognizes it as equivalent
to ACME.
For more information about full names, refer to the DECnet-Plus
documentation.
Support for OpenVMS Cluster Systems DECnet-Plus software supports OpenVMS Cluster systems and
the use of cluster aliases. DECnet-Plus allows for three aliases
for each OpenVMS Cluster. DECnet Phase IV nodes cannot be DECnet-Plus
alias members. (A separate alias must be configured for use with
DECnet Phase IV nodes.)
The CLUSTER_CONFIG.COM command procedure performs an OpenVMS
Cluster configuration. It can configure all members of a cluster
from any cluster member. It 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 configure an OpenVMS Cluster. Use NET$CONFIGURE.COM directly
to configure additional DECnet-Plus satellite nodes once CLUSTER_CONFIG.COM
has already been used.
DECnet-Plus Management Tools and Utilities DECnet-Plus for OpenVMS provides a variety of network tools
that let you perform the following tasks:
Manage local and remote DECnet Phase
V components. Two interfaces are available: the Network Control
Language (NCL) command-line interface and a Motif-based windows
interface (NET$MGMT.) HP supplies the DECNET_MIGRATE tool that converts
individual DECnet Phase IV NCP commands to NCL commands, and NCP
commands within command procedures to NCL commands. You can use DECNET_MIGRATE
when you are new to DECnet-Plus, learning NCL, and want help specifying familiar
NCP commands in NCL syntax.
Manage
remote DECnet Phase IV nodes with the NCP Emulator (NCP.EXE). This
utility supports a significant range of NCP commands. It is not
designed to replace NCL for managing a DECnet-Plus system.
Use DECnet-Plus for OpenVMS initialization scripts
(files in the form SYS$MANAGER:NET$*.NCL).
Perform maintenance operations (using MOP) such
as downline load, upline dump, remote console connection, and loopback
testing support. DECnet-Plus for OpenVMS provides enhanced support
and performance for concurrent downline loads. For more information
about MOP and how to start this process, refer to the DECnet-Plus
for OpenVMS Network Management guide.
Perform enhanced event logging using EVD.
Use Common Trace Facility (CTF) for troubleshooting.
Use the DECNET_REGISTER tool to assist in managing
node names in your network for the Local and DECdns namespaces.
HP OpenVMS System Manager's Manual, Volume 2:... 
Network Considerations
