HP OpenVMS Systems Documentation
DECnet-Plus for OpenVMS
An OSI administrative domain consists of a combination of end systems, intermediate systems, and subnetworks. You can also subdivide the administrative domain into routing domains, in which all systems and subnetworks use the same routing protocols.
The Network layer complies with the ISO standards for network packet formats and addressing. Data messages are forwarded through the network in self-contained packets that include the source and destination addresses.
DECnet-Plus for OpenVMS systems support the packet format that is specified in ISO standard 8473, and can exchange data with other vendors' systems that also conform to the ISO packet format standard.
The Network layer accepts messages from the Transport layer and encloses them in packets called network protocol data units (NPDUs). The NPDU includes the Network layer header that contains the source and destination addresses for the data. The Network layer address for a system is called the network service access point (NSAP). The NSAP is located at the boundary between the Network layer and the Transport layer, where communication between the layers takes place. For complete information about NSAPs, see the DECnet-Plus Planning Guide.
The Network layer uses the destination NSAP address to forward the
NPDUs to the destination system. The Network layer also provides
compatibility with Phase IV.
3.8 Data Link Layer
The Data Link layer provides a communications path between directly connected systems in a network. It controls the movement of information between systems, including the transmission and receipt of data. In providing delivery of data to the adjacent node, the Data Link layer performs some or all of the following functions: establishment of the link (initializing and conditioning the line), error detection and recovery, data flow control, data framing control, and packet sequence control.
DECnet-Plus for OpenVMS uses synchronous, asynchronous (VAX only), Ethernet, and FDDI communications controllers to interface with other network nodes.
LAN connectivity is provided by the CSMA-CD and FDDI controllers and drivers supporting ISO 8802-2 logical link control (LLC) type 1 connectionless service and ISO 8802-3 LLC type 2. DECnet-Plus also supports Ethernet V2 packets on CSMA-CD devices.
Use of FDDI packets larger than 1500 bytes requires a Phase V router on the FDDI LAN. As with cluster alias support, the Phase V router may be configured to run the Phase IV distance vector routing protocol or the Phase V Link State Routing Protocol.
WAN connectivity is provided by WAN device drivers supporting host-based synchronous communications options for wide area networking.
All the data link devices support DDCMP, HDLC/LAPB and SDLC protocols. BISYNC and GENBYTE (VAX only) protocols are also supported on some options. WAN device drivers are required by X.25 to establish host-based wide area connections.
Synchronous controllers use DDCMP or HDLC, either when directly connected or when connected via modems, to provide full- or half-duplex communications over point-to-point lines. Synchronous DDCMP multipoint tributary connections are also supported. Asynchronous controllers (on VAX systems) use DDCMP, either when directly connected or when connected via modems, to provide only full-duplex communications over point-to-point lines. Error correcting and data suppression modems are not supported.
Asynchronous lines (on VAX systems) are supported only to other systems running DECnet-Plus for OpenVMS VAX, DECnet-VAX, DECnet-RSX, and DECnet-DOS.
DDCMP operation (on VAX systems) is not supported in cases where an asynchronous physical communications line is emulated by lower-level protocols or communications subsystems. Examples of this include X.29 virtual terminals, asynchronous connections as emulated by terminal servers, and connections via data switches.
DECnet-Plus for OpenVMS allows up to four circuits to be defined and
operational on an end system. This capability allows a single end
system to be connected to up to four separate LANs or WANs. Note that
all circuits must be equal in capacity and connectivity.
3.8.1 Support for CSMA-CD Protocol on a LAN
The Data Link layer allows the transmission of data over a local area network cable by means of the CSMA-CD (Carrier Sense Multiple Access with Collision Detection) protocol. CSMA-CD ensures equal access to multiple systems connected to the LAN. DECnet-Plus for OpenVMS supports both the existing Ethernet protocol and the protocol that complies with ISO 8802 (also known as IEEE 802).
The Ethernet and ISO 8802 protocols are compatible, with only slight differences in packet format. A DECnet-Plus system transmits in both ISO and Ethernet formats, and listens for frames in ISO and Ethernet formats. If a Phase IV system is connected to the LAN, the DECnet-Plus system also transmits in Ethernet format.
CSMA-CD LANs are similar to LANs defined by ISO 8802-3. LANs are privately owned, reliable, high-speed networks that connect information-processing systems in a limited geographic area, such as an office, a building, or a complex of buildings. It is a best-effort delivery system.
CSMA-CD allows multiple stations to access the broadcast channel at will, avoids contention by means of carrier sense and deference, and resolves contention by means of collision detection and retransmission. Each station awaits an idle channel before transmitting and can detect overlapping transmissions by other stations.
CSMA-CD stations provide for multiaccess connection between a number of systems on the same broadcast circuit. This kind of routing circuit is a path to many systems. Each system on one CSMA-CD station is considered adjacent to every other system on that station and equally accessible.
The media is passive coaxial cable or shielded twisted-pair cable that uses Manchester-encoded, digital baseband signaling, with interconnections containing all active components so that no switching logic or central computer is needed to establish or control communications.
At the Data Link layer, network control for the LAN is multiaccess, fairly distributed to all systems. The frame length allocation is from 64 to 1518 bytes (including an 18-byte envelope).
A system on an ISO 8802-3 (CSMA-CD) LAN is connected to the CSMA-CD station by:
When manufactured, LAN controllers are given a 48-bit hardware address.
A particular ISO 8802-3 system is identified by the hardware address of its station (line); this hardware address is stored in read-only memory in the LAN controller. When DECnet-Plus starts a CSMA-CD station, it constructs a physical address for the system. When you shut off machine power or change the state of the CSMA-CD station to off, the LAN controller resets the physical address to the original hardware address.
DECnet-Plus has no restrictions on the number of end systems on a LAN. In addition, you do not need an intermediate system on a CSMA-CD LAN.
ISO 8802-3 (CSMA-CD) LANs support a bus topology, a single
communications medium to which all the systems are attached as equals.
The single network cable replaces the numerous interconnecting cables
usually required in traditional WANs. This type of network is also
called a broadcast LAN. The maximum possible distance
between systems on the LAN is 2.8 kilometers (1.74 miles).
184.108.40.206 Extended LANs
You can connect segments of coaxial cable to extend LANs beyond the 500-meter (1640 feet) limit of a single segment. Extended LANs create larger networks in terms of distance and also in terms of the number of connections that can be made. (A 500-meter segment supports 100 physical connections.) Repeaters and bridges join cable segments:
If the end systems communicate only with each other, you do not need an intermediate system on a LAN, but can use host-based routing. Optionally, you can use one to limit multicast traffic. To route messages off the LAN over other routing circuits, you must configure an intermediate system such as DDCMP circuits.
If a LAN is operating with more than one area and with one or more
level 1 intermediate systems, you need a level 2 intermediate system to
transport messages between areas.
220.127.116.11 Multicircuit End Systems
DECnet-Plus for OpenVMS allows multiple circuits to be active and
usable simultaneously on an end system. For example, you can connect an
end system to two LAN cables. Both routing circuits are used and
traffic is split between the circuits, but no routing occurs over these
circuits. A DECnet-Plus for OpenVMS end system can support a maximum of
three circuits. This feature provides for redundancy and increased data
throughput without requiring an intermediate system.
18.104.22.168 Areas and Multihomed Systems
You can partition a large DECnet-Plus routing domain into subdomains called areas. For Phase IV, an area is a group of network nodes that can run independently, with all nodes in the group having the same area address. DECnet-Plus areas are similar to Phase IV areas except for the following new features:
A node can be in only one area in a network. DECnet-Plus systems, however, can have more than one area address. Such a system is a multihomed system. You can assign up to three area addresses to a DECnet-Plus system.
A DECnet-Plus area is a set of systems that all share the same area address (or addresses). An area (and the systems within the area) can have more than one area address. For example, if an area in a DECnet-Plus network is connected to an X.25 public network, a system in that area of the network would have two addresses: one for the DECnet-Plus network and one for the X.25 network. A system cannot have addresses on two networks that are not connected.
If you connect two areas to a DECnet-Plus LAN, the level 2 intermediate
systems automatically combine themselves into one area with two area
addresses. Phase IV LANs can be divided into several areas. Mixed Phase
IV and DECnet-Plus LANs can also include several areas.
3.8.2 Support for the HDLC Protocol
High-level Data Link Control (HDLC) protocol data links are ISO, synchronous, point-to-point links that are basically the same in function as existing DDCMP synchronous links. However, HDLC is a bit-oriented protocol, whereas DDCMP is a byte-oriented protocol.
HDLC operates over synchronous, switched, or nonswitched communications links. HDLC supports a broad range of existing subsets, including the subset used in X.25 networks.
HDLC operates in either of two modes:
HDLC links use UI frames and XID frames. A UI frame is an unnumbered,
information frame that carries data not subject to flow control or
error recovery. An XID frame exchanges operational parameters between
22.214.171.124 LAPB Support
DECnet-Plus for OpenVMS also supports a modified form of HDLC called
link access protocol balanced (LAPB). LAPB is the CCITT-approved link
level protocol for X.25 connections. LAPB defines the procedure for
link control in which the DTE/DCE interface is defined as operating in
two-way asynchronous balanced mode (ABM). LAPB is for the reliable
transfer of a packet from a host to an X.25 packet switch, which then
forwards the packet on to its destination.
3.8.3 Support for the DDCMP Protocol
DDCMP is designed to provide an error-free communications path between adjacent systems. It operates over serial lines, delimits frames by a special character, and includes checksums at the link level.
DECnet-Plus for OpenVMS continues to support proprietary DDCMP data links, which include these types of connections:
DDCMP provides a low-level communications path between systems. The protocol detects any bit errors that are introduced by the communications channel and requests retransmission of the block. The DDCMP module provides for framing, link management, and message exchange (data transfer). Framing involves synchronization of bytes and messages.
DDCMP pipelining permits several packets to be sent before an acknowledgment is received. Piggybacking permits an acknowledgment to be transmitted on a data packet.
The DDCMP protocol moves information blocks over an unreliable communication channel and guarantees delivery of routing messages. Individual systems on DDCMP routing circuits are addressed directly because no multicast or broadcast addressing capability is available.
The Data Link layer supports point-to-point, DDCMP links, either
synchronous or asynchronous. The two types of asynchronous links are
static (permanent) and dynamic
126.96.36.199 Synchronous DDCMP
Synchronous links provide the medium to high-speed point-to-point communication. The synchronous DDCMP Protocol can run in full- or half-duplex mode. This allows DDCMP the flexibility of being used for local synchronous communications or for remote synchronous communications over a telephone line using a modem.
DDCMP is implemented in the driver software (WANDD) for the synchronous
188.8.131.52 Asynchronous DDCMP
Asynchronous links provide a low-speed, low-cost media for point-to-point communication. Asynchronous DDCMP can run over any directly connected station that the DECnet-Plus for OpenVMS system supports. Asynchronous DDCMP provides for a full-duplex connection. You can use it for remote asynchronous communications over a telephone line using a modem. Asynchronous connections are not supported for maintenance operations or for controller loopback testing.
Asynchronous DDCMP does not need to be predefined for dynamic connections. It is established automatically when a dynamic asynchronous DDCMP link is made.
DECnet-Plus supports HDLC as an alternative to DDCMP to:
You can convert existing DDCMP point-to-point synchronous lines to HDLC lines. However, DECnet-Plus also supports DDCMP for compatibility and to provide these capabilities not available with HDLC:
The Physical layer is responsible for the transmission
and receipt of data on the physical media that connects systems. It
transparently moves data between the system and the communications path
signaling equipment. The Physical layer can include part of the device
driver for a communications device and for communications hardware:
interface devices, modems, and communication lines.
3.9.1 CSMA-CD LAN Interface
The Physical layer supports the CSMA-CD interface, which complies with
ISO standard 8802-3 and the IEEE 802.3 standard. The Physical layer
also allows CSMA-CD LAN connections based on the DECnet Phase IV
3.9.2 Modem Connect Module
The DECnet-Plus Modem Connect module defines the operation of synchronous and asynchronous devices. It provides for network management of stations (physical lines) that conform to industry standards for modem connection. You can establish and monitor the following types of links:
The Modem Connect module supports several industry standards for physical interfaces:
The Modem Connect module does not contain driver-specific code. It contains all the common routines related to network management for all synchronous and asynchronous drivers. The functions controlled through the Modem Connect module include:
DECnet-Plus for OpenVMS network management capabilities include:
The structure of DECnet-Plus network management defines formal relationships between the management software at the various layers and the directors that communicate with the layers on behalf of network managers.
The two major components of network management are directors and entities. Directors are interfaces for managing the entities. They are typically used by the network manager and usually involve a command language. NCL management entities, which are the manageable components that make up the network, relate to other entities on the same system.