     	  Software   Product  Description  D  ___________________________________________________________________  D  PRODUCT NAME:  DEC TCP/IP Services for                 SPD 25.A4.05(                 OpenVMS VAX, Version 3.1    DESCRIPTION  F  The DEC TCP/IP Services for OpenVMS VAX product is a layered softwareD  product that provides interoperability and resource sharing betweenE  OpenVMS VAX systems, UNIX[R] systems, and other systems that support =  the TCP/IP Protocol Suite, and Sun[R] Microsystems' NFS[TM].   G  The DEC TCP/IP Services for OpenVMS VAX (TCP/IP) product provides net- D  work file access, remote terminal access, remote command execution,D  remote printing, mail, and application development. DEC TCP/IP Ser-@  vices for OpenVMS VAX is also identified by the acronymn "UCX".  	  FEATURES     Installation and Configuration G  The DEC TCP/IP Services for OpenVMS VAX V3.1 product is installed with   VMSINSTAL.   D  For configuration ease, the DEC TCP/IP Services for OpenVMS productG  provides a menu-driven configuration procedure. This procedure enables D  you to configure only those services and applications that you use.H  It also enables you to configure all client software components quickly+  without selecting individual menu options.               D                                DIGITAL                      May 1994  D                                                          AE-ME49F-TE         Communications   D  Communications are based on the 4.3 Berkeley Software Distribution,3  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)    o  Ethernet support    o  FDDI support  F  o  Auxiliary (AUX) Server (inetd), plus enhancements such as security     and event logging   0  Fiber Distributed Data Interface (FDDI) Support  E  FDDI is an ANSI standard for a network technology based on fiber op- G  tics. It specifies a 100-megabit-per-second transmission rate. DEC TCP D  /IP Services for OpenVMS VAX allows OpenVMS VAX systems to take ad-H  vantage of this technology by enabling TCP/IP communications with other  hosts in these configurations:     o  On the same FDDI network    o  Over a FDDI/Ethernet bridge     o  Over a router   F  OpenVMS VAX hosts are also able to act as an Internet gateway between)  FDDI networks and one or more Ethernets.   D  The management of the FDDI controller is integrated with the TCP/IP  network management interface.  #                                   2          Auxiliary Server inetd   E  The inetd software is the TCP/IP service dispatcher for UNIX systems F  which was first provided by Berkeley Software Distribution (BSD) 4.3.  F  This feature significantly simplifies the writing of applications andD  manages overhead by reducing the number of simultaneous server pro-  cesses on the system.  A  The DEC TCP/IP Services for OpenVMS VAX implementation of inetd:   E  o  Listens for incoming connection requests and appropriately starts E     application services. It 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.                                         #                                   3          BIND Server  G  Translates Domain Name System host names to IP addresses. Network man- J  agers set up a BIND database to configure primary, secondary, and cachingF  servers on OpenVMS VAX hosts. This complements the BIND resolver, theD  client part of BIND that requests name-to-address translations from  a BIND server.     Remote Booting   F  Remote host booting of diskless clients using OpenVMS VAX as the bootG  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   F  UCX Management provides DCL-style commands to control and monitor the  UCX software components.   0  Simple Network Management Protocol (SNMP) Agent  G  SNMP is the internet standard protocol for network management over TCP F  /IP. The SNMP agent communicates with network management directors toF  provide information about network activity. MIB II variables are sup-  ported within SNMP.  $  Security and Network Access Control  D  System managers use network security features to control the acces-<  sibility to OpenVMS VAX systems from remote Internet hosts.  #  Application Programming Interfaces   D  DEC TCP/IP Services for OpenVMS VAX V3.1 includes the following ap-"  plication programming interfaces:  "  -  C socket programming interfaceE     Provides the Berkeley socket programming interface to develop TCP 2     /IP networking applications in the C language.    -  QIO programming interface E     Provides a QIO programming interface to develop TCP/IP networking -     applications in any OpenVMS VAX language.   #                                   4          -  SRIQIO interface/     Provides emulation of the SRIQIO interface.   #  -  SunRPC, with XDR and Portmapper G     Sun[R] Remote Procedure Calls (SunRPC) are included in the UCX Pro- D     gramming interface. The SunRPC library includes a library of RPCF     function calls, the Portmapper module, and eXternal Data Represen-     tation (XDR) routines.  
  Applications   J  This component includes the widespread end-user protocols for file trans-H  fer, remote login, remote command processing, remote printing, and mail
  exchange.     o  File Transfer Protocol (FTP)  G  FTP is the internet application protocol for file transfer. It enables 2  users to transfer files to and from remote hosts.  
  o  Telnet  E  Telnet is the internet application protocol for remote login. It en- D  ables OpenVMS VAX users to log into remote systems and remote users!  to log into OpenVMS VAX systems.   G  Telnet provides support for both character and line modes. It also en- 2  ables users to activate multiple Telnet sessions.    o  Telnet 3270   F  Telnet 3270 enables users to make Telnet connections from OpenVMS VAXD  systems to remote IBM[R] systems using a 3270-style terminal inter-  face.  1  o  Berkeley Remote Commands (rlogin, rsh, rexec)   D  DEC TCP/IP Services for OpenVMS VAX implements the popular UNIX re-F  mote login (rlogin), remote shell (rsh), and remote executive (rexec)
  services.  D  Like Telnet, remote login (rlogin) enables users to log into remote:  systems and remote users to log into OpenVMS VAX systems.  #                                   5        D  Rsh enables OpenVMS VAX users to execute commands on remote systemsE  and remote users to execute DCL commands on OpenVMS VAX systems. Au- ?  thentication is based on either user password or proxy access.     o  Remote printing   I  DEC TCP/IP Services for OpenVMS VAX provides the following remote print-   ing services:  D  OpenVMS VAX users can issue DCL-style PRINT commands to print files*  on remote systems using the LPD protocol.  E  Similarly, remote users can print files on OpenVMS VAX systems using   the LPD protocol.  H  OpenVMS VAX users can also use the TELNET Print Symbiont to print files  on remote systems.   (  o  Simple Mail Transfer Protocol (SMTP)  G  SMTP is the internet application protocol for mail. Users can send and 2  receive electronic mail to and from remote hosts.    Network File System  F  The NFS[TM] software supports the Network File System (NFS) V2.0 pro-E  tocol specifications. NFS is an application layer protocol that pro- ?  vides clients with transparent access to remote file services.   D  The NFS server software promotes data sharing among clients by pro-G  viding a central data storage facility for OpenVMS VAX and UNIX files. E  The NFS server software provides two types of file access for remote 	  clients:     o  Access to OpenVMS VAX files   D  o  Access to files that are compatible with the UNIX Operating Sys-     tem.    #                                   6        
  Automount  E  As implemented in DEC TCP/IP Services for OpenVMS VAX, the NFS AUTO- D  MOUNT command transparently mounts and unmounts NFS file systems onD  an as-needed basis, especially useful for mounting file systems and*  directories that are occasionally needed.    File Conversion On-The-Fly   F  Maximizes interoperability between OpenVMS VAX and other systems uti-D  lizing the NFS Protocol by providing a sequential "read on-the-fly"  file conversion capability.    PC-NFS Server  E  Remote PC users mount and access NFS files from OpenVMS VAX. UID/GID G  identification and authentication of the remote PC user is established G  through the use of the UCX Proxy Database. Once access is established, 3  users can print via the PC-NFS printing mechanism.     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 200             VAX 4000 Model 300             VAX 4000 Model 500             VAX 4000 Model 600             VAX 4000 Model 700   $            VAX 6000 Model 200 Series    #                                   7          $            VAX 6000 Model 300 Series$            VAX 6000 Model 400 Series$            VAX 6000 Model 500 Series$            VAX 6000 Model 600 Series              VAX 9000 Model 110             VAX 9000 Model 210 $            VAX 9000 Model 300 Series$            VAX 9000 Model 400 Series  1            VAX 8200, VAX 8250, VAX 8300, VAX 8350 1            VAX 8500, VAX 8530, VAX 8550, VAX 8600 1            VAX 8650, VAX 8700, VAX 8800, VAX 8810 '            VAX 8820, VAX 8830, VAX 8840   -            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 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,$            VAXstation 3100 Model 76,,            VAXstation 3200, VAXstation 3500,+            VAXstation 3520, VAXstation 3540         #                                   8          $            VAXstation 4000 Model 60,$            VAXstation 4000 Model 90,            VAXstation 4000 VLC  )  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     Processors Not Supported   D  VAX-11/725, VAX-11/730, VAX-11/782, MicroVAX I, VAXstation I, VAXs-  tation 8000  E  For performance reasons, Digital does not recommend using a MicroVAX ,  2000 or any VAXstation as an NFS[R] server.    Other Hardware Required:   8  One of the following controller interfaces is required:  #                                   9          +     DEUNA    Ethernet to UNIBUS controller. @     DELUA    Ethernet to UNIBUS controller. The minimum revision"              level required is F1.8     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. 8     DEBNA    Ethernet to VAXBI communication controller.?     DEQNA    Ethernet controller to Q-bus. The minimum revision               required is K3.B     DELQA    Ethernet controller to Q-bus. This is the replacementB              for DEQNA. The minimum revision level required is C3.C     DESQA    Ethernet controller to Q-bus for S-BOX configurations. 3     SGEC     Ethernet adapter for VAX 4000 systems. ;     DEMFA    DEC FDDI Controller 400 (XMI-to-FDDI Adapter). A     DEFTA    The DEFTA is a high-performance network adapter that C              connects TURBO-channel systems to ANSI FDDI local area               networks.A     DEMNA    The DEMNA is a high-performance network adapter that ?              connects XMI systems to both the Ethernet and IEEE '              802.3 local area networks.   E  DEC TCP/IP Services for OpenVMS can share an Ethernet Interface with 3  other Digital networking products, such as DECnet.   1  Disk Space Requirements (Block Cluster Size = 1)   %  For DEC TCP/IP Services for OpenVMS:   !  Global Pages               1,970   Global Sections            287  Disk space required for    7,000 blocks (3,500 Kbytes)   installation:7  Disk space required for    6,000 blocks (3,000 Kbytes)   use (permanent):       #                                  10        F  These counts refer to the disk space required on the system disk. TheE  sizes are approximate; actual sizes may vary depending on the user's 9  system environment, configuration, and software options.     CLUSTER ENVIRONMENT  D  This layered product is fully supported when installed on any validG  and licensed VAXcluster* configuration without restrictions. The HARD- F  WARE REQUIREMENTS section of this product's Software Product Descrip-;  tion detail any special hardware required by this product.   E  *  V5.x and 6.x VAXcluster configurations are fully described in the F     VAXcluster Software Product Description (29.78.xx) and include CI,4     Ethernet, and Mixed Interconnect configurations.    SOFTWARE REQUIREMENTS  D  To qualify for a software support contract, DEC TCP/IP Services for5  OpenVMS requires VMS Operating System V6.0 or later.   D  Client access to DEC TCP/IP Services for OpenVMS requires a UNIX[R]G  Operating System that supports the protocols specified by NFS V2.0 and G  all applicable TCP/IP protocols as defined by the Request for Comments   (RFC).     OpenVMS Tailoring:   D  For VMS V5.x or 6.0 systems, the following VMS classes are required0  for full functionality of this layered product:    o  VMS Required Saveset    o  Programming Support   ;  o  BLISS Required Files (optional for program development)   D  For more information on VMS classes and tailoring, refer to the VMS>  Operating System Software Product Description (SPD 25.01.xx).    #                                  11          GROWTH CONSIDERATIONS  F  The minimum hardware and software requirements for any future versionD  of this product may be different from the requirements for the cur-  rent version.    DISTRIBUTION MEDIA   .  9-track 1600 BPI Magtape, TK50 Streaming Tape  E  This product is also available as part of the VMS 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-0PHA*-** '     Software Documentation: QA-VHRAA-GZ *     Software Product Services: QT-0PHA*-**  G  *  Denotes variant fields. For additional information on available li- E     censes, services, and media, refer to the appropriate price book.         #                                  12          SOFTWARE LICENSING   F  This software is furnished only under a license. For more informationF  about Digital's licensing terms and policies, contact your local Dig-
  ital office.   %  License Management Facility Support:5  C  This layered product supports the VMS License Management Facility.e  D  License units for this product are allocated on an Unlimited System  Use basis.v  E  For more information about the License Management Facility, refer to E  the VMS Operating System Software Product Description (SPD 25.01.xx)SD  or the License Management Facility manual of the VMS Operating Sys-  tem documentation set.r    SOFTWARE PRODUCT SERVICES  F  A variety of service options are available from Digital. For more in-.  formation, contact your local Digital office.    SOFTWARE WARRANTY  H  Warranty for this software product is provided by Digital with the pur-G  chase of a license for the product as defined in the Software Warranty 
  Addendum.                        #                                  13D T  I    APPENDIX AO  E  The NFS component of DEC TCP/IP Services for OpenVMS has been testedc1  for interoperability with the following systems:e    Sun Microsystems SunOS     Hewlett-Packard[R] HP[R]-UX    IBM[R] AIX[R]    Apple[R] A/UX[R]q  #  Santa Cruz Operations SCO[TM] UNIXe  D  Digital supports connectivity with these clients, but does not sup-'  port the operating systems themselves.   G  The above information is valid at time of release. Please contact youra:  local Digital office for the most up-to-date information.  A  [R] AIX and IBM are registered trademarks of International Busi-s      ness Machines Corporation.o  @  [R] A/UX and Apple are registered trademarks of Apple Computer,	      Inc.o  A  [R] Hewlett-Packard and HP are registered trademarks of Hewlett-g      Packard Company.o  ?  [R] NFS and Sun are registered trademarks of Sun Microsystems, 	      Inc.t  @  [R] UNIX is a registered trademark of Unix System Laboratories,4      Inc., a wholly-owned subsidiary of Novell, Inc.  A  [TM] Network Computing Systems is a trademark of Hewlett-Packardr
      Company.s  7  [TM] SCO is a trademark of Santa Cruz Operations, Inc.o  #                                  14r e  o    B  [TM] The Digital Logo, CI, DEC, DECmcc, DECnet, DELUA, DEQNA, DE-C      UNA, MicroVAX, OpenVMS, Q-bus, TK, ULTRIX, UNIBUS, VAX, VAXBI,sA      VAXcluster, VAXft, VAXserver, VAXstation, and VMS are trade-D,      marks of Digital Equipment Corporation.  ;   1994 Digital Equipment Corporation. All rights reserved.t                                                                  #                                  15d