      Software Product  Description   C ___________________________________________________________________   C PRODUCT NAME:   Compaq TCP/IP Services for OpenVMS Version 5.1  SPD  46.46.14   DESCRIPTION   D The Compaq TCP/IP Services for OpenVMS software product is the Open-E VMS implementation of the industry-standard TCP/IP protocol suite and E internet services for OpenVMS Alpha and OpenVMS VAX systems. The ker- H nel software is ported from Compaq Tru64 UNIX Version 5.1 product, whichE is based on the Berkeley Software Distribution (BSD) Versions 4.3 and 8 4.4, with enhancements from Compaq Computer Corporation.  D Internetworking with TCP/IP hides the hardware details of each indi-G vidual network and allows computers to communicate independent of their C physical network connections. Internetworking uses a uniform set of D protocols to define behavior on an internet for all nodes using sup-E ported network media. TCP/IP provides both a standard transport mech- H anism and full-duplex, reliable, stream communication services for soft- ware applications.   Features  G The features of the Compaq TCP/IP Services for OpenVMS product include:   D o  Support for the following network hardware configurations: Ether-F    net, Fiber Distributed Data Interface (FDDI), Token Ring, and asyn-4    chronous transfer mode (ATM; Alpha systems only).  H o  A Berkeley Internet Name Domain (BIND) name server and resolver basedC    on the Internet Software Consortium's (ISC) BIND 8.1.2 plus many E    features from 8.2, including BIND server cluster failover and DHCP     dynamic updates to BIND.   F o  Load broker cluster load balancing, round-robin scheduling, and im-     proved failover capabilities.  C                                                          March 2001   C                                                         AE-Q088L-TE        ? o  SNMP Version 2, ported from the Compaq Tru64 UNIX code base.   C o  A choice of DCL-style or UNIX style management commands for con- D    figuring and managing the network connections and the TCP/IP Ser-    vices software.  F o  Application programming interfaces (APIs) for developing customizedE    applications: $QIO, SRI $QIO, standard C sockets and C sockets li- 1    brary (BSD V4.3 and V4.4), ONC RPC, and eSNMP.   F o  Troubleshooting tools, including error messages that display on theC    screen or print to log files; the Trace utility (TCPTRACE); BIND D    server load balancing and NSLOOKUP debugging; and management com-2    mands to isolate problems and tune performance.  H o  FTP support for long file names, deep directories, and extended char-4    acter sets (OpenVMS extended file specification).  F o  Enhanced Gateway Routing Daemon (GATED) based on GateD Unicast Ver--    sion 4.0.6, with advanced routing options.   D o  Path MTU for TCP and UDP for calculating the most efficient means)    of transporting data across a network.   C o  Classless Inter-domain Routing (CIDR), which reduces routing ta- =    bles and makes more efficient use of the IP address space.   E o  Easy, fast installation using the POLYCENTER Software Installation     utility.   E o  A flexible configuration process that includes an interactive con-     figuration procedure.  E o  Multiple adapters per subnet, which provides load-balanced connec- )    tions resulting in greater throughput.   C o  Support for Internet Protocol Version 6 (IPv6) for customers who F    want to start using IPv6 today or for those who want to test or ex-    periment with IPv6.  F o  NFS enhancements (including support for Versions 2 and 3), NFS over)    TCP and UDP, and improved performance.   "                                  2       E o  SMTP antiSPAM relay, support for SFF (Send From File), and support     for outbound alias.  B o  DHCP (Dynamic Host Control Protocol) client and server support.  C o  Restartable services provides startup and shutdown files for in- D    dividual services, which allows system managers to stop and startE    individual services without impairing the operation of the remain-      ing TCP/IP Services software.  F o  Metric server enhancements, including dynamic configuration of log-E    ical names, which may be defined for CPU rating, compute interval, C    and debug level; enhanced logging processes to include more mes- F    sages; and more information provided with the messages; support forH    multihomed systems to allow load balancing of incoming traffic across    multiple IP addresses.   F o  XDM terminal support for network displays, such as X terminals. TheH    login server supports the X Display Manager Control Protocol (XDMCP),H    which allows display devices to request that the login server present    a login screen.   Licenses  D The following Compaq TCP/IP Services for OpenVMS licenses are avail- able:   C ___________________________________________________________________ C License__________Description_______________________________________   B Client           For customers who require only client components,A                  such as FTP, LPD, TELNET, SNMP, NTP, NFS client, @                  Metric Server, POP, FINGER, RLOGIN, REXEC, RSH,                  and RMT/RCD.             "                                  3         C ___________________________________________________________________   A Server           For customers who require full product function- A                  ality, this license enables all functionality in A                  the product. This includes all the client compo- A                  nents, 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-C _________________ity.______________________________________________    Network Interface Layer Support   C With support for multiple network interfaces for each physical net- D work controller, the Compaq TCP/IP Services for OpenVMS software al-D lows OpenVMS systems to connect to individual host computers on dif- ferent types of networks:    o  Ethernet for IPv4 and IPv6   < o  Fiber Distributed Data Interface (FDDI) for IPv4 and IPv6  
 o  Token Ring   8 o  Asynchronous transfer mode (ATM) (Alpha systems only)  C Individual host computers can also connect with other hosts or net- C works over serial communications lines using either the Serial Line F Internet Protocol (SLIP or CSLIP) or the Point-to-Point Protocol (PPP). (OpenVMS Alpha Version 7.1 and Version 7.2-1).   Internet Layer Support  C The Compaq TCP/IP Services for OpenVMS product supports the follow- C ing Internet layer protocols that work together to move data around 
 the internet:   D o  Internet Protocol (IP) - a connectionless packet delivery service    for IPv4 and IPv6.   "                                  4       G o  Internet Control Message Protocol (ICMP) - provides diagnostic func- B    tions and handles error and control messages for IPv4 and IPv6.  E o  Address Resolution Protocol (ARP) - dynamically maps an IP address +    to a physical hardware address for IPv4.   D o  Neighbor Discovery - dynamically maps an IP address to a physical    hardware address for IPv6.   G o  Routing protocols and routing daemons - enables gateways to exchange F    current routing information about hosts and directly connected net-&    works. Supported protocols include:  E    -  Routing Information Protocol (RIP) Version 1 (RFC 1058) and RIP ,       Version 2 (RFC 1388) for IPv4 and IPv6  :    -  Open Shortest Path First (OSPF) Version 2 (RFC 1583)  /    -  Exterior Gateway Protocol (EGP) (RFC 904)   @    -  Border Gateway Protocol (BGP) (RFC 1163 RFC 1267 RFC 1654)                                      "                                  5       3    -  Router Discovery (RFC 1256) for IPv4 and IPv6   C The routing daemons ROUTED and GATED communicate with the kernel to 6 add new routes or to delete or modify existing routes.   Transport Layer Support   C To provide either connection-oriented or connectionless data trans- C mission between two hosts (local or remote), the Compaq TCP/IP Ser- D vices for OpenVMS product supports both TCP and UDP protocols. TheseC protocols form the bridge between the Application layer and the In- 
 ternet layer:   G o  Transmission Control Protocol (TCP) - provides reliable, connection- F    oriented, sequenced data transfers for applications that must guar-    antee delivery of the data.  D o  User Datagram Protocol (UDP) - provides fast, connectionless dataD    transfers for applications that do not require delivery confirma-    tion.  E This release supports the features documented in RFC 1323, including:   E o  SACK (Selective Acknowledgments), which supports multiple acknowl- E    edgment windows and allows outstanding acknowledgments even if se- #    quence numbers are not in order.   E o  PAWS (Protection Against Wrapped Sequence) numbers, which supplies C    time stamps on transactions to prevent wrapped sequence numbers.   E o  TCP Window Scale, which provides window scale factors for TCP con-     nections.                "                                  6        Application Layer Support   D The Compaq TCP/IP Services for OpenVMS product supports numerous Ap-6 plication layer protocols that allow OpenVMS users to:  ! o  Run software on remote systems   7 o  Transfer data files between local and remote systems   F o  Share remote system resources such as disk storage space and print-D    ers as if they were directly connected to the user's local system  I o  Send and receive electronic mail messages locally or across the world-     wide Internet  F o  Provide consistent, reliable, and efficient network services to all    users on the internet   Remote Computing  C 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   D o  Support for window sizing (rows and columns) and location options  F The popular UNIX Remote commands, called R commands, let OpenVMS usersG work in accounts on remote internet hosts that are either UNIX or Open- E VMS systems. The Compaq TCP/IP Services for OpenVMS software supports - the RLOGIN, RSH, REXEC, and RMT/RCD commands.   F The Finger utility enables users to obtain information about each userD on local or remote systems. This information includes user name, ac-0 count name, and the program the user is running.  "                                  7       
 File Transfer   J OpenVMS users transfer data files between local and remote systems through$ the use of the following components:  @ o  File Transfer Protocol (FTP) - transfers files between hosts.  I o  Trivial File Transfer Protocol (TFTP) - downloads and transfers files.   H o  The remote copy (rcp) command - copies files to or from remote hosts.  D FTP supports extended file specifications (long file names, deep di-8 rectories, and extended character sets) for ODS-5 disks.   Resource Sharing  G The Compaq TCP/IP Services for OpenVMS software provides network print- C ing services through the line printer/line printer daemon (LPR/LPD) * and the TELNET print symbiont (TELNETSYM).  D o  LPD provides remote printing services for UNIX and OpenVMS clientE    hosts through local and remote print queues. Once the print queues C    are set up by the system manager, OpenVMS client users issue the G    DCL command PRINT and UNIX client users typically issue the lpr com-     mand.  H o  TELNETSYM provides remote print services that enable the use of stan-=    dard OpenVMS printing features not available with LPR/LPD.   D With the Network File System (NFS) server software, NFS client usersF gain transparent access to remote file services. With NFS, when a userC accesses files and directories from a remote system, they appear to C reside on the local system regardless of operating system, hardware D type, or architectural differences between the local and remote sys-K tems. The PC-NFS daemon provides authentication services to PC-NFS clients.   D This release provides support for NFS Version 2 and Version 3, basedC on the Compaq Tru64 UNIX Version 5.1 protocols. It responds to both H the NFS Version 2 and Version 3 protocols. The main benefit is increasedC maximum file size - up to 1 terabyte for an OpenVMS file system and   "                                  8       E up to 4 gigabytes for a container file system. This release also pro- E vides NFS support over both TCP and UDP. NFS over TCP allows file ac- D cess over wide area links. Performance gains may result from the im-E provements to file size processing and the enhanced write performance F that allows the NFS server to acknowledge a write operation before theD files are actually written to disk. Afterward, the server's responseD to a commit message confirms that the data has been written to disk.  D The NFS component of the Compaq TCP/IP Services for OpenVMS softwareE has been tested for interoperability and connectivity with clients of  the following systems:      Sun Microsystems SunOS     Hewlett-Packard HP-UX
    IBM AIX
    Apple A/UX      Santa Cruz Operation SCO UNIX   Electronic Mail   E With the Simple Mail Transfer Protocol (SMTP), OpenVMS users can send C and receive electronic mail to and from local and remote hosts. The H Compaq TCP/IP Services for OpenVMS implementation of SMTP uses the Open-F VMS Mail facility, which automatically recognizes an SMTP host address  in the format smith@widgets.com.  D This release supports antiSPAM relay for SMTP mail, which provides aC mechanism for controlling whether the OpenVMS server is used to re- C lay mail. This allows you to prevent the system from being used for F SPAM transmissions. It also includes support for SFF (Send-From-File),F which provides the ability to create a mail message in a file and sendC it to the SMTP mailer to be delivered with headers you specify, and E support for the specification of an outbound alias that is applied to D mail as it is sent and that specifies the network address to which a reply will be sent.   C The SMTP server works with the Post Office Protocol (POP) server to D provide a reliable mail service. With POP as the mail repository, PCD clients are assured that mail is accepted even when the PC is turned off.  "                                  9        Network Services  E With the following Compaq TCP/IP Services for OpenVMS management com- F ponents, network and system managers can provide consistent, reliable,@ and efficient services to their users with minimal interruption:  F o  Simple Network Management Protocol (SNMP) Version 2 includes a mas-C    ter agent and subagents that allow the OpenVMS system to be man- E    aged by a management station on the network. This version includes D    the same features found in the Compaq Tru64 UNIX SNMPv2 implemen-!    tation and other improvements.   E o  Network Time Protocol (NTP) Version 3 provides a means to synchro- F    nize time and coordinate time distribution throughout a TCP/IP net-D    work. NTP aims to provide accurate and dependable timekeeping for    hosts on TCP/IP networks.  F o  Berkeley Internet Name Domain (BIND) is a distributed database sys-E    tem that distributes and manages host information so that hosts do D    not need to locally manage the address of every other host on theC    internet. This version is based on the Internet Software Consor- F    tium's (ISC) BIND 8.1.2 implementation and includes dynamic updatesD    and BIND server cluster failover, which allows multiple BIND mas-E    ter servers to share a common database, thus providing both redun- E    dancy and a failover mechanism when one of the servers becomes un- 
    available.   F o  Portmapper is a database system that allocates ports so system man-G    agers do not need to preconfigure client applications with port num-     bers for each service.   C o  Auxiliary server process is the Compaq TCP/IP Services for Open- C    VMS implementation of the UNIX internet daemon inetd. The auxil- D    iary server greatly simplifies application writing, manages over-F    head by reducing simultaneous server processes, provides system se-H    curity through authentication of service requests, and supports event    and error logging.s      "                                 10 E  I  D o  Dynamic Host Configuration Protocol (DHCP) and the Bootstrap Pro-D    tocol (BOOTP). The DHCP protocol is a superset of BOOTP. In addi-C    tion to BOOTP functionality (answering bootstrap requests), DHCP.C    offers robust configuration services, including IP address, sub- E    net masks, and default gateways. The DHCP server can be configuredrC    to support BOOTP clients. If BOOTP is enabled without DHCP, DHCPo"    functionality is not available.  F DHCP dynamically updates BIND using a feature that allows DHCP clientsC to be configured with a registered name. DHCP uses this name to as- D sign an address when it updates the BIND database. In addition, thisC release offers both a DHCP client and server, which provides a cen-pD tralized approach to the configuration and maintenance of IP addressC space. With DHCP server, the system manager can provide dynamic al-e. location of IP addresses from an OpenVMS host.   Management Control Program  C The Compaq TCP/IP Services for OpenVMS product provides the Manage-tC ment Control Program, which is a comprehensive, easy-to-use networkdD management tool that includes over 100 OpenVMS style commands. TheseC commands let system managers configure and monitor the product com-  ponents locally.   UNIX Management Commands  D The Compaq TCP/IP Services for OpenVMS product provides UNIX manage-E ment commands for system managers experienced in managing a UNIX net-uF work subsystem. Supported commands include: ifconfig, netstat, syscon-D fig, route, arp, ping, traceroute, and ripquery. Note that some UNIX* flags and parameters may not be supported.   Error Message Documentation   D The Compaq TCP/IP Services for OpenVMS product provides improved er-E ror messages from previous versions. Message documentation for a num-oE ber of TCP/IP Services components is available on line as part of thet& OpenVMS Help Message utility (MSGHLP).    "                                 11 f  d  ) Application Programming Interfaces (APIs)S  C The Compaq TCP/IP Services for OpenVMS product provides the follow-V< ing APIs for programmers to develop customized applications:  D o  Standard C Sockets and C Sockets Library provide UNIX like accessD    to TCP, UDP, and raw IP to applications written in the C program-    ming language.d  D o  The $QIO interface extends the OpenVMS system services for socketD    communications, providing access to TCP, UDP, and IP for applica--    tions written in any programming language.i  D o  The SRI $QIO interface translates older, incompatible $QIO inter-    faces into $QIO interfaces.  C o  ONC RPC provides an industry-standard, portable API for program-nF    mers who do not have an in-depth knowledge of networking protocols.D    This is an efficient alternative to application development using    sockets.   F o  Extensible Simple Network Management Protocol (eSNMP) provides rou-%    tines for building SNMP subagents.s   o  Basic IPv6 APIs.     PATHWORKS and DECnet over TCP/IP  E The Compaq TCP/IP Services for OpenVMS product includes the PATHWORKSlF IP (PWIP) driver and PWIP ancillary control process (PWIP_ACP) for im-( proved PATHWORKS and TCP/IP integration.  D The PWIP driver makes possible communication between OpenVMS systemsD running both PATHWORKS server and TCP/IP Services software, and per-F sonal computers running PATHWORKS client software. It also enables theF DECnet-over-TCP/IP feature, which is included with the DECnet-Plus forF OpenVMS Version 6.0 and later software. (For more information, see the' DECnet-Plus for OpenVMS documentation.)     "                                 12 c  s   INSTALLATION AND CONFIGURATION  D System managers install the Compaq TCP/IP Services for OpenVMS prod-E uct using the POLYCENTER Software Installation utility. A menu-drivenpE configuration procedure makes it easy to enable either all componentsh# and services, or only those needed.f   HARDWARE REQUIREMENTSr   Supported Processors  D The Compaq TCP/IP Services for OpenVMS product supports central pro-F cessing units (CPUs) running OpenVMS Versions 7.1, 7.2, 7.2-1, or 7.3.F For a complete list of hardware products, see the SPD for the specific! OpenVMS operating system release.l   Required Network Controllers  D The Compaq TCP/IP Services for OpenVMS software supports all networkC devices listed in the OpenVMS Operating System Software Product De-l scription (SPD 41.87.xx).D  C The Compaq TCP/IP Services for OpenVMS software can share an Ether-eC net interface with other Compaq networking products such as DECnet-e Plus for OpenVMS.n   Memory Requirementss  C The following table shows the minimum amount of memory required for_I the Compaq TCP/IP Services for OpenVMS product under the client or server_ license.  C ___________________________________________________________________oC System___________Minimum_Memory____________________________________M   OpenVMS VAX      32 MB  C OpenVMS_Alpha____64_MB_____________________________________________     "                                 13        Disk Space Requirements   C The approximate amount of space required on the system disk to sup-_F port the Compaq TCP/IP for OpenVMS software under the client or serverD license is as follows. Actual sizes may vary depending on the system1 environment, configuration, and software options.   C ___________________________________________________________________FC System_________________Free_Blocks_Required________________________    OpenVMS Alpha          90,000   C OpenVMS_VAX____________60,000______________________________________r   CLUSTER SUPPORT_  F The Compaq TCP/IP Services for OpenVMS product is fully supported whenB installed on any valid and licensed OpenVMS Cluster configuration.   SOFTWARE REQUIREMENTSt  F To qualify for a software support contract, the Compaq TCP/IP ServicesC for OpenVMS product requires the following OpenVMS operating system  version:  / o  For OpenVMS VAX systems, Versions 7.1 or 7.2   3 o  For OpenVMS Alpha systems, Versions 7.1 or 7.2-1n  E Client access requires a system that supports the protocols specifiedsC by NFS Version 2 or Version 3, and all TCP/IP application protocolso2 defined by the TCP/IP Request for Comments (RFCs).  D For Systems Running XDMCP: DECwindows Motif Version 1.2-5 (or later)            "                                 14 i  7   GROWTH CONSIDERATIONS   E The minimum hardware and software requirements for any future versionsG of the Compaq TCP/IP Services for OpenVMS product may be different fromm1 the minimum requirements for the current version.t   DISTRIBUTION MEDIA  H Media and documentation for the Compaq TCP/IP Services for OpenVMS prod-C uct are available on the Compaq CD-ROM Software Library for OpenVMSPD (QA-03XAA-H8). You can order a printed documentation set separately.   ORDERING INFORMATION  ( Compaq TCP/IP Services for OpenVMS Alpha  !    Software Licenses: QL-0LXA*-** &    Software Documentation: QA-0LXAA-GZ)    Software Product Services: QT-0LXA*-**a  / Compaq TCP/IP Services for OpenVMS Alpha Client   !    Software Licenses: QL-0M2A*-**d&    Software Documentation: QA-0LXAA-GZ)    Software Product Services: QT-0M2A*-**o  7 Compaq TCP/IP Services for OpenVMS Alpha Client Upgrader       Software License: QL-0PHA*-**&    Software Documentation: QA-0LXAA-GZ)    Software Product Services: QT-0PHA*-**f  & Compaq TCP/IP Services for OpenVMS VAX  !    Software Licenses: QL-VHRA*-**     Software Media: QA-VHRAA-H*&    Software Documentation: QA-VHRAA-GZ)    Software Product Services: QL-VHRA*-**5    "                                 15       - Compaq TCP/IP Services for OpenVMS VAX Clientt  !    Software Licenses: QL-GL7A*-**I&    Software Documentation: QA-VHRAA-GZ)    Software Product Services: QT-GL7A*-**e  5 Compaq TCP/IP Services for OpenVMS VAX Client Upgradep       Software License: QL-OPJA*-**&    Software Documentation: QA-VHRAA-GZ)    Software Product Services: QT-OPJA*-**l  E *  Denotes variant fields. For additional information about availablerF    licenses, services, and media, refer to the appropriate price book.C    This ordering information was valid at the time of release. Con- D    tact your Compaq representative for current ordering information.   SOFTWARE LICENSING  C This software is furnished under license only. For more information C about Compaq licensing terms and policies, contact your Compaq rep-  resentative.  E The client license provides complete product functionality except forrH 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 Supportn  C The Compaq TCP/IP Services for OpenVMS product supports the OpenVMS " License Management Facility (LMF).  D For information about the License Management Facility, see the Open-C VMS Operating System Software Product Description (SPD 41.87.xx) ore the OpenVMS documentation.          "                                 16        SOFTWARE WARRANTY   F This software is provided by Compaq with a 90-day conformance warrantyF in accordance with the Compaq warranty terms applicable to the license	 purchase.e   SOFTWARE PRODUCT SERVICESr  D A variety of service options are available from Compaq. For detailedD information about the service options, contact your local Compaq of- fice.   E The product information in this SPD was valid at time of release. For > current product information, contact your local Compaq office.  "  2001 Compaq Computer Corporation  C COMPAQ, VAX, VMS, and the Compaq logo Registered in U.S. Patent ands Trademark Office.   C OpenVMS and Tru64 are trademarks of Compaq Information Technologieso5 Group, L.P. in the United States and other countries.   C All other product names mentioned herein may be trademarks of theiri respective companies.o  F Confidential computer software. Valid license from Compaq required forC possession, use, or copying. Consistent with FAR 12.211 and 12.212,XH Commercial Computer Software, Computer Software Documentation, and Tech-C nical Data for Commercial Items are licensed to the U.S. GovernmentT+ under vendor's standard commercial license.e  E Compaq shall not be liable for technical or editorial errors or omis-uD sions contained herein. The information in this document is providedC "as is" without warranty of any kind and is subject to change with-eC out notice. The warranties for Compaq products are set forth in the E express limited warranty statements accompanying such products. Noth-eF ing herein should be construed as constituting an additional warranty.    "                                 17 r  f                                                                                  "                                 18