       DESCRIPTION  G  DEC TCP/IP Services for OpenVMS VAX is a layered software product that H  provides interoperability and resource sharing between OpenVMS VAX sys-F  tems, UNIX[R] systems, and other systems that support the TCP/IP Pro--  tocol Suite and Sun[R] Microsystems NFS[TM].   F  The DEC TCP/IP Services for OpenVMS VAX product provides network fileH  access, remote terminal access, remote command execution, remote print-F  ing, mail, and application development. DEC TCP/IP Services for Open-8  VMS VAX has previously been identified by the name UCX.  
  NEW FEATURES   D  DEC TCP/IP Services for OpenVMS has the new features highlighted in  the following list:  F  o  NFS Client VMS-to-VMS - The Network File System (NFS) Protocol al-F     lows a user to access remote host file system as if it were local.G     With NFS Client functionality, OpenVMS users mount NFS files stored F     on remote OpenVMS hosts as if they were local OpenVMS files. UsersG     can execute typical file actions such as create/delete, read/write,      and set attributes.   E  o  SLIP/CSLIP - SLIP/CSLIP allows users to connect host-to-host over C     a serial line. The serial line type may be dialup or dedicated.   ?  o  Network Time Protocol (NTP) - NTP synchronizes time stamps.   2  o  UCX$TRACE - The UCX$TRACE Utility is enhanced.    INSTALLATION AND CONFIGURATION   G  The DEC TCP/IP Services for OpenVMS VAX V3.3 product is installed with   VMSINSTAL.   I  For configuration ease, DEC TCP/IP Services for OpenVMS provides a menu- F  driven configuration procedure. This procedure enables you to config-D  ure only those services and applications that you use. You can also  D                                DIGITAL                    APRIL 1995  D                                                          AE-ME49G-TE       G  configure all client software components quickly without selecting in-   dividual menu options.     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)  E  DEC TCP/IP Services for OpenVMS also includes the functionality dis- %  cussed in the following subsections.   0  Fiber Distributed Data Interface (FDDI) Support  E  FDDI is an ANSI standard for a network technology based on fiber op- D  tics. This technology specifies a 100MPS transmission rate. DEC TCPI  /IP Services for OpenVMS VAX enables TCP/IP communications between Open- E  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   E  OpenVMS VAX hosts act as Internet gateways 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 <  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.  E  The DEC TCP/IP Services for OpenVMS VAX implementation of inetd does   the following:   E  o  Listens for incoming connection requests and appropriately starts      application services.   D  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  J  The BIND Server translates Domain Name System host names to IP addresses.H  Network managers set up BIND databases to configure primary, secondary,D  and caching servers on OpenVMS VAX hosts. This complements the BINDG  resolver, the client part of BIND that requests name-to-address trans-   lations from a BIND server.    Remote Booting   E  Remote host booting of diskless clients uses OpenVMS VAX as the boot G  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.   #                                   3        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.3 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.     -  SRI QIO interface /     Provides emulation of the SRIQIO interface.   $  -  Sun RPC, with XDR and PortmapperG     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)  #                                   4        G  FTP is the internet application protocol for file transfer. It enables 2  users to transfer files to and from remote hosts.  
  o  TELNET  H  TELNET is the internet application protocol for remote login. This pro-D  tocol enables OpenVMS VAX users to log in to remote systems and re--  mote users to log in to OpenVMS VAX systems.   F  TELNET provides support for both character and line modes and enables,  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-E  mote login rlogin, remote shell rsh, and remote executive rexec ser-   vices.   F  Like TELNET, rlogin enables users to log in to remote systems and re--  mote users to log in to OpenVMS VAX systems.   E  The rsh service enables OpenVMS VAX users to execute commands on re- E  mote systems and remote users to execute DCL commands on OpenVMS VAX F  systems. Authentication is based on either user password or proxy ac-  cess.  G  The rexec service provides authentication for the remote command based   on user names and passwords.     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.  #                                   5        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.    o  Network File System (NFS)   F  The NFS software supports the V2.0 protocol specifications. NFS is anF  application layer protocol that provides clients with transparent ac-  cess 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  G     o  Access to files that are compatible with the UNIX operating sys- 
        tem  D  The NFS client software allows interactive users and local applica-F  tions to access files that physically reside on a remote host running  the NFS server software.   
  Automount  F  As implemented in DEC TCP/IP Services for OpenVMS VAX, the /AUTOMOUNTE  qualifier of the MOUNT command transparently mounts and unmounts NFS H  file systems on an as-needed basis, especially useful for mounting file6  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.  #                                   6          PC-NFS Server  E  Remote PC users mount and access NFS files from OpenVMS VAX. UID/GID H  identification and authentication of the remote PC user are establishedG  through the use of the UCX Proxy Database. Once access is established, 3  users can print via the PC-NFS printing mechanism.     PATHWORKS Integration  J  DEC TCP/IP Services for OpenVMS VAX V3.3 supports the PATHWORKS IP driverH  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  2            VAX 8200, VAX 8250, VAX 8300, VAX 8350,2            VAX 8500, VAX 8530, VAX 8550, VAX 8600,2            VAX 8650, VAX 8700, VAX 8800, VAX 8810,2            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:  D  VAX-11/725, VAX-11/730, VAX-11/782, MicroVAX I, VAXstation I, VAXs-  tation 8000      #                                   9        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:  +     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.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). B     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.  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               8,100   Global sections            42)  Disk space required for    18,000 blocks 
  installation     #                                  10          )  Disk space required for    17,000 blocks   use (permanent)  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 details 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 for=  OpenVMS VAX requires OpenVMS 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:   E  For VMS V5.5 or later or OpenVMS 6.0 or later operating systems, the F  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        D  For more information on OpenVMS classes and tailoring, refer to theF  OpenVMS Operating System Software Product Description (SPD 25.01.42).    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 MEDIAc  .  9-track 1600 BPI Magtape, TK50 Streaming Tape  I  This product is also available as part of the OpenVMS Consolidated Soft-n+  ware Distribution on CD-ROM (QA-VWJ8X-A8).     ORDERING INFORMATIONp  "  DEC TCP/IP Client for OpenVMS VAX  "     Software Licenses: QL-GL7A*-**'     Software Documentation: QA-VHRAA-GZn*     Software Product Services: QT-GL7A*-**  $  DEC TCP/IP Services for OpenVMS VAX  "     Software Licenses: QL-VHRA*-**     Software Media: QA-VHRAA-H*s'     Software Documentation: QA-VHRAA-GZh*     Software Product Services: QT-VHRA*-**    DEC TCP/IP Client Upgrade  !     Software License: QL-0PJA*-**s'     Software Documentation: QA-VHRAA-GZ *     Software Product Services: QT-0PJA*-**  G  *  Denotes variant fields. For additional information on available li-oD     censes, services, and media refer to the appropriate price book.  #                                  12e w  e    SOFTWARE LICENSINGt  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.r  %  License Management Facility Support:t  D  This layered product supports the OpenVMS License Management Facil-  ity.T  D  License units for this product are allocated on an Unlimited System  Use basis.s  E  For more information about the License Management Facility, refer tosI  the OpenVMS Operating System Software Product Description (SPD 25.01.42)dH  or the License Management Facility manual of the OpenVMS Operating Sys-  tem documentation set.     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 Warrantyt
  Addendum.                      #                                  13          APPENDIX An  E  The NFS component of DEC TCP/IP Services for OpenVMS has been testedl1  for interoperability with the following systems:P    o  OpenVMS VAX and OpenVMS AXP     o  Sun Microsystems SunOS    o  Hewlett-Packard[R] HP[R]-UXT    o  IBM[R] AIX[R]e    o  Apple[R] A/UX[R]  &  o  Santa Cruz Operations SCO[TM] UNIX    o  DEC UNIX, DEC OSF/ULTRIX  D  Digital supports connectivity with these clients, but does not sup-'  port the operating systems themselves.t  G  The above information is valid at time of release. Please contact yourr:  local Digital office for the most up-to-date information.  A  [R] AIX and IBM are registered trademarks of International Busi-n      ness Machines Corporation.s  @  [R] A/UX and Apple are registered trademarks of Apple Computer,	      Inc.O  ;  [R] Hewlett-Packard and HP-UX are registered trademarks of       Hewlett-Packard Company.   ?  [R] NFS and Sun are registered trademarks of Sun Microsystems,/	      Inc.k  B  [R] UNIX is a registered trademark in the United States and otherA      countries, licensed exclusively through X/Open Company, Ltd.   A  [TM] Network Computing Systems is a trademark of Hewlett-Packardt
      Company.o  7  [TM] SCO is a trademark of Santa Cruz Operations, Inc.w  #                                  14e a  y    D  [TM] The DIGITAL Logo, Alpha AXP, AXP, DEC, DECmcc, DECnet, DEC OSFA      /ULTRIX, DECstation, DECwindows, DEC UNIX, Digital, OpenVMS,dA      PATHWORKS, TURBOchannel, VAX, VAXcluster, VMScluster, and VTs5      are trademarks of Digital Equipment Corporation.   &   1995 Digital Equipment Corporation.    All rights reserved.                                                               #                                  15 