       DESCRIPTION  2  DEC TCP/IP Services for OpenVMS AXP is a layered  software product that 8  provides interoperability and resource sharing between  OpenVMS AXP sys-7  tems, UNIX[R] systems, and other systems that support   the TCP/IP Pro- -  tocol Suite and Sun[R] Microsystems NFS[TM].   6  DEC TCP/IP Services for OpenVMS AXP provides network  file access, re-8  mote terminal access, remote command execution, remote  printing, mail, 6  and application development. DEC TCP/IP Services for  OpenVMS AXP was '  previously identified by the name UCX.   
  NEW FEATURES   6  DEC TCP/IP Services for OpenVMS has the new features  highlighted in  the following list:  4  o  NFS Client VMS-to-VMS - The Network File System  Protocol allows users 8     to remotely access a host file system as if it were  the users' lo-4     cal file system. With NFS Client functionality,  OpenVMS users mount 8     NFS files stored on remote OpenVMS hosts as if they  were local Open-6     VMS files. Users can execute typical file actions  such as create,     /delete, read/write, and set attributes.  4  o  SLIP/CSLIP - SLIP/CSLIP allows users to connect  host-to-host over 1     a serial line. The serial line may be either   dedicated or dialup.  8  o  Network Time Protocol (NTP) - NTP synchronizes time  stamps.   2  o  UCX$TRACE - The UCX$TRACE Utility is enhanced.    INSTALLATION AND CONFIGURATION   9  The DEC TCP/IP Services for OpenVMS AXP V3.3 product is   installed with  VMSINSTAL.   5  For configuration ease, the DEC TCP/IP Services for   OpenVMS product 6  provides a menu-driven configuration procedure. This  procedure enables 7  you to configure only those services and applications  
 that you use.   9                                DIGITAL                      April 1995   9                                                            AE-Q088C-TE        7  You can also configure all client software components  
 quickly with- '  out selecting individual menu options.     COMMUNICATIONS   7  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)                                          #                                   2        3  DEC TCP/IP Services for OpenVMS also includes the   functionality dis-%  cussed in the following subsections.   0  Fiber Distributed Data Interface (FDDI) Support  9  FDDI is an ANSI standard for a network technology based   on fiber op-7  tics. This technology specifies a 100MPS transmission  
 rate. DEC TCP -  /IP Services for OpenVMS AXP enables TCP/IP   communications between Open-1  VMS AXP 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   6  OpenVMS AXP hosts act as an Internet gateway between  FDDI networks and   one or more Ethernets.   5  The management of the FDDI controller is integrated   with the TCP/IP   network management interface.    Auxiliary Server (inetd)   9  The inetd software is the TCP/IP service dispatcher for   UNIX systems8  first provided by Berkeley Software Distribution (BSD)  4.3.  6  This feature significantly simplifies the writing of  applications and9  manages overhead by reducing the number of simultaneous   server pro-   cesses on the system.  8  The DEC TCP/IP Services for OpenVMS AXP implementation 
 of inetd does   the following:   1  o  Listens for incoming connection requests and   appropriately starts6     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.   #                                   3          o  Offers event logging.     BIND Server  4  The BIND Server translates Domain Name System host  names to IP addresses.6  Network managers set up a BIND database to configure  primary, secondary, 0  and caching servers on OpenVMS AXP hosts. This  complements the BIND1  resolver, the client part of BIND that requests   name-to-address trans-  lations from a BIND server.    Remote Booting   6  Remote host booting of diskless clients uses OpenVMS  AXP as the boot 8  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   7  UCX Management provides DCL-style commands to control   and monitor the   UCX software components.   0  Simple Network Management Protocol (SNMP) Agent  4  SNMP is the internet standard protocol for network  management over TCP /  /IP. The SNMP agent communicates with network   management directors to 4  provide information about network activity. MIB II  variables are sup-  ported within SNMP.  $  Security and Network Access Control  2  System managers use network security features to  control the acces-6  sibility to OpenVMS AXP systems from remote Internet  hosts.  #  Application Programming Interfaces   7  DEC TCP/IP Services for OpenVMS AXP V3.3 includes the  
 following ap- "  plication programming interfaces:  "  -  C socket programming interface7     Provides the Berkeley socket programming interface   to develop TCP2     /IP networking applications in the C language.  #                                   4          -  QIO programming interface 4     Provides a QIO programming interface to develop  TCP/IP networking -     applications in any OpenVMS AXP language.     -  SRI QIO interface /     Provides emulation of the SRIQIO interface.   $  -  Sun RPC, with XDR and Portmapper8     Sun[R] Remote Procedure Calls (SunRPC) are included  in the UCX Pro- 6     gramming interface. The SunRPC library includes a  library of RPC8     function calls, the Portmapper module, and eXternal  Data Represen-     tation (XDR) routines.  
  Applications   7  The UCX components in this section provide widespread  
 end-user pro- 8  tocols for file transfer, remote login, remote command  processing, re- "  mote printing, and mail exchange.     o  File Transfer Protocol (FTP)  3  FTP is the internet application protocol for file   transfer. It enables2  users to transfer files to and from remote hosts.  
  o  TELNET  8  TELNET is the internet application protocol for remote  login. This pro-5  tocol enables OpenVMS AXP users to log in to remote   systems and re- -  mote users to log in to OpenVMS AXP systems.   5  TELNET provides support for both character and line   modes. It also en-2  ables users to activate multiple TELNET sessions.    o  TELNET 3270   6  TELNET 3270 enables users to make TELNET connections  from OpenVMS AXP5  systems to remote IBM[R] systems using a 3270-style   terminal inter-   face.  1  o  Berkeley Remote Commands (rlogin, rsh, rexec)   #                                   5        4  DEC TCP/IP Services for OpenVMS AXP implements the  popular UNIX re-5  mote login (rlogin), remote shell (rsh), and remote   executive (rexec) 
  services.  9  Like TELNET, remote login (rlogin) enables users to log   in to remote3  systems and remote users to log in to OpenVMS AXP   systems.  6  Rsh enables OpenVMS AXP users to execute commands on  remote systems9  and remote users to execute DCL commands on OpenVMS AXP   systems. Au-8  thentication is based on either user password or proxy  access.     o  Remote Printing   2  DEC TCP/IP Services for OpenVMS AXP provides the  following remote print-   ing services:  9  OpenVMS AXP users can issue DCL-style PRINT commands to   print files *  on remote systems using the LPD protocol.  8  Similarly, remote users can print files on OpenVMS AXP 
 systems using   the LPD protocol.  1  OpenVMS AXP users can also use the TELNET Print   Symbiont to print files   on remote systems.   (  o  Simple Mail Transfer Protocol (SMTP)  5  SMTP is the internet application protocol for mail.   Users can send and2  receive electronic mail to and from remote hosts.    Network File System  7  The NFS[TM] software supports the Network File System   (NFS) V2.0 pro- 3  tocol specifications. NFS is an application layer   protocol that pro-6  vides clients with transparent access to remote file 	 services.   5  The NFS server software promotes data sharing among   clients by pro- 8  viding a central data storage facility for OpenVMS AXP  and UNIX files. 4  The NFS server software provides two types of file  access for remote 	  clients:      o  Access to OpenVMS AXP files.  #                                   6        6  o  Access to files that are compatible with the UNIX  operating sys-     tem.  
  Automount  2  DEC TCP/IP Services for OpenVMS AXP uses the NFS  AUTOMOUNT command to5  transparently mount and unmount NFS file systems as   needed. This is 7  useful for mounting file systems and directories that  
 are occasion- 
  ally needed.     File Conversion On-the-Fly   9  This utility maximizes interoperability between OpenVMS  
 AXP and other 2  systems that use the NFS Protocol by providing a  sequential "read on-  the-fly" file converter.     PC-NFS Server  5  Remote PC users mount and access NFS files from NFS   Servers. UID/GID9  identification and authentication of the remote PC user   are established 8  through the use of the UCX Proxy Database. Once access  is established, 3  users can print via the PC-NFS printing mechanism.     PATHWORKS Integration  7  DEC TCP/IP Services for OpenVMS AXP V3.3 supports the   PATHWORKS IP driver 9  for improved PATHWORKS and TCP/IP integration (requires   PATHWORKS Ver-  sion 5 series).    HARDWARE REQUIREMENTS    Processors Supported:    Alpha     DEC 2000 Model 300,  AXP:      DEC 2000 Model 500,%            DEC 2100 Server A500/600MP         #                                   7                      DEC 3000 Model 300,            DEC 3000 Model 300L,             DEC 3000 Model 300X,              DEC 3000 Model 300LX,            DEC 3000 Model 400,            DEC 3000 Model 400S,             DEC 3000 Model 500,            DEC 3000 Model 500S,             DEC 3000 Model 500X,             DEC 3000 Model 600,            DEC 3000 Model 600S,             DEC 3000 Model 800,            DEC 3000 Model 800S              DEC 4000 Model 610,            DEC 4000 Model 620,            DEC 4000 Model 710,            DEC 4000 Model 720               DEC 7000 Model 610,            DEC 7000 Model 620,            DEC 7000 Model 630,            DEC 7000 Model 640               DEC 10000 Model 610,             DEC 10000 Model 620,             DEC 10000 Model 630,             DEC 10000 Model 640    Other Hardware Required  8  One of the following controller interfaces is required:  1  Integral    The Integral Ethernet is a resident   Ethernet communi-   Ethernet    cations system.        #                                   8          5  DEFTA       The DEFTA is a high-performance network   adapter that9              connects TURBO-channel systems to ANSI FDDI  
 local area              networks.  5  DEMFA       The DEMFA is a high-performance network   adapter that5              connects XMI systems to ANSI FDDI local   area networks.4              DEMFA requires microcode rev of 1.4 or  higher.   5  DEMNA       The DEMNA is a high-performance network   adapter that7              connects XMI systems to both the Ethernet   and IEEE'              802.3 local area networks.   9  PMAD        The PMAD is a network adapter that connects  
 TURBOchan-7              nel systems to both the Ethernet and IEEE   802.3 local               area networks.   5  DETRA       Token Ring adapter for TURBOchannel bus.   ,  DW110       Token Ring adapter for ISA bus.  -  DW300       Token Ring adapter for EISA bus.   2  DEC TCP/IP Services for OpenVMS AXP can share an  Ethernet interface9  with other Digital networking products, such as DECnet.   Disk Space Re-$  quirements (Block Cluster Size = 1)       Global pages = 8100      Global sections = 428     Disk space required for installation = 17000 blocks 
 (8700 Kbytes) 4     Disk space required for use (permanent) = 16000  blocks (8200 Kbytes)  6  These counts refer to the disk space required on the  system disk. The8  sizes are approximate; actual sizes may vary depending 
 on the user's 1  system environment, configuration, and software   options.    CLUSTER ENVIRONMENT  8  This layered product is fully supported when installed  on any valid/  and licensed VMScluster configuration without   restrictions. The HARD- 4  WARE REQUIREMENTS section of this Software Product  Description details #  any special hardware requirements.   #                                   9          SOFTWARE REQUIREMENTS  8  To qualify for a software support contract, DEC TCP/IP  Services for OpenVMS9  AXP V3.3 requires the OpenVMS AXP operating system V6.1  	 or later.   6  Client access to DEC TCP/IP Services for OpenVMS AXP 	 requires:   7  A system that supports the protocols specified by NFS   V2.0 and all ap-7  plication TCP/IP protocols defined by the Request for   Comments (RFCs).  8  See Appendix A for a list of compatible client systems.    For Systems Using Terminals:   .  o  OpenVMS AXP Operating System V6.1 or later  %  For Workstations Running DECwindows:   .  o  OpenVMS AXP Operating System V6.1 or later  5  For Workstations Running DECwindows Using Motif[R] :   .  o  OpenVMS AXP Operating System V6.1 or later  4  o  DECwindows Motif V1.1 (or later) for OpenVMS AXP    GROWTH CONSIDERATIONS  8  The minimum hardware and software requirements for any  future version3  of this product may be different from the minimum   requirements for the  current version.   DISTRIBUTION MEDIA   8  Media and documentation for this product are available  on Digital CD-5  ROM Software Library for OpenVMS AXP (QA-03XAA-H8).   Documentation in+  hardcopy format may be ordered separately.         #                                  10          ORDERING INFORMATION   "  DEC TCP/IP Client for OpenVMS AXP  "     Software Licenses: QL-0M2A*-**'     Software Documentation: QA-0LXAA-GZ *     Software Product Services: QT-0M2A*-**  $  DEC TCP/IP Services for OpenVMS AXP  "     Software Licenses: QL-0LXA*-**'     Software Documentation: QA-0LXAA-GZ *     Software Product Services: QT-0LXA*-**    DEC TCP/IP Client Upgrade  !     Software License: QL-0PHA*-** '     Software Documentation: QA-0LXAA-GZ *     Software Product Services: QT-0PHA*-**  7  *  Denotes variant fields. For additional information   on available li-9     censes, services, and media refer to the appropriate   price book. 7     The above information is valid at time of release.   Please contact6     your local Digital office for the most up-to-date  information.    SOFTWARE LICENSING   6  This software is furnished only under a license. For  more information7  about Digital's licensing terms and policies, contact   your local Dig- 
  ital office.   $  License Management Facility Support  7  This layered product supports the OpenVMS AXP License   Management Fa-  cility (LMF).  4  License units for this product are allocated on an  unlimited useba-  sis.     #                                  11        3  For more information about the License Management   Facility, see the /  OpenVMS AXP Operating System Software Product   Description (SPD 41.87.xx)3  or the OpenVMS AXP Operating System documentation.     SOFTWARE PRODUCT SERVICES  1  A variety of service options are available from   Digital. For more in- .  formation, contact your local Digital office.    SOFTWARE WARRANTY  3  Warranty for this software product is provided by   Digital with the pur- 6  chase of a license for the product as defined in the  Software Warranty   Addendum of this SPD.    APPENDIX A   6  The NFS component of DEC TCP/IP Services for OpenVMS  has been tested 7  for interoperability and connectivity with clients of  
 the following 	  systems:     o  Sun MicroSystems SunOS    o  Hewlett Packard[R] HP-UX[R]     o  IBM AIX[R]    o  Apple[R] A/UXD  %  o  Santa Cruz Operation SCO[TM] UNIXe  4  The above information is valid at time of release.  Please contact yourd.  local Digital office for the most up-to-date  information.  8  [R]  Apple and A/UX are registered trademarks of Apple 	 Computer,e
       Inc.        #                                  12s r  e    /  [R]  Hewlett-Packard and HP-UX are registered e trademarks of thet       Hewlett-Packard Company.  2  [R]  IBM and AIX are registered trademark of the 
 International $       Business Machines Corporation.  2  [R]  Motif is a registered trademark of The Open  Software Founda-       tion, Inc.  3  [R]  UNIX is a registered trademark in the United F States and other5       countries, licensed exclusively through X/Open  
 Company, Ltd.c  9  [R]  Sun is a registered trademark of Sun MicroSystems, a Inc.  2  [TM] NFS is a trademark of Sun MicroSystems, Inc.  7  [TM] SCO is a trademark of Santa Cruz Operations, Inc.f  5  [TM] The DIGITAL Logo, Alpha AXP, AXP, DEC, DECmcc, e DECnet, DEC-8       station, DECwindows, Digital, OpenVMS, PATHWORKS, 
 TURBOchan-3       nel, VAX, VAXcluster, VMScluster, and VT are c
 trademarks oft$       Digital Equipment Corporation.  &   1995 Digital Equipment Corporation.    All rights reserved.o                          #                                  13   