Software Product Description ___________________________________________________________________ PRODUCT NAME: HP DECnet-Plus for OpenVMS Integrity servers Version 8.4 and OpenVMS Alpha Version 8.4 SPD 50.45.21 Description HP DECnet-Plus for OpenVMS is an implementation of Phase V of the DIG- ITAL Network Architecture (DNA) for the OpenVMS Alpha and Integrity servers operating system. HP DECnet-Plus integrates DECnet and Open Systems Interconnection (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 combi- nation with TCP/IP protocol stacks, OpenVMS systems can participate in multivendor, multiprotocol networks adhering to open networking stan- dards. HP DECnet-Plus for OpenVMS features include: o Support for OpenVMS LAN failover sets. LAN failover provides a mech- anism to protect LAN applications against network interface card (NIC) failures. A LAN failover set is defined by the system man- ager and consists of a set of like adapters (all the same class) that support LAN failover. One adapter in the failover set is used for LAN traffic; one or more other adapters in the set remain idle. If the active adapter fails, one of the idle adapters in the set automatically takes over LAN traffic using the same address as the failed adapter. o DECdns Server on Integrity server systems, Alpha systems, and VAX systems March 2010 o The ability to run DECnet and OSI applications over TCP/IP trans- ports. o Support for 64-bit addresses, allowing 64-bit network applications to take advantage of the P2 addressing of Alpha systems running Open- VMS Alpha Version 7.1 or later. Support for 64-bit addressing is limited to the DECnet-Plus $QIO interface. o Continued support for 32-bit network applications. o Host-based routing, which includes communication with nodes run- ning DECnet Phase IV and OSI protocols and FDDI large packets, and X.25 switched and permanent virtual circuits. o FAST configuration option, which allows quick configuration upgrades from Phase IV to Phase V. o X.25 network management interface, providing efficient wide area network (WAN) management. o The ability to configure all members of a cluster from any clus- ter member. o OSI application programming interfaces (APIs). o Expanded naming options, allowing one or more of the following di- rectory naming services: Local, DECdns, and/or DNS/BIND (referred to as Domain by DECnet-Plus software). These directory naming ser- vices can be searched in any order, as determined during config- uration of the product. o Routing segregated mode to allow the Routing layer to choose a Phase IV router for those packets having a Phase IV compatible address. (Packets having a Phase V extended address are sent to a Phase V router by default.) This is a configurable option. o Reverse path caching to capture path information for later use in reaching remote systems. o Increased network size, supported through the use of ISO OSI ad- dressing. o Simplified installation and configuration process. 2 o The Network Control Language (NCL). Network management is based on DNA CMIP, HP's implementation of the OSI international standard Com- mon Management Information Protocol. o A graphical network management user interface, net$mgmt, for im- proved network management, using NCL. o An NCP (Network Control Program) emulator to facilitate installa- tion of layered products written for DECnet Phase IV. o Installation using the POLYCENTER Software Installation utility. o Support for topologies using multicircuit and multihomed end nodes. o Dynamic connections over X.25 networks. HP DECnet-Plus for OpenVMS includes OSI implementation in accordance with current U.S. and U.K. GOSIP requirements: o Application, Presentation, and Session layers - File Transfer, Access, and Management (FTAM) application - Virtual Terminal application - Applicaton Service Elements (ASEs), including ACSE (Association Control Service Element) o Transport layer classes 0, 2, and 4 o Lower layers - OSI addressing formats, supporting large network topologies - End system to intermediate system (ES-IS) routing - Connectionless Mode Network Service (CLNS) over local area net- work (LAN) and wide area network (WAN) , and X.25 - Logical Link Control type 2 (LLC2) for Connection-Oriented Net- work Service (CONS) over LAN 3 - Data Link layer, supporting High-level Data Link Control (HDLC) for wide area communications (Alpha only), ISO 8802-3 (Ether- net CSMA/CD) and FDDI LANs. HDLC support includes the LAPB (Link Access Protocol Balanced) protocol for X.25 communications. For Version 8.2, HDLC is supported only on OpenVMS Alpha systems. - Physical layer, with CSMA/CD, HDLC (Alpha only), and FDDI de- vices supported. HP DECnet-Plus for OpenVMS offers task-to-task communications, file management, downline system and task loading, network command termi- nals, and network resource sharing capabilities using DNA, OSI, and TCP/IP protocols. DECnet-Plus for OpenVMS communicates with adjacent and non-adjacent DECnet Phase IV, Advanced Server/PATHWORKS, DECnet- Plus implementations on other OpenVMS systems and Tru64 UNIX systems, as well as systems running TCP/IP transports and on OSI-compliant sys- tems from other vendors. OpenVMS programs written in native-mode programming languages can use DECnet-Plus for OpenVMS capabilities. Depending on the system configuration, networks combining HP DECnet- Plus for OpenVMS systems with other DECnet, OSI, and TCP/IP products may limit the functions available if all products do not support equal features. Data Link Layer HP DECnet-Plus for OpenVMS uses Ethernet and FDDI communications con- trollers 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 con- nectionless service. HP DECnet-Plus also supports Ethernet Version 2 packet formats on CSMA/CD devices. 4 Use of FDDI packets larger than 1500 bytes requires a Phase V router on the FDDI LAN. The maximum Phase V FDDI packet size is 4352 bytes for use with other Phase V network nodes. As with cluster alias sup- port, you can configure the Phase V router to run the Phase IV dis- tance vector routing protocol or the Phase V link state routing pro- tocol. WAN connectivity is provided by optional X.25 software supporting host- based synchronous communications interfaces (Alpha-only). All the synchronous devices support DIGITAL-HDLC (Alpha-only) and LAPB/E (Alpha-only) and data link protocols. X.25 for OpenVMS Alpha is re- quired to establish host-based wide area connections. HP DECnet-Plus for OpenVMS allows a maximum of 32 circuits on a full routing node and up to four circuits 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. HP recommends that the circuits be equal in capacity and connectivity. The optional X.25 for OpenVMS software allows HP DECnet-Plus for Open- VMS systems to connect to PSDNs (packet switching data networks) con- forming to CCITT Recommendation X.25 (1980 or 1984) and/or ISO 7776 and 8208, or through an X.25 relay system directly connected to a PSDN, or through an X.25 connector node (X.25 gateway), or over TCP/IP us- ing RFC 1613 (XOT). The software allows process-to-process as well as terminal-to-process communications between Alpha systems and remote DTE (data terminal equipment) over a PSDN. The X.25 software provides the Connection-Oriented Network Service (CONS) to allow mapping between a destination NSAP address and a destination DTE address according to ISO 8348. Direct access to a PSDN (using the supported device drivers) requires an X.25 license. See the Optional Software section. For more details on the X.25 software for OpenVMS, refer to the X.25 for OpenVMS Alpha and Integrity systems Software Product Description (SPD 47.37.xx). 5 Network Layer HP DECnet-Plus for OpenVMS supports the Connectionless-Mode Network Service (CLNS) and the Connection-Oriented Network Service (CONS). Exchange of routing information between end systems and routers uses the ISO 9542 ES-IS routing protocol. This protocol allows DECnet-Plus systems to autoconfigure as end systems with ISO 9542-conformant routers. Addresses conform to the ISO 8348 Addendum 2 specification, allowing the support of large network topologies. As long as the system address stays within the addressing range of Phase IV systems (up to 1,023 sys- tems per area and up to 63 areas per network), and uses the same ini- tial domain part (IDP), you can use Phase IV or Phase V routers. The Network layer supports the capability of an end system to be mul- ticircuited and multihomed. Multicircuit support allows multiple cir- cuits to be active simultaneously. This functionality increases net- work reliability and data throughput. Multihomed end-system support allows a system to have up to three network entity titles. Segregated routing mode is a settable attribute. It directs routing to choose a Phase IV router for those packets having a destination ad- dress that can be translated to the Phase IV format. All other pack- ets are sent to a Phase V router, if available. The Routing layer is able to cache information about the paths that are used to reach remote nodes. Transport Layer HP DECnet-Plus for OpenVMS provides support for: o OSI Transport protocol as specified in ISO 8073 o RFC 1006 and RFC 1859 to allow OSI and DECnet applications to run over TCP/IP 6 o Network Services Protocol (NSP) NSP, RFC 1006, and OSI transports support communications between DEC- net, TCP/IP, and OSI systems. NSP provides backward compatibility with Phase IV DECnet systems. RFC 1859 support for DECnet applications is provided by a kernel in- terface that is implemented on all TCP/IP stacks available for use on the OpenVMS operating system. The supported applications include all licensed DECnet applications as well as layered products and user-written applications that conform to the documented DECnet programming inter- faces. RFC 1006 is a specification for running OSI applications over TCP/IP. Operation of the FTAM and Virtual Terminal application over a TCP/IP network is supported along with other layered OSI applications such as X.400 and X.500. A separate TCP/IP stack is required on the same system with DECnet- Plus. See the Optional Software section of this SPD for information on supported TCP/IP products. OSI transport supports transport classes 0, 2, and 4 on connection- oriented networks and class 4 on connectionless networks. OSI transport uses two types of network service: o The Connectionless-Mode Network Service (CLNS) using the Internet protocol (ISO 8473) and ES-IS protocol (ISO 9542) to communicate across linked subnetworks. o The Connection-Oriented Network Service (CONS). 7 Upper Layers HP DECnet-Plus for OpenVMS software provides the OSI upper layer stack consisting of Session, Presentation and Application layers. The Ap- plication layer provides Association Control Service Element (ACSE); File Transfer, Management, and Access (FTAM); and Virtual Terminal (VT). HP DECnet-Plus for OpenVMS also provides a range of DECnet applica- tions and services including file and record access, remote terminal access, mail, and phone. Applications Transport Options for Applications You can run applications written to the DECnet upper layers over NSP or TCP/IP transports using RFC 1859. This includes the network appli- cations that are licensed with DECnet-Plus as well as user-written ap- plications that adhere to the documented DECnet programming interfaces. You can run applications written to the OSI upper layers over OSI or TCP/IP transports using RFC 1006. Existing DECnet and OSI applications require no modification to run over TCP/IP using RFC 1859 and RFC 1006. Remote File Transfer HP DECnet-Plus for OpenVMS supports two upper layer protocols for re- mote file transfer: the OSI protocol's File Transfer, Access, and Man- agement (FTAM) and the DECnet Data Access Protocol (DAP). FTAM FTAM supports file transfer, access, and management between a DECnet- Plus for OpenVMS system and other systems with software adhering to ISO 8571. In addition, FTAM is conformant with NIST Phase II and Phase III agreements and is certified as being conformant to the released specifications of U.S. GOSIP, U.K. GOSIP, and ENV41204. 8 In addition, FTAM: o Provides users the ability to create, delete, rename, view, and copy files using DCL commands. o Is implemented as an Application Service Element (ASE) of the OSI Application layer. o Acts as the initiator or as the responder in a connection. o Accesses and transfers files with both binary and character data. It supports FTAM-1, FTAM-2, FTAM-3, and NBS-9 document types. HP DECnet-Plus for OpenVMS also supports gateway services between FTAM and DAP. A full description of the FTAM services in DECnet-Plus for OpenVMS is provided in Appendix A of this document. DAP The DECnet Data Access Protocol (DAP) supports task-to-task communi- cations, file and record access, and proxy access. Task-to-Task Communications: For most applications, you can use task- to-task communications in a transparent manner where the remote task is treated as a full-duplex, record-oriented device. Transparent op- eration is provided with the following interfaces: system service calls, RMS calls (OPEN, GET, PUT, and CLOSE), and high-level language I/O state- ments (which are mapped to RMS calls). A nontransparent mode of task- to-task communications is offered by means of the system service in- terface that extends the capabilities provided by the transparent mode. These capabilities include support for interrupt messages and multi- ple inbound connect requests. Using HP DECnet-Plus for OpenVMS, an OpenVMS program written in a na- tive mode programming language can exchange messages with other user programs. 9 File Access: File access is supported to and from remote DECnet-Plus for OpenVMS systems, transparent to native mode high-level language programs using RMS. User programs can sequentially read, create, and delete files on a remote node. Record Access: User programs can perform record level operations such as GET, PUT, UPDATE, DELETE, FIND, and REWIND to access and modify files residing on a remote OpenVMS node. In addition to sequential access to a file, several other access methods are supported through RMS us- ing DECnet-Plus for OpenVMS. These methods include random access by relative record number, random access by key value, random access by record file address (RFA), and block I/O access by virtual block num- ber. Proxy Access: Remote users can have access to up to 15 proxy accounts on a specific remote system. One proxy account should be designated as the default proxy account on the remote system. Command Language File Management You can use most OpenVMS DIGITAL Command Language (DCL) commands to perform remote file operations. These commands include: ANALYZE, APPEND, BACKUP, CLOSE, CONVERT, COPY, CREATE, DELETE, DIFFERENCES, DIRECTORY, DUMP, OPEN, PRINT, PURGE, READ, SEARCH, SUBMIT, TYPE, and WRITE. The operation of these commands is transparent except for commands that invoke processing on a specific system (for example, SUBMIT/REMOTE and PRINT/REMOTE). Only a node name added to a file specification is re- quired to invoke the network capabilities using one of these commands. Using the COPY command, a user can transfer sequential, relative, and indexed-sequential (ISAM) files between DECnet-Plus for OpenVMS nodes that support compatible file structures and record formats. Users can transfer sequential or relative files with fixed length, variable length, or variable length with fixed control field records between two DECnet- Plus for OpenVMS systems. Similarly, multikeyed indexed files with vari- able or fixed length records are supported. 10 The SUBMIT/REMOTE command allows command files residing on a remote node to be submitted for execution at the remote node. The command file must be in the format expected by the node responsible for execution. DECnet-Plus for OpenVMS allows OpenVMS command files to be received from other systems and executed. The DCL command EXCHANGE/NETWORK allows the transfer of files to or from heterogeneous systems. This command gives users the option to trans- fer file types between MS-DOS, UNIX systems and OpenVMS systems re- gardless of record semantics. Unlike the COPY command, which preserves file and record organization during a file transfer, this command en- ables the user to modify file and record attributes during file trans- fer. OSI Application Programming Interfaces (APIs) The OSI application programming interfaces enable users to write dis- tributed applications that communicate over open networks and use the OSI services provided by DECnet-Plus. The interfaces are provided under the Extended Function license and include: o An interface to FTAM (File Transfer, Access, and Management) o Interfaces to the ACSE (Association Control Service Element) and Presentation layers o An interface to ROSE (Remote Operations Service Element) o An interface to the OSI Session layer The interfaces permit application writers to use the services of the OSI upper layers in their applications. The APIs allow you to develop applications on DECnet-Plus systems. You must compile and link source code with the APIs. The APIs are required on the development system and the compile/link system. You can run the resulting application on any DECnet-Plus system with the appropriate operating system. The APIs are not required on these target systems. See Appendix B for details on the OSI APIs. 11 Network Virtual Terminal DECnet-Plus supports two upper layer protocols for terminal access: the OSI Virtual Terminal protocol and the DECnet Command Terminal pro- tocol. 12 Virtual Terminal Virtual Terminal (VT) supports the ISO Virtual Terminal Protocol (ISO 9041). This protocol allows remote logins and access to remote appli- cations between DECnet-Plus for OpenVMS systems and any remote sys- tem, including multivendor systems, that also run an ISO-compliant Vir- tual Terminal implementation. Virtual Terminal is implemented as an Application Service Element (ASE) of the OSI Application layer. Virtual Terminal may act as the terminal/initiator (for a local user) or as the host/responder (for the remote user). A full description of Virtual Terminal features is provided in Appendix A of this SPD. Command Terminal The DCL command SET HOST allows a terminal user on one DECnet-Plus for OpenVMS node to establish a logical connection to another DECnet-Plus or DECnet Phase IV node that uses the Command Terminal (CTERM) pro- tocol. This connection makes the terminal appear to be physically con- nected to the remote system and the operator can use all the standard system and network utilities supported by that remote node. This ca- pability is particularly useful for doing remote program development and allows the terminal users on smaller application-oriented systems to use the resources of larger development-oriented systems. Other interfaces are included in DECnet-Plus for OpenVMS. You can de- velop programs and procedures based on these interfaces for functions such as file access and task-to-task communications on individual sys- tems. Because the DECnet-Plus for OpenVMS interfaces stay the same, you can use the programs and procedures developed on an individual sys- tem in a network environment without modifying them. 13 Services Downline Loading HP DECnet-Plus for OpenVMS allows for the loading of an unattended sys- tem using the services provided by the Maintenance Operations Module (MOM). MOM provides a set of maintenance operations over various types of circuits by using the Maintenance Operations Protocol (MOP). A load- able system is a system that has a load device enabled for MOP ser- vice functions and for which a properly formatted load file is sup- plied. Downline loading involves transferring a copy of the load file image to a remote target node. Load requests can come from the local DECnet-Plus for OpenVMS operator or from the target node. Downline load- ing is supported for HP server products. 14 Downline Task Loading Initial task images for loadable systems can be stored on OpenVMS file system devices and loaded into remote nodes. Programs already execut- ing on loadable systems can be checkpointed to the host OpenVMS file system and later restored to main memory in the node. These features simplify the operation of network systems that do not have mass stor- age devices. Upline Dumping Memory images of adjacent nodes connected by HP DECnet-Plus for Open- VMS can be written or dumped into a file on an OpenVMS system. This facility provides assistance in troubleshooting in the event of a sys- tem crash. This facility is also supported for HP server products. Mail The OpenVMS Mail utility allows transmission of text messages between users on systems supporting MAIL-11. The HP DECnet-Plus for OpenVMS software allows users to exchange mail with users of other DECnet-Plus and/or DECnet Phase IV systems. Phone The OpenVMS Phone utility allows users to send and receive data in- teractively from one user's terminal to another user's terminal. DECnet- Plus allows users on different systems in the same DECnet-Plus net- work to exchange information. OpenVMS Cluster Alias HP 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 can be accessed using this mechanism. The maximum num- ber of nodes supported for a cluster alias is 92. Refer to the Open- VMS Cluster SPD (29.78.xx) for relevant restrictions. 15 DECnet-Plus no longer requires a cluster member to be configured as a router. Clusters in a DECnet-Plus environment require a reachable IS-IS compliant router on the LAN. Network Management Network management is provided with the Network Control Language (NCL). Network management implements the DECnet-Plus layered model, based on the HP hierarchical structure called Enterprise Management Architec- ture (EMA). Users can access NCL through either a command line interface or a graph- ical user interface (GUI) called net$mgmt. The GUI allows network man- agers to view the status of network components and control those com- ponents from a Motif-based window interface. The HP DECnet-Plus for OpenVMS network management software allows sys- tem and network managers to: o Control and monitor the operation of a network and provide infor- mation related to network traffic and performance o Configure network operating parameters o Start up and shut down network components as needed o Detect and isolate network problems, and return the network to ser- vice once repaired. In addition, the network management software can provide information, warning network managers of faulty or failing network components, both hardware and software. Network Command Language (NCL) is provided as a utility to the net- work manager to perform the operations described above. Network managers can also use NCL to test specific components of the network. NCL enables transmission and reception of test messages ei- ther between systems or through controller loopback arrangements. The messages can then be compared for possible errors. NCL helps users iso- late network problems. 16 HP DECnet-Plus for OpenVMS provides network event logging to a ter- minal device, disk file, or remote system. NCL users can enable and disable the event logging facility as well as optionally filter spe- cific events. NCL uses the DNA Common Management Information Protocol (CMIP), which permits entity management from a single location anywhere in the DECnet- Plus network. The Common Trace Facility (CTF) allows the network manager to collect and display information about specific protocol exchanges between sys- tems. HP DECnet-Plus for OpenVMS supports an ISO CMISE application program- ming interface (API) conforming to the service definitions in ISO 9595. The API allows for development of applications that can communicate with other management applications conforming to ISO 9595 on remote nodes in the network. DECnet-Plus supports the NCP Emulator for remote management of Phase IV DECnet systems. 17 Name Service Options HP DECnet-Plus for OpenVMS allows the use of one or more naming ser- vices. The available services are DECdns, DNS/BIND (referred to as Do- main by DECnet-Plus software), and the Local namespace. TCP/IP host name and address information is maintained in DNS/BIND. DECnet node names and address towers are maintained in the DECdns and/or Local names- paces. If DECnet over TCP/IP is in use by the DECdns clerks and servers, then the IP towers will be automatically maintained in the DECdns names- pace as well. When you use more than one name service, a configurable search list defines the order in which the existing services are to be accessed. Local Namespace Using the Local namespace, you can define up to 100,000 nodes in a lo- cal naming database. A migration tool is available to move the Phase IV database to the large local file format and/or DECdns format. DNS/BIND DECnet can use TCP/IP naming and addressing information from the DNS/BIND name service. DECdns HP DECnet-Plus for OpenVMS provides a global naming service called the DIGITAL Distributed Naming Service (DECdns). The full DECdns service provides a consistent, network-wide set of names for network resources called the namespace. This namespace is main- tained by one or more DECdns server systems. HP recommends that DECdns servers be installed on at least two systems in every LAN. This should provide adequate service and redundancy. The features provided by DECdns include: o A networkwide name-to-attribute mapping service that allows selected HP applications to create, read, modify, and delete names in the namespace 18 o A hierarchical structure permitting a large number of names to be stored and distributed across the network o Access control to each name in the namespace o Management and event logging 19 Distributed Time Service HP DECnet-Plus for OpenVMS provides a network time service with DECdts, the DIGITAL Distributed Time Service. DECdts provides precise, fault- tolerant clock synchronization for systems in a LAN or WAN. Time is provided in Coordinated Universal Time (UTC) and can be used across a global network. Several forms of time providers are supported, and a callable interface for applications allows users to add their own time providers, including NTP. DECdts can be used by distributed ap- plications to determine event sequencing, duration, and scheduling. Secure Shell HP DECnet-Plus for OpenVMS now supports Secure Shell (SSH) and uses the port forwarding feature of SSH. This enables you to transmit DEC- net/IP data over a secure channel, thus providing data security. The DECnet transmitter side requires modification to support this feature; however the receiver side does not require any change. This feature can be used either Process wide or System wide by defin- ing the logical with the /PROCESS or /SYSTEM qualifiers. Operation DECnet-Plus is implemented under OpenVMS as an ancillary control pro- cess (ACP) and a network device driver with HP-supplied executive-level components and user-level programs. The normal OpenVMS protection has been incorporated in the operation of DECnet-Plus. For example, incoming connects, including file access and file transfer requests, are protected by the normal OpenVMS lo- gin and file protection mechanisms. Outgoing connects, including file access and file transfer requests, can include user password infor- mation that is implicitly specified by NCL, or explicitly specified by the user for verification on the remote node. 20 Configuration and Performance You can configure DECnet-Plus using either the BASIC or ADVANCED con- figuration options. Cluster nodes are configurable from any node within the cluster. As with any network protocol, the performance of a given DECnet-Plus for OpenVMS node is a function not only of the expected network traf- fic and resultant processing, but also of the amount of concurrent pro- cessing specific to that node. Thus, node performance depends on many factors including: o CPU types o Number and type of devices o Number of device interrupts per unit time o Communications line(s) characteristics o Number and size of buffers o Message size and frequency of transmission o Applications in use It is important to note that the rate at which user data can be trans- mitted (throughput) over a communications line can sometimes approach, but will never exceed, the actual line speed. This is because the ac- tual throughput is a function of many factors, including the line qual- ity, protocol overhead, topology, and network application(s), as well as the factors cited in this section. The performance of DECnet-Plus is comparable to the performance of DEC- net Phase IV. However, in a symmetrical multiprocessing environment the performance of DECnet-Plus can be far superior to that of DECnet Phase IV. With DECnet Phase IV the NETACP process can only execute on the primary CPU. With DECnet-Plus the NET$ACP process can be sched- uled on any available CPU, resulting in improved performance. 21 Standards Conformance HP DECnet-Plus for OpenVMS has been designed and implemented to con- form to the following standards: o ISO - 4335 - 7776, 7809 - 8073, 8208, 8327, 8473, 8571, 8650, 8802-2, 8802-3, 8823, 8878, 8881 - 9314, 9542, 9041 - 3309 o EN 41 204, 41 205, 41 206, 41 207 o CCITT Recommendation X.25 (1978, 1980, or 1984) using the LAPB or LAPBE variants of the X.25 packet level and data link protocols (Alpha- only) o U.S. GOSIP V2.0 o U.K. GOSIP V4.0 Contact your local HP office for the most recent conformance certifi- cates. Documentation The documentation for HP DECnet-Plus for OpenVMS is supplied as fol- lows: o Online versions of the documentation are shipped as part of the Open- VMS Online Documentation Library on CD-ROM and on the OpenVMS lay- ered product CD-ROM. o Printed copies of the documentation are available as a separate or- der. 22 o An optional X.25 documentation set covering accounting, X.29, and X.25 Mail is available as a separate order. o New features are documented extensively in the Release Notes. Installation DECnet-Plus software is customer installable. Installation services are available for customers who request installation of the software product by an experienced HP software specialist. HP requires that a customer's first use of X.25 include HP Installa- tion Services. These services provide for installation of the soft- ware product by an experienced HP software specialist. Customer Responsibilities Before HP Services can install the software, the customer must: o Ensure that the system meets the minimum hardware and software re- quirements (as specified in the relevant SPDs) o Prior to installing HP hardware or software, obtain, install, and demonstrate as operational any modems and other necessary customer equipment or facilities to which HP's communications hardware or software will connect o Designate one adjacent node to verify installation and connectiv- ity o Make available for a reasonable period of time, as mutually agreed upon by HP and the customer, all hardware communications facili- ties and terminals that are to be used during installation. Delays caused by any failure to meet these responsibilities will be charged at the prevailing rate for time and materials. Installation of HP DECnet-Plus for OpenVMS consists of the following tasks: o Verify that all components of HP DECnet-Plus for OpenVMS have been received. 23 o Verify that the necessary versions of the OpenVMS software and doc- umentation are available. o Verify the appropriate SYSGEN parameters. Note: If a software specialist is required to modify the previously installed operating system parameters, a time and materials charge will apply. o Create any necessary HP DECnet-Plus for OpenVMS accounts and di- rectories. o Enable software by registering the License Product Authorization Key (PAK) . o Install the HP DECnet-Plus software on the target system using the POLYCENTER Software Installation utility . o Verify the proper installation of HP DECnet-Plus for OpenVMS by run- ning a series of tests to show connectivity to a designated node. Connectivity to all other nodes within the network is the responsi- bility of the customer. HP recommends the use of NCL to help verify connectivity. In some cases, the PSDN supplier (or PTT) may impose restrictions, lim- itations, or requirements on the proposed HP network configuration. The customer must understand and adhere to these controls for every network. Hardware Requirements Refer to the HP OpenVMS for Integrity Servers and HP OpenVMS Alpha Op- erating Systems Software Product Description (SPD 82.35.xx) for hard- ware requirements and processor support. Disk Space Requirements (Block Cluster Size = 1) The following counts refer to the disk space required on the system disk. The sizes are approximate; actual sizes may vary depending on the user's system environment, configuration, and software options. 24 Disk space required for installation: - Base DECnet-Plus software: 89,000 blocks - Base DECnet-Plus software with optional DECdns server and DECdts server software included: 104,000 blocks Supported LAN Adapters Refer to the HP OpenVMS for Integrity Servers and HP OpenVMS Alpha Op- erating Systems Software Product Description (SPD 82.35.xx) for a list of supported LAN adapters. Software Requirements HP DECnet-Plus for OpenVMS Integrity servers Version 8.4 requires Open- VMS Version 8.4 and Alpha Version 8.4 requires OpenVMS Version 8.4 of the operating system. Optional Software TCP/IP A separate TCP/IP protocol stack is required to use the DECnet over TCP/IP features in DECnet-Plus. This release contains support for In- ternet Protocol Version 4 (IPv4) and does not support Internet Pro- tocol Version 6 (IPv6). The following TCP/IP product has been tested with DECnet-Plus: HP TCP/IP Services for OpenVMS Version 5.7. HP TCP/IP Client Software License: QL-0M2A*-** HP TCP/IP Services Software License: QL-0LXA*-** HP TCP/IP Client Upgrade License: QL-0PHA*-** SPD: 46.46.xx X.25 Optional License 25 The DECnet-Plus for OpenVMS license grants the right to use the OSI applications for CONS over LLC2 or CLNS over DEC-HDLC (Alpha-only). All other X.25 software functions over LAPB (Alpha-only), LLC2, and RFC 1613 require the X.25 for OpenVMS license. The X.25 for OpenVMS license is also required to enable the X.25 util- ities, such as X.25 Mail and SET HOST/X.25, as well as the X.25 ap- plication programming interfaces (APIs). Version 2.0 of the X.25 for OpenVMS product is required for this version of DECnet-Plus. Software Licenses: Alpha QL-0THA*-AA Integrity Servers BA390AC Media and Documenta- tion: Alpha QA-03XAA-H8 Integrity Servers BA390AA (See SPD 47.37.xx.) Growth Considerations The minimum hardware/software requirements for any future version of this product may be different from the requirements for the current version. Distribution Media This product is available as part of the OpenVMS Consolidated Soft- ware Distribution on CD-ROM. The software documentation for this prod- uct is also available as part of the OpenVMS Online Documentation Li- brary on CD-ROM. 26 Ordering Information In the following table, asterisks (*) denote variant fields. For ad- ditional information on available licenses, services, and media re- fer to the appropriate price book. Software Licenses: Alpha End System QL-MTFA*-AA Integrity Servers Included in OE license End System Alpha Extended QL-MTGA*-AA Function Integrity Servers BA406AC Extended Function Software Media: Alpha QA-03XAA-H8 Integrity Servers BA322AA BA323AA Consolidated Distri- bution Services: Alpha QT-03XAA-*8 Integrity Servers Included in OE service offerings Software Licensing The DECnet-Plus licenses give users the right to use the software and includes the delivery of a License Product Authorization Key (PAK) to enable the DECnet-Plus for OpenVMS software. On OpenVMS Integrity server systems, the DECnet for OpenVMS license is part of Base Operating En- vironment (BOE), which is licensed on a per core license basis. The End System license grants the right to use all the DECnet-Plus fea- tures with the exception of the OSI application programming interfaces, the OSI applications gateway, and routing. 27 The Extended Function license grants the right to use the DECnet-Plus end-system features, OSI application gateways, OSI application pro- gramming interfaces, and host-based routing. DECnet-Plus Cluster Alias no longer requires a cluster member to be configured as a router and hence the extended function license is also not required to be present on the cluster. However it is required to have a reachable IS-IS compliant router on the LAN. The Extended Function License is also required to configure a node as a DECdns server. This software is furnished under a license only. For more information about HP's licensing terms and policies, contact your local HP office. License Management Facility Support This product supports the OpenVMS Alpha and Integrity servers License Management Facility. License units for this product are allocated on a CPU basis. For more information on the License Management Facility, refer to the HP OpenVMS for Integrity Servers and HP OpenVMS Alpha Operating Sys- tems Software Product Description (SPD 82.35.xx) or the License Man- agement Facility manual of the OpenVMS Alpha operating system docu- mentation set. For more information about HP's licensing terms and policies, contact your local HP office. Software Product Services Prerequisite Support For the use of X.25 with PSDNs, it is recommended that the customer and HP jointly prepare a Network Profile and Customer Support Plan cov- ering all the intended network nodes, their usage of switched virtual circuits (SVCs), permanent virtual circuits (PVCs), and other network 28 facilities, and their support. Without this Network Profile and Cus- tomer Support Plan, HP cannot support the network connections. A variety of service options are available from HP. For more infor- mation, contact your local HP office. Software Warranty This software is provided by HP with a 90 day comformance warranty in accordance with the HP warranty terms applicable to the license pur- chase. 29 Appendix A: File Transfer, Access, and Management (FTAM) FTAM software provides communications for the following file opera- tions between open systems: o Copying files between local and remote systems o Appending, deleting, or renaming files o Displaying information about files An open system is a computer system that implements the standards for each of the seven layers of the Open Systems Interconnection (OSI) Ref- erence Model for communications as defined by the International Or- ganization for Standardization. An FTAM system is any open system con- taining an FTAM implementation that conforms to the FTAM standard and includes the implementations of the necessary underlying OSI services. FTAM implements several standards that define the following components of these layers of the OSI Basic Reference Model: the FTAM service el- ement and the Association Control Service Element (ACSE) of the Ap- plication layer, the Presentation layer, and the Session layer. Supported Standards FTAM conforms to the following OSI standards: o ISO 8571 - File Transfer, Access, and Management service and pro- tocol o ISO 8650 - ACSE protocol o ISO 8823 - Presentation protocol o ISO 8327 - Session protocol Table 1 compares the supported implementation profiles for different standards bodies and their relationship to each other. 30 ___________________________________________________________________ Table_1:_Standards_and_Implementation______________________________ International Standardized Profiles (ISP) ISO_10607_________NIST________CEN/CENELEC_and_EWOS_________________ Part 1: Spec- - - ification of ACSE, Pre- sentation and Session proto- cols for use by FTAM Part 2: Def- - - inition of document types, con- straint sets, and syntaxes Part 3: AFT11 T1 - A/111 - - Simple Simple iENV 41 204 File Trans- File fer Service Transfer (Unstructured) Part 4: AFT12 T2 - Po- A/112 - (DISP)[1] - sitional ENV 41 206 Positional File File Trans- Transfer fer Service (Flat)[2] ___________________________________________________________________ [1]Draft ISP [2]AFT12 is not supported by DECnet-Plus 31 ___________________________________________________________________ International Standardized Profiles (ISP) ISO_10607_________NIST________CEN/CENELEC_and_EWOS_________________ Part 5: AFT3 M1 - A/13 - (DISP)[1] - Manage- ENV 41 205 File Manage- ment ment_Service_______________________________________________________ [1]Draft ISP ___________________________________________________________________ FTAM Component Software The component software includes the user facilities (initiators), re- sponders, management tools, and problem determination tools. FTAM User Facilities Users access the FTAM user facilities by entering the following Open- VMS operating system commands: APPEND, COPY, DIRECTORY, RENAME, and DELETE. These commands operate on files stored on any FTAM system whose implementations are compatible with FTAM. You cannot use these com- mands to manipulate files directly on your local system. Support for Any File-Naming Convention A file designation is system-specific information that identifies a file to its storage system. FTAM software lets users specify files us- ing the naming conventions of the systems where the files reside. FTAM supports the OpenVMS operating system RMS format for file specifica- tions and a comparable style of file-specification format that accom- modates non-RMS file designations. 32 Support for Several File Types FTAM software can access and transfer files containing both binary and ASCII data. FTAM-1, FTAM-2, FTAM-3, and NBS-9 document types are sup- ported. FTAM-1 files are unstructured text files, FTAM-2 files are sequential text files, and FTAM-3 files are unstructured binary files. Table 2 shows the parameters supported by FTAM-1, FTAM-2, and FTAM-3 document types. ___________________________________________________________________ Table_2:_FTAM_Document_Types_______________________________________ String Document Signifi- Universal Type______cance_______Class_______Maximum_String_Length____________ FTAM-1 Not IA5String Presence and absence of parame- significant ter GeneralString Fixed VisibleStrinPresence of parameter GraphicString Variable VisibleStrinPresence and absence of parame- ter GraphicString FTAM-2 Not VisibleStrinPresence or absence of parameter significant GraphicString FTAM-3 Not Presence or absence of parameter significant __________Fixed___________________Presence_of_parameter____________ NBS-9 files are NBS file directories. 33 Flexible and Transparent Access for Local Files FTAM software treats local files the same way that the OpenVMS oper- ating system file system treats them. File Transfers The FTAM COPY command transfers files between compatible FTAM systems without modifying the source file. The facility can transfer files in either direction between the local system and a remote FTAM system. The COPY command can also transfer files between two remote FTAM sys- tems for a local FTAM user. The COPY command also allows you to append one or more files to a sin- gle output file within or between FTAM systems. FTAM-DAP Gateway The FTAM-DAP Gateway lets you perform file operations from a non-OSI system that supports the DAP protocol to an OSI system supporting FTAM. Remote users of the gateway need not establish accounts on the gate- way system to use its capabilities. The gateway does not support the APPEND functionality. 34 File Deletion The FTAM DELETE command lets you delete one or more files on any com- bination of FTAM systems provided you have delete access to those files on the specific FTAM system. Renaming Requests The FTAM RENAME command allows you to rename files. The command works on files stored on remote FTAM systems (remote files). The command en- ables you to change the path name or file name of an existing file. For remote files, you must specify whatever type of information the remote FTAM system requires for specifying files. Directory Requests The FTAM DIRECTORY command lets you display the complete set of FTAM file attributes. Specific options allow you to vary the display of at- tributes that are meaningful in an OpenVMS operating system environ- ment, for example, date and time of the last modification of file name. FTAM File Error Recovery FTAM provides file error recovery functionality, both in the COPY ini- tiator command and in the FTAM responder. File error recovery is pro- vided for classes 1, 2, and 3 errors as detailed in ISO 8571-4. Class 1 file error recovery provides only the restart functionality, while classes 2 and 3 provide both the restart and recovery function- ality as follows: o If an internal error is detected in the data transfer regime, class 1 recovery restarts the data transfer regime by retransmitting the file data beginning at the negotiated checkpoint within the data transfer regime. o Class 2 error recovery provides for the re-establishment of the se- lect and open regimes, and also allows for the retransmission of file data beginning at a negotiated checkpoint within the data trans- fer regime. 35 o Class 3 error recovery provides full recovery by re-establishing a lost FTAM association and its select and open regimes. Class 3 recovery then restarts the data transfer regime by retransmitting the file data beginning at the negotiated checkpoint within the data transfer regime. All restart and recovery operations and procedures are completely trans- parent to the user. 36 Management and Problem Determination Tools FTAM software supplies a number of management tools, including an in- stallation verification procedure (IVP), a tracing utility, event log- ging, and informational and error messages. FTAM Installation Verification Procedure (IVP) The FTAM IVP sets up outbound and inbound application associations. A connection is made to your local system (as a loopback test). The FTAM IVP checks that your installation is able to set up and release presentation and session connections. It tests the FTAM software by starting a responder and reading the attributes of a file with the DI- RECTORY command. FTAM Tracing Utility The FTAM tracing utility (OSITRACE) is a tool for identifying prob- lems in protocol exchanges between your local system and any remote FTAM system. The tracing utility captures protocol exchanges and tran- scribes them into easily read text; OSITRACE data is written to SYS$OUTPUT. The FTAM tracing utility monitors data exchanges for individual as- sociations. The tracing utility can trace data originating from the following components: FTAM (DATA, PROTOCOL, and STRUCTURING), ACSE, Presentation, and Session. OSI Address Lookup Using X.500 The FTAM software is capable of retrieving network addresses from the X.500 directory. You can use this functionality with or instead of re- trieving addresses from a local repository. FTAM Event Logging For event logging, the FTAM responder writes records to OSIF$RESPONDER.LOG. 37 Requirements for Compatibility with FTAM FTAM lets an open system perform a specific set of file transfer, ac- cess, and management activities with any open system having a compat- ible FTAM implementation. The Protocol Implementation Conformance Statement (PICS) provides more information about HP's FTAM implementation. 38 Appendix B: Virtual Terminal DECnet-Plus Virtual Terminal (VT) is Hewlett Packard Company's imple- mentation of the ISO Virtual Terminal Basic Class standard, which con- sists of the service definition (ISO 9040) and the protocol (ISO 9041). VT software adheres to these standards, thereby providing interactive access between DECnet-Plus systems and other multivendor terminal sys- tems and host systems that also adhere to the ISO Virtual Terminal Ba- sic Class standard. VT is implemented as an Application Service Element (ASE) of the OSI Application layer. VT can run over Transport layer classes 0, 2 or 4 over CONS, and TP4 over CLNS. VT can also run over TCP/IP networks using RFC 1006. VT provides terminal/initiator (for a local user) and host/responder (for the remote user) capabilities. Terminal/responder and host/initiator are not supported. Supported Standards VT conforms to the following OSI standards: ISO 9041 - Virtual Terminal protocol - basic class ISO 8650 - ACSE protocol ISO 8823 - Presentation protocol ISO 8327 - Session protocol Virtual Terminal Features Virtual Terminal supports the following features: o Basic class (character cell terminals) of service o Asynchronous mode (A-Mode) of operation o Profile Support - Default A-mode (per ISO 9040) - A-mode Generalized Telnet (adheres to OIW Stable Agreements) - A-mode Transparent (adheres to OIW Stable Agreements) 39 - A-mode Telnet 1988 (adheres to OIW Stable Agreements) o Functional Units - destructiveBreak - structuredCOs - urgentData o Supported Gateways - Bidirectional VT/Telnet - Bidirectional VT/LAT o Online Help OSI Address Lookup using X.500 The VT software is capable of retrieving network addresses from the X.500 directory. You can use this functionality with or instead of re- trieving addresses from a local repository. Command Mode Command mode allows you to execute commands that can modify the char- acteristics of the Virtual Terminal association with the remote ap- plication. Trace Utility The VT tracing utility (OSITRACE) is a tool for identifying problems in protocol exchanges between your local system and any remote sys- tem. The utility captures protocol exchanges and transcribes them into easily read text. The tracing utility monitors data exchanges for individual associa- tions. The utility can trace data originating from the VT, ACSE, Pre- sentation, and Session components. 40 Appendix C: OSI Application Programming Interfaces FTAM API The FTAM API supports the OSI standard ISO 8571: Information Process- ing Systems, Open Systems Interconnection, and File Transfer, Access, and Management. The FTAM API provides the interface to the FTAM protocol machine pro- vided in DECnet-Plus. Communications between the application code and the FTAM protocol machine are carried out using ASN.1 encoded data struc- tures. The API supports the following functions: Abort Begin-Group Cancel Change-Attributes Create Close Data Data-End Delete Deselect End-Group Initialize Open Read-Attributes Read Select Terminate Transfer-End Write OSI Application Kernel (OSAK) API The OSAK API provides a direct interface to services at the ACSE and Presentation layer. The OSAK API supports the following OSI standards for the ACSE layer: 41 o ISO 8650: Information Processing Systems, Open Systems Intercon- nection, Protocol Specification for the Association Control Ser- vice Element o ISO 8649: Information Processing Systems, Open Systems Intercon- nection, Service Definition for the Association Control Service El- ement The OSAK API provides the interface to the ACSE services. It provides the following services: Associate Release Abort Redirect The redirect service is not an ACSE service. The service allows ap- plications to redirect an incoming association to another process on the local system. The OSAK API also includes support for the OSI Presentation layer with support for the following OSI standards: o ISO 8823: Information Processing Systems, Open Systems Intercon- nection, Connection-Oriented Presentation Protocol Specification o ISO 8822: Information Processing Systems, Open Systems Intercon- nection, Connection-Oriented Presentation Service Definition o ISO 8327: Information Processing Systems, Open Systems Intercon- nection, Basic Connection-Oriented Session Protocol Specification o ISO 8326: Information Processing Systems, Open Systems Intercon- nection, Basic Connection-Oriented Session Service Definition The Presentation layer services supported by the OSAK API are: Alter-Context Data Capability-Data Expedited-Data Typed-Data 42 Token-Please Token-Give Control-Give Sync-Major Sync-Minor Resynchronize Exception-Report Activity-Start Activity-Interrupt Activity-Resume Activity-Discard Activity-End The OSAK API also supports (by pass through) the OSI Session layer ser- vices. Session Layer API The Session layer API, called the OSAK Session Programming Interface (SPI), supports the following OSI standards: o ISO 8327: Information Processing Systems, Open Systems Intercon- nection, Basic Connection Oriented Session Protocol Specification o ISO 8326: Information Processing Systems, Open Systems Intercon- nection, Basic Connection Oriented Session Service Definition. The Session layer supports ISO Session version 1 and version 2. Ses- sion version 1 allows up to 512 octets of user data on a service. Ses- sion version 2 supports the restrictions imposed by the National In- stitute of Standards and Technology allowing up to 10,240 octets of data on a service. HP DECnet-Plus for OpenVMS Version 7.3 includes Version 3.0 of the OSAK SPI. Users of the OSAK SPI Version 1.1 should upgrade to Version 3.0. The OSAK API provides the interface to the following connect and re- lease services: Connect Release 43 Abort Redirect The redirect service is not a Session service. The service allows ap- plications to redirect an incoming connection to another process on the local system. The Session layer services supported by the OSAK API are: Data Capability-Data Expedited-Data Typed-Data Token-Please Token-Give Control-Give Sync-Major Sync-Minor Resynchronize Exception-Report Activity-Start Activity-Interrupt Activity-Resume Activity-Discard Activity-End ROSE API The Remote Operations Service Element (ROSE) supports the OSI stan- dard ISO 9072: Information Processing Systems, Text Communication, and Remote Operations. ROSE supports interactive applications in a distributed open systems environment. It is a service for multivendor distributed processing. The ROSE functionality provides a mechanism that allows for encoding and decoding the remote operations protocol control information, as defined in ISO 9072, for the following services: Invoke 44 Result Error Reject The information in this document is valid at the time of release. Please contact your local HP office for the most up-to-date information. © Copyright 2010 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for pos- session, use or copying. Consistent with FAR 12.211 and 12.212, Com- mercial Computer Software, Computer Software Documentation, and Tech- nical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional war- ranty. HP shall not be liable for technical or editorial errors or omis- sions contained herein. 45 46