Software Product Description ___________________________________________________________________ PRODUCT NAME: HP TCP/IP Services for OpenVMS Version 5.4 SPD 46.46.17 DESCRIPTION The HP TCP/IP Services for OpenVMS software product is the OpenVMS im- plementation of the industry-standard TCP/IP protocol suite and in- ternet services for OpenVMS Alpha and OpenVMS VAX systems. The ker- nel software is ported from the Tru64 UNIX product, which is based on the Berkeley Software Distribution (BSD) Versions 4.3 and 4.4, with enhancements from HP. Note: TCP/IP Services V5.4 is not supported on VAX systems. Internetworking with TCP/IP hides the hardware details of each indi- vidual network and allows computers to communicate independent of their physical network connections. Internetworking uses a uniform set of protocols to define behavior on an internet for all nodes using sup- ported network media. TCP/IP provides both a standard transport mech- anism and full-duplex, reliable, stream communication services for soft- ware applications. Licenses The following HP TCP/IP Services for OpenVMS licenses are available: September 2003 AE-Q088N-TE HP TCP/IP Services for OpenVMS Version 5.4 SPD 46.46.17 ___________________________________________________________________ License__________Description_______________________________________ Client For customers who require only client components (FTP, IMAP, LPD, TELNET, SNMP, NTP, NFS client, metric server, POP, FINGER, SSH, RLOGIN, REXEC, RSH, RMT/RCD, and XDM). Server For customers who require full product function- ality including all the client components, plus BIND, BOOTP, DHCP, TFTP, NFS Server, PC-NFS, and load broker. Client up- For customers who previously purchased a client grade license and now require full server functional- _________________ity.______________________________________________ Network Interface Layer Support With support for multiple network interfaces for each physical net- work controller, the HP TCP/IP Services for OpenVMS software allows OpenVMS systems to connect to individual host computers on different types of networks: o Ethernet for IPv4 and IPv6 o Fiber Distributed Data Interface (FDDI) for IPv4 and IPv6 o Token Ring for IPv4 o Asynchronous transfer mode (ATM) (Alpha systems only) for IPv4 Individual host computers can also connect with other hosts or net- works over serial communications lines using either the Serial Line Internet Protocol (SLIP or CSLIP) or the Point-to-Point Protocol (PPP). 2 HP TCP/IP Services for OpenVMS Version 5.4 SPD 46.46.17 Internet Layer Support The HP TCP/IP Services for OpenVMS product supports the following In- ternet layer protocols that work together to move data around the in- ternet: o Internet Protocol (IP) provides a connectionless packet delivery service for IPv4 and IPv6. o Internet Control Message Protocol (ICMP) provides diagnostic func- tions and handles error and control messages for IPv4 and IPv6. o Address Resolution Protocol (ARP) dynamically maps an IP address to a physical hardware address for IPv4. o Neighbor Discovery discovers neighbors in the same link, dynami- cally detects routers, dynamically maps all IP addresses to a phys- ical hardware address for IPv6, and maintains information about the paths to active neighbors. o Path MTU for TCP and UDP calculates the most efficient means of trans- porting data across a network. o Classless Interdomain Routing (CIDR) reduces routing tables and makes more efficient use of the IP address space. o IPv6 mobile correspondent node allows the OpenVMS host to commu- nicate with mobile nodes and other correspondent nodes. o Routing protocols and routing daemons enable gateways to exchange current routing information about hosts and directly connected net- works. Supported protocols include: - Routing Information Protocol (RIP) Version 1 (RFC 1058) and RIP Version 2 (RFC 1388) for IPv4, and RIPng (RFC 2080) for IPv6 - Open Shortest Path First (OSPF) Version 2 (RFC 1583) - Exterior Gateway Protocol (EGP) (RFC 904) - Border Gateway Protocol (BGP) (RFC 1163, RFC 1267) - Router Discovery (RFC 1256) for IPv4 3 HP TCP/IP Services for OpenVMS Version 5.4 SPD 46.46.17 The routing daemons ROUTED and GATED communicate with the kernel to add new routes or to delete or modify existing routes. The Enhanced Gateway Routing Daemon (GATED) is based on GateD Unicast Version 4.0.6, with advanced routing options. 4 HP TCP/IP Services for OpenVMS Version 5.4 SPD 46.46.17 High Availability failSAFE IP provides higher availability of IP addresses by removing the NIC as a single point of failure. failSAFE IP is cluster aware, so standby IP addresses can be configured within the same node or across a cluster. Typical failures that failSAFE IP guards against include NIC failure, broken cable, failed port on a switch, and node shutdown. Transport Layer Support To provide either connection-oriented or connectionless data trans- mission between two hosts (local or remote), the HP TCP/IP Services for OpenVMS product supports both TCP and UDP protocols. These pro- tocols form the bridge between the Application layer and the Inter- net layer: o Transmission Control Protocol (TCP) provides reliable, connection- oriented, sequenced data transfers for applications that must guar- antee delivery of the data. o User Datagram Protocol (UDP) provides fast, connectionless data trans- fers for applications that do not require delivery confirmation. The TCP Extensions for High Performance (RFC 1323), and the IETF Wire- less TCP Standards help prevent congestion on low-bandwidth high-delay wireless and satellite networks. The wireless TCP set of standards en- compasses TCP Extensions for High Performance (RFC 1323), SACK (RFC 2018), and Path MTU Discovery for IPv4 (RFC 1191) and IPv6 (RFC 1981). - RFC 1323 includes support for PAWS (Protection Against Wrapped Se- quence) numbers, which supplies time stamps on transactions to pre- vent wrapped sequence numbers and for TCP window scale, which pro- vides window scale factors for TCP connections. - RFC 2018 defines TCP selective acknowledgment options, supporting multiple acknowledgment windows and allowing outstanding acknowl- edgments even if sequence numbers are not in order. 5 HP TCP/IP Services for OpenVMS Version 5.4 SPD 46.46.17 Application Layer Support The HP TCP/IP Services for OpenVMS product supports numerous Appli- cation layer protocols that allow OpenVMS users to: o Run software on remote systems o Transfer data files between local and remote systems o Share remote system resources such as disk storage space and print- ers as if they were directly connected to the user's local system o Send and receive electronic mail messages locally or across the world- wide Internet o Provide consistent, reliable, and efficient network services to all users on the internet Remote Computing With TELNET, an OpenVMS user can log in to remote hosts in the net- work. The TELNET features include: o Simultaneous multiple sessions o IBM 3270 model terminal emulation (TN3270) o Support for both OpenVMS style and UNIX style interfaces o Support for window sizing (rows and columns) and location options o Kerberos authentication The popular UNIX Remote commands, called R commands, let OpenVMS users work in accounts on remote internet hosts that are either UNIX or OpenVMS systems. The HP TCP/IP Services for OpenVMS software supports the RLOGIN, RSH, REXEC, and RMT/RCD commands. The SSH command logs into a remote server and provides remote command execution using authentication and data encryption to ensure a secure connection. 6 HP TCP/IP Services for OpenVMS Version 5.4 SPD 46.46.17 The FINGER utility enables users to obtain information about each user on local or remote systems. This information includes user name, ac- count name, and the program the user is running. The X Display Manager Control Protocol (XDMCP) allows display devices to request that the login server present a login screen. File Transfer OpenVMS users transfer data files between local and remote systems through the use of the following components: o File Transfer Protocol (FTP) creates, deletes, and copies files and directories between hosts. FTP supports OpenVMS Extended File Specifications (long file names, deep directories, and extended character sets) for ODS-5 disks. o Trivial File Transfer Protocol (TFTP) transfers files using the UDP protocol and no authentication and is typically used during the boot- strap process of diskless systems. o The remote copy (rcp) command copies files between the local host and a remote host or between two remote hosts. o The secure copy (SCP) and secure file transfer (SFTP) commands en- sure secure file copy operations using authentication and data en- cryption. Resource Sharing The HP TCP/IP Services for OpenVMS software provides network print- ing services through the line printer/line printer daemon (LPR/LPD) and the TELNET print symbiont (TELNETSYM). o LPD provides remote printing services for UNIX and OpenVMS client hosts through local and remote print queues. Once the system man- ager sets up the print queues, OpenVMS client users enter the DCL command PRINT, and UNIX client users enter the lpr command. LPD can be configured for clusterwide availability, providing load bal- ancing and automatic failover for LPD-controlled print queues on the OpenVMS host. 7 HP TCP/IP Services for OpenVMS Version 5.4 SPD 46.46.17 o TELNETSYM provides remote print services that enable the use of stan- dard OpenVMS printing features not available with LPR/LPD. Network File System The Network File System (NFS) server software allows NFS client users to gain transparent access to remote file services. With NFS, when a user accesses files and directories from a remote system, they appear to reside on the local system regardless of operating system, hard- ware type, or architectural differences between the local and remote systems. The PC-NFS daemon provides authentication services to PC-NFS clients. TCP/IP Services provides support for NFS Version 2 and Version 3 in the NFS server. The NFS client is limited to Version 2. The main benefit of NFS Version 3 is increased maximum file size-up to 1 terabyte for an OpenVMS file system and up to 4 gigabytes for a container file system. Performance gains may result from the improve- ments to file-size processing and the enhanced write performance that allows the NFS server to acknowledge a write operation before the files are actually written to disk. Afterward, the server's response to a commit message confirms that the data has been written to disk. The NFS server supports communication over both TCP and UDP. NFS over TCP offers better support for file access over wide area links than UDP. The NFS client is limited to UDP only. The NFS server and client support OpenVMS Extended File Specifications, including long file names, deep directories, and extended character sets on ODS-5 file structures. 8 HP TCP/IP Services for OpenVMS Version 5.4 SPD 46.46.17 Electronic Mail With the Simple Mail Transfer Protocol (SMTP), OpenVMS users can send and receive electronic mail to and from local and remote hosts. The HP TCP/IP Services for OpenVMS implementation of SMTP uses the OpenVMS Mail facility, which automatically recognizes an SMTP host address in the format smith@widgets.com. SMTP provides support for SFF (Send From File) and outbound alias specification. The following mail systems work with SMTP, providing reliable, server- based mail repositories for clients: o Post Office Protocol (POP) server o IMAP Mail server (Alpha systems only) Network Services With the following HP TCP/IP Services for OpenVMS management compo- nents, network and system managers can provide consistent, reliable, and efficient services to their users with minimal interruption: o Simple Network Management Protocol (SNMP) Version 2 includes a mas- ter agent and subagents that allow the OpenVMS system to be man- aged by a management station on the network. This version includes the same features found in the HP Tru64 UNIX SNMPv2 implementation, along with other improvements. o Network Time Protocol (NTP) Version 4 provides a means to synchro- nize time and coordinate time distribution throughout a TCP/IP net- work. NTP provides accurate and dependable timekeeping for OpenVMS hosts on TCP/IP networks. o Berkeley Internet Name Domain (BIND) is a distributed database sys- tem that distributes and manages host information so that hosts do not need to locally manage the address of every other host on the internet. The BIND 9 server (available on Alpha systems only) is based on the Internet Software Consortium's (ISC) BIND 9.2.1 im- plementation. It includes dynamic updates and BIND server cluster failover, which allows multiple BIND master servers to share a com- mon database, thus providing both redundancy and a failover mech- anism when one of the servers becomes unavailable. 9 HP TCP/IP Services for OpenVMS Version 5.4 SPD 46.46.17 The BIND resolver on both VAX and Alpha systems, and the BIND server on VAX systems, are based on the ISC's BIND 8.1.2 implementation. o Load broker supplies cluster load balancing, round-robin schedul- ing, and automatic failover. o Metric server calculates and reports the DNS load on the local host. It includes dynamic configuration of logical names, which can be defined for CPU rating, compute interval, and debug level, as well as support for multihomed systems to allow load balancing of in- coming traffic across multiple IP addresses. o Portmapper allocates ports so that system managers do not need to preconfigure client applications with port numbers for each ser- vice. o Auxiliary server process is the HP TCP/IP Services for OpenVMS im- plementation of the UNIX internet daemon (inetd). The auxiliary server greatly simplifies application writing, manages overhead by reduc- ing simultaneous server processes, provides system security through authentication of service requests, and supports event and error logging. o Dynamic Host Configuration Protocol (DHCP) is a superset of the Boot- strap Protocol (BOOTP). In addition to BOOTP functionality (answer- ing bootstrap requests), DHCP offers robust configuration services, including IP address, subnet masks, and default gateways. The DHCP server can be configured to support BOOTP clients. If BOOTP is en- abled without DHCP, DHCP functionality is not available. o DHCP dynamically updates BIND using a feature that allows DHCP clients to be configured with a registered name. DHCP uses this name to as- sign an address when it updates the BIND database. In addition, this release offers both a DHCP client and server, which provides a cen- tralized approach to the configuration and maintenance of IP ad- dress space. With DHCP server, the system manager can provide dy- namic allocation of IP addresses from an OpenVMS host. 10 HP TCP/IP Services for OpenVMS Version 5.4 SPD 46.46.17 Security The HP TCP/IP Services for OpenVMS product provides optional security mechanisms, including: o Secure POP SSL (Secure Sockets Layer) is supported for POP (Post Office proto- col), providing secure retrieval of mail. The secure POP server accepts connections on port 995. Secure POP en- crypts passwords, data, and POP commands and is compatible with clients that use SSL, such as Microsoft[R] Outlook. To use this feature, you must download the HP SSL kit for OpenVMS Al- pha 11 HP TCP/IP Services for OpenVMS Version 5.4 SPD 46.46.17 o SSH for OpenVMS The Secure Shell (SSH) for OpenVMS client and server provide secure login, remote command execution, and file transfer. This implementa- tion is based on SSH2 Version 2.4.1, from SSH Communications Security Corp. Performance and Scalability The TCP/IP kernel has been modified to provide increased performance on symmetric multiprocessing (SMP) systems. The new kernel is optional. The default is to run with the classic TCP/IP kernel. This complete redesign of the TCP/IP kernel provides enhanced perfor- mance on SMP systems by removing CPU contention among users. The new kernel uses a dynamic spinlock to lock the main internal database. All processing that requires locking is directed to a designated TCP/IP CPU, thereby eliminating CPU contention with other CPU users. Essen- tially, network I/O becomes a series of asynchronous, transaction-based operations. Management Control Program The HP TCP/IP Services for OpenVMS product provides the Management Con- trol Program, which is a comprehensive, easy-to-use network manage- ment tool based on familiar OpenVMS DCL command syntax. These commands let system managers configure and monitor the product components lo- cally. The flexible configuration process includes an interactive configu- ration procedure. Startup and shutdown files are provided for individual services, al- lowing system managers to stop and start individual services without affecting the operation of the remaining TCP/IP Services software. Support for both DCL or UNIX management commands provides a choice of methods for configuring and managing the network connections and the TCP/IP Services software. 12 HP TCP/IP Services for OpenVMS Version 5.4 SPD 46.46.17 UNIX Network Management Utilities The HP TCP/IP Services for OpenVMS product provides UNIX networking management utilities for system managers who are experienced in man- aging and troubleshooting the UNIX network subsystem. Supported util- ities include: o arp o finger o ifconfig o netstat o ping o ripquery o route o sysconfig o sysconfigdb o tcptrace o traceroute o tcpdump Subsystems can be configured in the sysconfigtab database. Note that some UNIX flags and parameters may not be supported. Error Message Documentation The HP TCP/IP Services for OpenVMS product provides online help for error messages for TCP/IP facilities and components. The information is included as part of the OpenVMS Help Message utility (MSGHLP). 13 HP TCP/IP Services for OpenVMS Version 5.4 SPD 46.46.17 Application Programming Interfaces (APIs) The HP TCP/IP Services for OpenVMS product provides the following APIs for programmers to develop customized applications: o Berkeley Sockets and Sockets Library provide UNIX like access for TCP, UDP, and raw IP to applications written in the C programming language. The library includes support for: - Both IPv4 and IPv6 basic socket interface extensions for IPv6 (RFC 2553 and IETF updates) - Advanced sockets API for IPv6 (RFC 2292 and IETF updates) o The $QIO interface extends the OpenVMS system services for socket communications, providing access to TCP, UDP, and IP for applica- tions written in supported programming languages. o The SRI $QIO interface translates older, incompatible SRI $QIO in- terfaces into $QIO interfaces. o ONC RPC provides an industry-standard, portable API for program- mers who do not have an in-depth knowledge of networking protocols. This is an efficient alternative to application development using sockets. o Extensible Simple Network Management Protocol (eSNMP) provides rou- tines for building SNMP subagents. PATHWORKS, Advanced Server, and DECnet over TCP/IP The HP TCP/IP Services for OpenVMS product includes the PATHWORKS IP (PWIP) driver and the PWIP ancillary control process (PWIP_ACP) for improved PATHWORKS/Advanced Server and TCP/IP integration. The PWIP driver allows communication between OpenVMS systems running both PATHWORKS Advanced Server or Advanced Server for OpenVMS, and TCP/IP Services software, and personal computers running PATHWORKS 32 client software. It also enables the DECnet-over-TCP/IP feature, which is in- cluded with the DECnet-Plus for OpenVMS. (For more information, see the DECnet-Plus for OpenVMS documentation.) 14 HP TCP/IP Services for OpenVMS Version 5.4 SPD 46.46.17 INSTALLATION AND CONFIGURATION System managers install the HP TCP/IP Services for OpenVMS product us- ing the POLYCENTER Software Installation utility. A menu-driven con- figuration procedure makes it easy to enable either all components and services or only those needed. HARDWARE REQUIREMENTS Supported Processors The HP TCP/IP Services for OpenVMS product supports central process- ing units (CPUs) running OpenVMS. For a complete list of hardware prod- ucts, see the SPD for the specific OpenVMS operating system release. Required Network Controllers The HP TCP/IP Services for OpenVMS software supports all network de- vices listed in the Software Product Description for the OpenVMS Op- erating System for Alpha and VAX systems (SPD 25.01.xx). The HP TCP/IP Services for OpenVMS software can share an Ethernet in- terface with other HP networking products such as DECnet-Plus for OpenVMS. Memory Requirements The following table shows the minimum amount of memory required for the HP TCP/IP Services for OpenVMS product under the client or server license. ___________________________________________________________________ System___________Minimum_Memory____________________________________ OpenVMS_Alpha____32_MB_____________________________________________ 15 HP TCP/IP Services for OpenVMS Version 5.4 SPD 46.46.17 Disk Space Requirements The approximate amount of space required on the system disk to sup- port the HP TCP/IP for OpenVMS software under the client or server li- cense is as follows. Actual sizes may vary depending on the system en- vironment, configuration, and software options. ___________________________________________________________________ System_________________Free_Blocks_Required________________________ OpenVMS_Alpha__________125,000_____________________________________ CLUSTER SUPPORT The HP TCP/IP Services for OpenVMS product is fully supported when in- stalled on any valid and licensed OpenVMS Cluster configuration. SOFTWARE REQUIREMENTS To qualify for a software support contract, the HP TCP/IP Services for OpenVMS Version 5.4 product requires one of the following OpenVMS op- erating system versions: o OpenVMS Alpha, Version 7.3-1 o OpenVMS Alpha, Version 7.3-2 Client access requires a system that supports the protocols specified by NFS Version 2 or Version 3, and all TCP/IP application protocols defined by the TCP/IP Request for Comments (RFCs). For Systems Running XDMCP: DECwindows Motif for OpenVMS, Version 1.2- 5 (or later) GROWTH CONSIDERATIONS The minimum hardware and software requirements for any future version of the HP TCP/IP Services for OpenVMS product may be different from the minimum requirements for the current version. 16 HP TCP/IP Services for OpenVMS Version 5.4 SPD 46.46.17 DISTRIBUTION MEDIA Media and documentation for the HP TCP/IP Services for OpenVMS prod- uct are available on the HP CD-ROM Software Library for OpenVMS. o To order the HP CD-ROM Software Library for OpenVMS for Alpha sys- tems, use order number QA-03XAA-H8. o To order the HP CD-ROM Software Library for OpenVMS for VAX sys- tems, use order number QA-5G88A-H8. ORDERING INFORMATION HP TCP/IP Services for OpenVMS Alpha Server Software Licenses: QL-0LXA*-** Software Documentation: QA-0LXAA-GZ Software Product Services: QT-0LXA*-** HP TCP/IP Services for OpenVMS Alpha Client Software Licenses: QL-0M2A*-** Software Documentation: QA-0LXAA-GZ Software Product Services: QT-0M2A*-** HP TCP/IP Services for OpenVMS Alpha Client Upgrade Software License: QL-0PHA*-** Software Documentation: QA-0LXAA-GZ Software Product Services: QT-0PHA*-** HP TCP/IP Services for OpenVMS VAX Server Software Licenses: QL-VHRA*-** Software Media: QA-VHRAA-H* Software Documentation: QA-VHRAA-GZ Software Product Services: QL-VHRA*-** HP TCP/IP Services for OpenVMS VAX Client Software Licenses: QL-GL7A*-** Software Documentation: QA-VHRAA-GZ 17 HP TCP/IP Services for OpenVMS Version 5.4 SPD 46.46.17 Software Product Services: QT-GL7A*-** HP TCP/IP Services for OpenVMS VAX Client Upgrade Software License: QL-OPJA*-** Software Documentation: QA-VHRAA-GZ Software Product Services: QT-OPJA*-** * Denotes variant fields. For additional information about available licenses, services, and media, refer to the appropriate price book. This ordering information was valid at the time of release. Con- tact your HP representative for current ordering information. SOFTWARE LICENSING This software is furnished under license only. For more information about HP licensing terms and policies, contact your HP representative. The client license provides complete product functionality except for the following server components: NFS server, BIND server, PC-NFS server, the remote BOOT server, the DHCP server, and the RMT/RCD server. License Management Facility Support The HP TCP/IP Services for OpenVMS product supports the OpenVMS Li- cense Management Facility (LMF). For information about the License Management Facility, see the soft- ware product description for the OpenVMS operating system for Alpha and VAX systems (SPD 25.01.xx), or consult the OpenVMS documentation. SOFTWARE WARRANTY This software is provided by HP with a 90-day conformance warranty in accordance with the HP warranty terms applicable to the license pur- chase. 18 HP TCP/IP Services for OpenVMS Version 5.4 SPD 46.46.17 SOFTWARE PRODUCT SERVICES A variety of service options are available from HP. For detailed in- formation about the service options, contact your local HP office. The product information in this SPD was valid at time of release. For current product information, contact your local HP office. © 2003 Hewlett-Packard Development Company, L.P. Microsoft[R] is a US registered trademark of Microsoft Corporation. UNIX[R] is a registered trademark of The Open Group. 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. Proprietary 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. 19 HP TCP/IP Services for OpenVMS Version 5.4 SPD 46.46.17 20