DESCRIPTION DEC TCP/IP Services for OpenVMS VAX is a layered software product that provides interoperability and resource sharing between OpenVMS VAX sys- tems, UNIX[R] systems, and other systems that support the TCP/IP Pro- tocol Suite and Sun[R] Microsystems NFS[TM]. The DEC TCP/IP Services for OpenVMS VAX product provides network file access, remote terminal access, remote command execution, remote print- ing, mail, and application development. DEC TCP/IP Services for Open- VMS VAX has previously been identified by the name UCX. NEW FEATURES DEC TCP/IP Services for OpenVMS has the new features highlighted in the following list: o NFS Client VMS-to-VMS - The Network File System (NFS) Protocol al- lows a user to access remote host file system as if it were local. With NFS Client functionality, OpenVMS users mount NFS files stored on remote OpenVMS hosts as if they were local OpenVMS files. Users can execute typical file actions such as create/delete, read/write, and set attributes. o SLIP/CSLIP - SLIP/CSLIP allows users to connect host-to-host over a serial line. The serial line type may be dialup or dedicated. o Network Time Protocol (NTP) - NTP synchronizes time stamps. o UCX$TRACE - The UCX$TRACE Utility is enhanced. INSTALLATION AND CONFIGURATION The DEC TCP/IP Services for OpenVMS VAX V3.3 product is installed with VMSINSTAL. For configuration ease, DEC TCP/IP Services for OpenVMS provides a menu- driven configuration procedure. This procedure enables you to config- ure only those services and applications that you use. You can also DIGITAL APRIL 1995 AE-ME49G-TE configure all client software components quickly without selecting in- dividual menu options. COMMUNICATIONS Communications are based on the 4.3 Berkeley Software Distribution, implementing the following protocols and features: o Transmission Control Protocol (TCP) o Internet Protocol (IP) o Internet Control Message Protocol (ICMP) o Address Resolution Protocol (ARP) o User Datagram Protocol (UDP) o Routing Information Protocol (RIP) DEC TCP/IP Services for OpenVMS also includes the functionality dis- cussed in the following subsections. Fiber Distributed Data Interface (FDDI) Support FDDI is an ANSI standard for a network technology based on fiber op- tics. This technology specifies a 100MPS transmission rate. DEC TCP /IP Services for OpenVMS VAX enables TCP/IP communications between Open- VMS VAX systems and other hosts that are in the following configura- tions: o On the same FDDI network o Over a FDDI/Ethernet bridge o Over a router OpenVMS VAX hosts act as Internet gateways between FDDI networks and one or more Ethernets. The management of the FDDI controller is integrated with the TCP/IP network management interface. 2 Auxiliary Server (inetd) The inetd software is the TCP/IP service dispatcher for UNIX systems first provided by Berkeley Software Distribution (BSD) 4.3. This feature significantly simplifies the writing of applications and manages overhead by reducing the number of simultaneous server pro- cesses on the system. The DEC TCP/IP Services for OpenVMS VAX implementation of inetd does the following: o Listens for incoming connection requests and appropriately starts application services. o Controls dynamic process creation in the same manner as the UNIX based inetd. o Provides a Services Database. o Provides security features. o Offers event logging. BIND Server The BIND Server translates Domain Name System host names to IP addresses. Network managers set up BIND databases to configure primary, secondary, and caching servers on OpenVMS VAX hosts. This complements the BIND resolver, the client part of BIND that requests name-to-address trans- lations from a BIND server. Remote Booting Remote host booting of diskless clients uses OpenVMS VAX as the boot server. This feature uses the BOOTP and TFTP Protocols to initiate the boot request and to download the boot files. UCX Management with Command-Line Interface UCX Management provides DCL-style commands to control and monitor the UCX software components. 3 Simple Network Management Protocol (SNMP) Agent SNMP is the internet standard protocol for network management over TCP /IP. The SNMP agent communicates with network management directors to provide information about network activity. MIB II variables are sup- ported within SNMP. Security and Network Access Control System managers use network security features to control the acces- sibility to OpenVMS VAX systems from remote Internet hosts. Application Programming Interfaces DEC TCP/IP Services for OpenVMS VAX V3.3 includes the following ap- plication programming interfaces: - C socket programming interface Provides the Berkeley socket programming interface to develop TCP /IP networking applications in the C language. - QIO programming interface Provides a QIO programming interface to develop TCP/IP networking applications in any OpenVMS VAX language. - SRI QIO interface Provides emulation of the SRIQIO interface. - Sun RPC, with XDR and Portmapper Sun[R] Remote Procedure Calls (SunRPC) are included in the UCX Pro- gramming interface. The SunRPC library includes a library of RPC function calls, the Portmapper module, and eXternal Data Represen- tation (XDR) routines. Applications This component includes the widespread end-user protocols for file trans- fer, remote login, remote command processing, remote printing, and mail exchange. o File Transfer Protocol (FTP) 4 FTP is the internet application protocol for file transfer. It enables users to transfer files to and from remote hosts. o TELNET TELNET is the internet application protocol for remote login. This pro- tocol enables OpenVMS VAX users to log in to remote systems and re- mote users to log in to OpenVMS VAX systems. TELNET provides support for both character and line modes and enables users to activate multiple TELNET sessions. o TELNET 3270 TELNET 3270 enables users to make TELNET connections from OpenVMS VAX systems to remote IBM[R] systems using a 3270-style terminal inter- face. o Berkeley Remote Commands (rlogin, rsh, rexec) DEC TCP/IP Services for OpenVMS VAX implements the popular UNIX re- mote login rlogin, remote shell rsh, and remote executive rexec ser- vices. Like TELNET, rlogin enables users to log in to remote systems and re- mote users to log in to OpenVMS VAX systems. The rsh service enables OpenVMS VAX users to execute commands on re- mote systems and remote users to execute DCL commands on OpenVMS VAX systems. Authentication is based on either user password or proxy ac- cess. The rexec service provides authentication for the remote command based on user names and passwords. o Remote Printing DEC TCP/IP Services for OpenVMS VAX provides the following remote print- ing services: OpenVMS VAX users can issue DCL-style PRINT commands to print files on remote systems using the LPD protocol. Similarly, remote users can print files on OpenVMS VAX systems using the LPD protocol. 5 OpenVMS VAX users can also use the TELNET Print Symbiont to print files on remote systems. o Simple Mail Transfer Protocol (SMTP) SMTP is the internet application protocol for mail. Users can send and receive electronic mail to and from remote hosts. o Network File System (NFS) The NFS software supports the V2.0 protocol specifications. NFS is an application layer protocol that provides clients with transparent ac- cess to remote file services. The NFS server software promotes data sharing among clients by pro- viding a central data storage facility for OpenVMS VAX and UNIX files. The NFS server software provides two types of file access for remote clients: o Access to OpenVMS VAX files o Access to files that are compatible with the UNIX operating sys- tem The NFS client software allows interactive users and local applica- tions to access files that physically reside on a remote host running the NFS server software. Automount As implemented in DEC TCP/IP Services for OpenVMS VAX, the /AUTOMOUNT qualifier of the MOUNT command transparently mounts and unmounts NFS file systems on an as-needed basis, especially useful for mounting file systems and directories that are occasionally needed. File Conversion On-The-Fly Maximizes interoperability between OpenVMS VAX and other systems uti- lizing the NFS Protocol by providing a sequential "read on-the-fly" file conversion capability. 6 PC-NFS Server Remote PC users mount and access NFS files from OpenVMS VAX. UID/GID identification and authentication of the remote PC user are established through the use of the UCX Proxy Database. Once access is established, users can print via the PC-NFS printing mechanism. PATHWORKS Integration DEC TCP/IP Services for OpenVMS VAX V3.3 supports the PATHWORKS IP driver for improved PATHWORKS and TCP/IP integration. (Requires PATHWORKS Ver- sion 5 series.) HARDWARE REQUIREMENTS Processors Supported: VAX: VAXft Model 110, VAXft Model 310, VAXft Model 410, VAXft Model 610, VAXft Model 612, VAXft Model 810 VAX 4000 Model 100, VAX 4000 Model 200, VAX 4000 Model 300, VAX 4000 Model 500, VAX 4000 Model 600, VAX 4000 Model 700 VAX 6000 Model 200 Series, VAX 6000 Model 300 Series, VAX 6000 Model 400 Series, VAX 6000 Model 500 Series, VAX 6000 Model 600 Series 7 VAX 7000-600 Series VAX 9000 Model 110, VAX 9000 Model 210, VAX 9000 Model 300 Series, VAX 9000 Model 400 Series VAX 8200, VAX 8250, VAX 8300, VAX 8350, VAX 8500, VAX 8530, VAX 8550, VAX 8600, VAX 8650, VAX 8700, VAX 8800, VAX 8810, VAX 8820, VAX 8830, VAX 8840, VAX 8842, VAX 8974, VAX 8978 VAX 10000-600 Series, VAX 10000-700 Series VAX-11/750, VAX-11/780, VAX-11/785 MicroVAX: MicroVAX II, MicroVAX 2000, MicroVAX 3100 Model 10/10E, MicroVAX 3100 Model 20/20E, MicroVAX 3100 Model 30, MicroVAX 3100 Model 40, MicroVAX 3100 Model 80, MicroVAX 3100 Model 90, MicroVAX 3300, MicroVAX 3400, MicroVAX 3500, MicroVAX 3600, MicroVAX 3800, MicroVAX 3900 VAXstation:VAXstation II, VAXstation 2000, VAXstation 3100 Model 30, VAXstation 3100 Model 38, VAXstation 3100 Model 40, VAXstation 3100 Model 48, 8 VAXstation 3100 Model 76, VAXstation 3200, VAXstation 3500, VAXstation 3520, VAXstation 3540 VAXstation 4000 Model 60, VAXstation 4000 Model 90, VAXstation 4000 VLC, VAXstation 8000 VAXserver VAXserver 3100, VAXserver 3300, VAXserver 3400, VAXserver 3500, VAXserver 3600, VAXserver 3602, VAXserver 3800, VAXserver 3900 VAXserver 4000 Model 200, VAXserver 4000 Model 300, VAXserver 4000 Model 500 VAXserver 6000 Model 210 VAXserver 6000 Model 220, VAXserver 6000 Model 310, VAXserver 6000 Model 320, VAXserver 6000 Model 410, VAXserver 6000 Model 420, VAXserver 6000 Model 510, VAXserver 6000 Model 520, VAXserver 6000 Model 610, VAXserver 6000 Model 620, VAXserver 6000 Model 630 VAXserver 9000 Series Processors Not Supported: VAX-11/725, VAX-11/730, VAX-11/782, MicroVAX I, VAXstation I, VAXs- tation 8000 9 For performance reasons, Digital does not recommend using a MicroVAX 2000 or any VAXstation as an NFS[R] server. Other Hardware Required One of the following controller interfaces is required: DEUNA Ethernet to UNIBUS controller. DELUA Ethernet to UNIBUS controller. The minimum revision level required is F1. DEBNI Ethernet to VAXBI communication controller. DEMNA High performance network adapter that connects XMI systems to both Ethernet and IEEE 802.3 local area networks. DESVA Ethernet controller interface. DEBNA Ethernet to VAXBI communication controller. DELQA Ethernet controller to Q-bus. This is the replacement for DEQNA. The minimum revision level required is C3. DESQA Ethernet controller to Q-bus for S-BOX configurations. SGEC Ethernet adapter for VAX 4000 systems. DEMFA DEC FDDI Controller 400 (XMI-to-FDDI Adapter). DEFTA High-performance network adapter that connects TURBO- channel systems to ANSI FDDI local area networks. DEMNA High-performance network adapter that connects XMI systems to both Ethernet and IEEE 802.3 local area networks. DEC TCP/IP Services for OpenVMS can share an Ethernet Interface with other Digital networking products, such as DECnet. Disk Space Requirements (Block Cluster Size = 1) For DEC TCP/IP Services for OpenVMS: Global pages 8,100 Global sections 42 Disk space required for 18,000 blocks installation 10 Disk space required for 17,000 blocks use (permanent) These 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. CLUSTER ENVIRONMENT This layered product is fully supported when installed on any valid and licensed VAXcluster* configuration without restrictions. The HARD- WARE REQUIREMENTS section of this product's Software Product Descrip- tion details any special hardware required by this product. * V5.x and 6.x VAXcluster configurations are fully described in the VAXcluster Software Product Description (29.78.xx) and include CI, Ethernet, and Mixed Interconnect configurations. SOFTWARE REQUIREMENTS To qualify for a software support contract, DEC TCP/IP Services for OpenVMS VAX requires OpenVMS operating system V6.0 or later. Client access to DEC TCP/IP Services for OpenVMS requires a UNIX[R] operating system that supports the protocols specified by NFS V2.0 and all applicable TCP/IP protocols as defined by the Request for Comments (RFC). OpenVMS Tailoring: For VMS V5.5 or later or OpenVMS 6.0 or later operating systems, the following OpenVMS classes are required for full functionality of this layered product: o OpenVMS Required Saveset o Programming Support o BLISS Required Files (optional for program development) 11 For more information on OpenVMS classes and tailoring, refer to the OpenVMS Operating System Software Product Description (SPD 25.01.42). GROWTH CONSIDERATIONS The minimum hardware and software requirements for any future version of this product may be different from the requirements for the cur- rent version. DISTRIBUTION MEDIA 9-track 1600 BPI Magtape, TK50 Streaming Tape This product is also available as part of the OpenVMS Consolidated Soft- ware Distribution on CD-ROM (QA-VWJ8X-A8). ORDERING INFORMATION DEC TCP/IP Client for OpenVMS VAX Software Licenses: QL-GL7A*-** Software Documentation: QA-VHRAA-GZ Software Product Services: QT-GL7A*-** DEC TCP/IP Services for OpenVMS VAX Software Licenses: QL-VHRA*-** Software Media: QA-VHRAA-H* Software Documentation: QA-VHRAA-GZ Software Product Services: QT-VHRA*-** DEC TCP/IP Client Upgrade Software License: QL-0PJA*-** Software Documentation: QA-VHRAA-GZ Software Product Services: QT-0PJA*-** * Denotes variant fields. For additional information on available li- censes, services, and media refer to the appropriate price book. 12 SOFTWARE LICENSING This software is furnished only under a license. For more information about Digital's licensing terms and policies, contact your local Dig- ital office. License Management Facility Support: This layered product supports the OpenVMS License Management Facil- ity. License units for this product are allocated on an Unlimited System Use basis. For more information about the License Management Facility, refer to the OpenVMS Operating System Software Product Description (SPD 25.01.42) or the License Management Facility manual of the OpenVMS Operating Sys- tem documentation set. SOFTWARE PRODUCT SERVICES A variety of service options are available from Digital. For more in- formation, contact your local Digital office. SOFTWARE WARRANTY Warranty for this software product is provided by Digital with the pur- chase of a license for the product as defined in the Software Warranty Addendum. 13 APPENDIX A The NFS component of DEC TCP/IP Services for OpenVMS has been tested for interoperability with the following systems: o OpenVMS VAX and OpenVMS AXP o Sun Microsystems SunOS o Hewlett-Packard[R] HP[R]-UX o IBM[R] AIX[R] o Apple[R] A/UX[R] o Santa Cruz Operations SCO[TM] UNIX o DEC UNIX, DEC OSF/ULTRIX Digital supports connectivity with these clients, but does not sup- port the operating systems themselves. The above information is valid at time of release. Please contact your local Digital office for the most up-to-date information. [R] AIX and IBM are registered trademarks of International Busi- ness Machines Corporation. [R] A/UX and Apple are registered trademarks of Apple Computer, Inc. [R] Hewlett-Packard and HP-UX are registered trademarks of Hewlett-Packard Company. [R] NFS and Sun are registered trademarks of Sun Microsystems, Inc. [R] UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company, Ltd. [TM] Network Computing Systems is a trademark of Hewlett-Packard Company. [TM] SCO is a trademark of Santa Cruz Operations, Inc. 14 [TM] The DIGITAL Logo, Alpha AXP, AXP, DEC, DECmcc, DECnet, DEC OSF /ULTRIX, DECstation, DECwindows, DEC UNIX, Digital, OpenVMS, PATHWORKS, TURBOchannel, VAX, VAXcluster, VMScluster, and VT are trademarks of Digital Equipment Corporation. © 1995 Digital Equipment Corporation. All rights reserved. 15