               H                     Compaq_TCP/IP_Services_for_OpenVMS__________________!                     Release Notes                           January 2001  D                     This document describes new features and changes?                     to the software; installation, upgrade, and ?                     compatibility information; new and existing D                     software problems and restrictions; and software2                     and documentation corrections.              E                     Revision/Update Information:  These release notes F                                                   supersede the TCP/IPF                                                   Services for OpenVMSF                                                   V5.0A Release Notes.  H                     Software Version:             Compaq TCP/IP ServicesI                                                   for OpenVMS Version 5.1   ?                     Operating Systems:            OpenVMS Alpha E                                                   Versions 7.1, 7.2-1 F                                                   OpenVMS VAX Versions:                                                   7.1, 7.2                        /                     Compaq Computer Corporation "                     Houston, Texas                 N               ________________________________________________________________  0                2001 Compaq Computer Corporation  F               COMPAQ, VAX, VMS, and the Compaq logo Registered in U.S.*               Patent and Trademark Office.  E               DECnet, OpenVMS, PATHWORKS, and Tru64 are trademarks of G               Compaq Information Technologies Group, L.P. in the United )               States and other countries.   H               UNIX is a trademark of The Open Group in the United States"               and other countries.  H               All other product names mentioned herein may be trademarks,               of their respective companies.  G               Confidential computer software. Valid license from Compaq G               required for possession, use, or copying. Consistent with B               FAR 12.211 and 12.212, Commercial Computer Software,E               Computer Software Documentation, and Technical Data for H               Commercial Items are licensed to the U.S. Government under3               vendor's standard commercial license.   C               Compaq shall not be liable for technical or editorial C               errors or omissions contained herein. The information C               in this document is provided "as is" without warranty F               of any kind and is subject to change without notice. TheI               warranties for Compaq products are set forth in the express E               limited warranty statements accompanying such products. C               Nothing herein should be construed as constituting an "               additional warranty.  H               This document was prepared using DECdocument, Version 3.3-               1b.                                  F      _________________________________________________________________  F                                                               Contents      F      Preface...................................................    vii         1  New Features and Changes  F            1.1   Version 5.1 Features..........................    1-1F            1.1.1     New Kernel................................    1-2<            1.1.2     Support for Internet Protocol Version 6F                      (IPv6)....................................    1-4F            1.1.2.1     Name Space Configuration Guidelines.....    1-5F            1.1.2.2     Using the Local Hosts Database..........    1-6?            1.1.2.3     Configuring or Deleting Interfaces Under F                        IPv6....................................    1-6F            1.1.3     GATED Enhancements........................    1-7F            1.1.4     Restartable Services......................    1-7F            1.1.4.1     Obsolete Files..........................    1-8F            1.1.4.2     New Files...............................    1-9>            1.1.4.3     Changes to the TCPIP$CONFIG.COM CommandF                        Procedure...............................   1-11F            1.1.5     BIND Enhancements.........................   1-11F            1.1.5.1     BIND Server Cluster Failover............   1-11F            1.1.5.2     Managing BIND Dynamic Updates...........   1-11F            1.1.6     Updates to SNMP...........................   1-12F            1.1.6.1     Managing the SNMP MIB Browser...........   1-13F            1.1.7     SMTP Features.............................   1-14F            1.1.7.1     SMTP SFF (Send From File)...............   1-14F            1.1.7.1.1    Format of the SFF File.................   1-15F            1.1.7.1.2    SFF File Requirements..................   1-16F            1.1.7.1.3    SFF Security Measures..................   1-17F            1.1.7.1.4    Invoking SFF from an Application.......   1-17F            1.1.7.1.5    Invoking SFF from DCL..................   1-18F            1.1.7.2     SMTP Outbound Alias.....................   1-18F            1.1.7.2.1    Defining the Outbound Alias............   1-18    F                                                                    iii                   @               1.1.7.2.2    Appending the Personal Name String toI                            the Outbound Alias.....................   1-19 I               1.1.7.2.3    Appending a Substitute Domain String...   1-20 5               1.1.7.2.4    Disabling Modifications to I                            TCPIP$SMTP_FROM........................   1-21 ?               1.1.7.2.5    TCPIP$SMTP_FROM and the Return-Path: I                            Header.................................   1-21 I               1.1.7.2.6    X-VMS-True-From: Header................   1-21 I               1.1.7.2.7    Managing Outbound Alias Processing.....   1-21 I               1.1.8     Metric Server Enhancements................   1-22 I               1.1.9     Load Broker Cluster Failover..............   1-23 I               1.1.10    DHCP Dynamically Updates BIND.............   1-24 I               1.1.11    XDM Terminal Support......................   1-25 I               1.1.12    TELNET Client Enhancements................   1-26 I               1.1.13    NFS Server and Client Enhancements........   1-26 I               1.1.13.1    NFS V3 Protocol.........................   1-27 I               1.1.13.2    Extending and Truncating Files..........   1-28 ;               1.1.13.3    NFS Client Reports True Allocated I                           Size....................................   1-28 I               1.1.13.4    MOUNT Retry Default Value...............   1-29 I               1.1.13.5    Network Locking.........................   1-29 I               1.1.13.6    Managing the MOUNT Service..............   1-30 I               1.1.14    DHCP Client Configuration.................   1-30 I               1.1.15    TCP Performance Options...................   1-33 I               1.2   Version 5.1 Changes...........................   1-33 I               1.2.1     Unsupported Management Commands...........   1-33 I               1.2.2     Changes to Management Commands............   1-34 I               1.2.3     Changes to NFS Server Configuration.......   1-35 >               1.2.3.1     Using NFSSTAT to Display StatisticalI                           Information.............................   1-37 >               1.2.3.2     Using SYSCONFIG to Modify NFS ServerI                           Attributes..............................   1-38 >               1.2.3.3     Using SYSCONFIG to Display ParameterI                           Settings................................   1-41 I               1.2.4     TCP/IP Process Names......................   1-41 I               1.2.5     FTP Changes...............................   1-42 I               1.2.5.1     FTP Passive Mode........................   1-42 I               1.2.5.2     FTP Message Enhancement.................   1-42 I               1.2.6     POP Server Threads Configuration..........   1-43 I               1.2.7     LPD Changes...............................   1-43 I               1.2.8     NTP Changes...............................   1-44 I               1.2.9     DHCP Changes..............................   1-45       
         iv                   I               1.2.10    BIND Changes..............................   1-47 I               1.2.10.1    Editable Network Services Database......   1-47 <               1.2.10.2    BIND Server Merges Dynamic UpdatesI                           Automatically...........................   1-49 I               1.2.11    SMTP Changes..............................   1-49 I               1.2.12    Message Improvements......................   1-51 >               1.2.13    Adjusting Interrupt Stack Pages on VAXI                         Systems...................................   1-52 I               1.2.14    TELNET Changes............................   1-53 I               1.2.15    Programming Example Changes...............   1-53 I               1.2.16    SHOW DEVICE Command Changes...............   1-53 I               1.2.17    Server Inactivity Timer Is Not Enforced...   1-54 I               1.3   Version 5.1 Documentation.....................   1-54   9         2  Installation, Configuration, and Startup Notes   I               2.1   Configuring IPv6..............................    2-1 I               2.1.1     Information for Users of the IPv6 EAK.....    2-1 I               2.1.2     Warning Message in TCPIP$CONFIG.COM.......    2-1 I               2.2   Removing Prior Versions of this Product.......    2-2 I               2.2.1     Saving Mail Messages When You Upgrade.....    2-2 I               2.2.2     Upgrading OpenVMS VAX Systems.............    2-2 <               2.3   System Page Table Entries Parameter (VAXI                     Systems Only).................................    2-3 I               2.4   Some UCX Files Remain After Installation......    2-3 @               2.5   Starting the Product After a Minimum OpenVMSI                     Boot..........................................    2-5 7               2.6   Preserving LPD Startup and Shutdown I                     Behavior......................................    2-6 I               2.6.1     OpenVMS Alpha Users.......................    2-6 I               2.6.2     OpenVMS VAX Users.........................    2-7 =               2.6.3     Troubleshooting SMTP and LPD Shutdown I                         Problems..................................    2-7 I               2.6.4     Merging Edits (All Users).................    2-8 I               2.7   SNMP Installation and Setup...................    2-8 I               2.7.1     Verifying the SNMP Installation...........    2-8 <               2.7.2     Preserving SNMP Startup and ShutdownI                         Behavior..................................    2-8 :               2.8   Setting Up the TCP/IP Services MessageI                     Database......................................    2-9 I               2.9   PROXYERROR Messages at Startup................   2-10         I                                                                         v                    $         3  Problems and Restrictions  I               3.1   NFS Problems and Restrictions.................    3-1 I               3.1.1     NFS Lock Requests Fail....................    3-1 I               3.1.2     NFS Client Problems and Restrictions......    3-2 I               3.2   DHCP Client Problems and Restrictions.........    3-2 I               3.3   IPv6 Problems and Restrictions................    3-3 I               3.3.1     IPv6 Proxy Lookup.........................    3-3 I               3.3.2     IPv6 Requires the BIND Resolver...........    3-3 I               3.4   RLOGIN Does Not Create Virtual Terminals......    3-3 I               3.5   TELNET Devices Remain After Shutdown..........    3-3 9               3.6   TELNETSYM Autostart Queues in OpenVMS I                     Clusters......................................    3-4 >               3.7   File Locking Requires Compaq C RTL ECO3 orI                     Higher........................................    3-4 I               3.8   PRODUCT REMOVE TCPIP Error Message............    3-4 I               3.9   Startup DUPLNAM Messages......................    3-5 I               3.10  Security Driver...............................    3-6 I               3.11  Command Restrictions..........................    3-6 I               3.12  NTP Problems and Restrictions.................    3-8 I               3.13  Error Messages................................    3-8 I               3.14  FTP Problems and Restrictions.................    3-8 I               3.14.1    GET/FDL Command...........................    3-8 ?               3.14.2    Extended File Specifications in a Mixed I                         Operating System Environment..............    3-9 I               3.15  DHCP Problems and Restrictions................   3-10 I               3.16  PPP/SLIP Problems and Restrictions............   3-11 I               3.16.1    Running PPP on OpenVMS Version 7.1........   3-11 I               3.16.2    PPPD CONNECT Causes the System to Fail....   3-11 I               3.17  Configuring Your Host as a Dialup Provider....   3-11 I               3.18  RCP Problems and Restrictions.................   3-11 >               3.19  REUSEADDR Behaviour change in V4.2 to V5.xI                     Transition....................................   3-13 I               3.20  POP Problems..................................   3-13 I               3.21  SMTP Problems.................................   3-14 <               3.22  Status Returned by RSH and REXEC CommandI                     Files.........................................   3-15 I               3.23  $QIO Programming..............................   3-15 I               3.24  SNMP Problems.................................   3-15 I               3.24.1    Incomplete Restart........................   3-16 I               3.24.2    SNMP IVP Error............................   3-16 I               3.24.3    Using Existing MIB Subagent Modules.......   3-16 3               3.24.4    Restrictions to RFC-Defined I                         Functionality.............................   3-18   
         vi                   I               3.24.5    SNMP Restrictions and Characteristics.....   3-19 I               3.24.6    Upgrading Requires Restart................   3-24 ?               3.24.7    Communication Controller Data Not Fully I                         Updated...................................   3-24 I               3.24.8    SNMP MIB Browser Usage....................   3-25 I               3.24.9    Duplicate Subagent Identifiers............   3-25 I               3.24.10   Invalid Response to Trap..................   3-25 I               3.25  eSNMP Programming and Subagent Development....   3-25 >               3.26  DIGITAL TCP/IP Services for OpenVMS User'sI                     Guide Problems and Restrictions...............   3-26            4  Corrections  I               4.1   Software Corrections..........................    4-1 I               4.1.1     UCP Problems Fixed Since Last Release.....    4-1 ?               4.1.2     TELNET Server Problems Fixed Since Last I                         Release...................................    4-1 ;               4.1.3     TELNETSYM Problems Fixed Since Last I                         Release...................................    4-2 I               4.1.4     IPC Problems Fixed Since Last Release.....    4-2 I               4.1.5     DHCP Problems Fixed Since Last Release....    4-2 I               4.1.6     POP Problems Fixed Since Last Release.....    4-2 I               4.1.7     SMTP Problems Fixed Since Last Release....    4-2 ?               4.1.8     BIND Resolver Problems Fixed Since Last I                         Release...................................    4-3 <               4.1.9     Management Problems Fixed Since LastI                         Release...................................    4-3 :               4.1.10    PPP/SLIP Problems Fixed Since LastI                         Release...................................    4-5f<               4.1.11    FTP Server Problems Fixed Since LastI                         Release...................................    4-5m<               4.1.12    FTP Client Problems Fixed Since LastI                         Release...................................    4-7n@               4.1.13    Load Balancing Problems Fixed Since LastI                         Release...................................    4-7 I               4.1.14    NTP Problems Fixed Since Last Release.....    4-8 I               4.2   Reported Problems Fixed Since Last Release....    4-8                 I                                                                       viiM e  o                       Tables  I               1         TCP/IP Services Documentation.............   viii   ?               1-1       Displaying Statistical Information with I                         NFSSTAT...................................   1-37   <               1-2       Modifying NFS Server Attributes withI                         SYSCONFIG.................................   1-39   I               2-1       UCX Files Remaining After Installation....    2-3_  <               4-1       Management Problems Fixed Since LastI                         Release...................................    4-8   =               4-2       BIND Server Problems Fixed Since Last I                         Release...................................    4-9p  <               4-3       NFS Client Problems Fixed Since LastI                         Release...................................   4-10T  ?               4-4       TELNET Server Problems Fixed Since LasteI                         Release...................................   4-10r  :               4-5       PPP/SLIP Problems Fixed Since LastI                         Release...................................   4-11   I               4-6       NTP Problems Fixed Since Last Release.....   4-11A                                           viii                             I         _________________________________________________________________a  I                                                                   Prefacem      C               The Compaq TCP/IP Services for OpenVMS product is theoD               Compaq implementation of the TCP/IP protocol suite andA               internet services for OpenVMS Alpha and OpenVMS VAXt               systems.  I               TCP/IP Services provides a comprehensive suite of functions G               and applications that support industry-standard protocols C               for heterogeneous network communications and resource                sharing.  I               For installation instructions, see the manual Compaq TCP/IP B               Services for OpenVMS Installation and Configuration.  I               The release notes provide version-specific information that_F               supersedes the information in the documentation set. TheE               features, restrictions, and corrections in this versioneH               of the software are described in the release notes. AlwaysD               read the release notes before installing the software.           Intended Audience   F               These release notes are intended for experienced OpenVMSF               and UNIX system managers and assumes a working knowledgeE               of OpenVMS system management, TCP/IP networking, TCP/IP2H               terminology, and some familiarity with the TCP/IP Services               product.  >               o  System managers using the POLYCENTER Software%                  Installation utility   ?                  For complete installation information, see the D                  Compaq TCP/IP Services for OpenVMS Installation and&                  Configuration manual.  5               o  Managers of OpenVMS layered productst  (               o  OpenVMS system managers  I                                                                       vii  1  4              !               o  Network managers            Related Documentse  H               Table 1 lists the documents available with this version of               TCP/IP Services.  I         Table_1_TCP/IP_Services_Documentation____________________________   I         Manual____________________Contents_______________________________   A         DIGITAL TCP/IP Services   This manual provides conceptual F         for OpenVMS Concepts and  information about networking and theI         Planning                  TCP/IP protocol including a description E                                   of the Compaq implementation of the F                                   Berkeley Internet Name Domain (BIND)E                                   service and the Network File System E                                   (NFS). It outlines general planning G                                   issues to consider before configuring1H                                   your system to use the TCP/IP Services+                                   software..  H                                   This manual also describes the manualsF                                   in the documentation set, provides aH                                   glossary of terms and acronyms for theG                                   TCP/IP Services software product, and.G                                   documents how to contact the InterNICtB                                   Registration Service to registerI                                   domains and access Request for Comments.)                                   (RFCs).   G         Compaq TCP/IP Services    This text file describes new features.G         for OpenVMS Release       and changes to the software includingTG         Notes                     installation, upgrade, configuration,gF                                   and compatibility information. TheseF                                   notes also describe new and existingI                                   software problems and restrictions, and I                                   software and documentation corrections.   G                                   Print this text file at the beginning H                                   of the installation procedure and readH                                   it before you install TCP/IP Services.  I                                                  (continued on next page)2           viii r  a              I         Table_1_(Cont.)_TCP/IP_Services_Documentation____________________   I         Manual____________________Contents_______________________________   I         Compaq TCP/IP Services    This manual explains how to install and H         for OpenVMS Installation  configure the TCP/IP Services product.         and Configurationa  B         DIGITAL TCP/IP Services   This manual describes how to useA         for OpenVMS User's Guide  the applications available with E                                   TCP/IP Services such as remote file D                                   operations, email, TELNET, TN3270,C                                   and network printing. This manual D                                   explains how to use these servicesH                                   to communicate with systems on privateI                                   internets or on the worldwide Internet.   H         Compaq TCP/IP Services    This manual describes how to configureI         for OpenVMS Management    and manage the TCP/IP Services product.   H                                   Use this manual with the Compaq TCP/IPI                                   Services for OpenVMS Management Command 3                                   Reference manual.   B         Compaq TCP/IP Services    This manual describes the TCP/IP?         for OpenVMS Management    Services management commands..H         Command Reference         Use this manual with the Compaq TCP/IP  I                                   Services for OpenVMS Management manual..  F         Compaq TCP/IP Services    This reference card lists the TCP/IPF         for OpenVMS Management    management commands by component andH         Command Quick Reference   describes the purpose of each command.         Card  >         Compaq TCP/IP Services    This reference card containsF         for OpenVMS UNIX Command  information about commonly performedD         Reference Card            network management tasks and theirE                                   corresponding TCP/IP management and D                                   Compaq Tru64 UNIX command formats.  I                                                  (continued on next page).      I                                                                        ix  e  g              I         Table_1_(Cont.)_TCP/IP_Services_Documentation____________________   I         Manual____________________Contents_______________________________.  E         DIGITAL TCP/IP Services   This manual presents an overview of.C         for OpenVMS ONC RPC       high-level programming using openeD         Programming               network computing remote procedureC                                   calls (ONC RPC). This manual alsovI                                   describes the RPC programming interfaceeD                                   and how to use the RPCGEN protocolB                                   compiler to create applications.  F         Compaq TCP/IP Services    This manual describes how to use theI         for OpenVMS Sockets       Sockets API and OpenVMS system serviceseB         API and System Services   to develop network applications.         Programmingt  B         Compaq TCP/IP Services    This manual describes the SimpleD         for OpenVMS SNMP          Network Management Protocol (SNMP)F         Programming and           and the SNMP application programmingA         Reference                 interface (eSNMP). It describes.D                                   the subagents provided with TCP/IPB                                   Services, utilities provided forF                                   managing subagents, and how to build5                                   your own subagents.   B         Compaq TCP/IP Services    This manual provides informationD         for OpenVMS Tuning and    about how to isolate the causes ofF         Troubleshooting           network problems and how to tune theG                                   TCP/IP Services software for the best .                                   performance.  @         Compaq TCP/IP Services    This manual describes the IPv6C         for OpenVMS Guide to      environment, the roles of systems.@         IPv6                      in this environment, the typesD                                   and function of the different IPv6H                                   addresses, and how to configure TCP/IPI         __________________________Services_to_access_the_6bone_network.__.  F               For additional information about Compaq OpenVMS productsF               and services, access the Compaq website at the following               location:   ,               http://www.openvms.compaq.com/  	         x                    H               For a comprehensive overview of the TCP/IP protocol suite,B               you might find the book Internetworking with TCP/IP:H               Principles, Protocols, and Architecture, by Douglas Comer,               useful.e           Reader's Comments   G               Compaq welcomes your comments on this manual. Please send <               comments to either of the following addresses:  /               Internet    openvmsdoc@compaq.coml  5               Mail        Compaq Computer Corporation >                           OSSG Documentation Group, ZKO3-4/U08,                           110 Spit Brook Rd./                           Nashua, NH 03062-2698   -         How to Order Additional Documentation   H               Visit the following World Wide Web address for information:               about how to order additional documentation:  ,               http://www.openvms.compaq.com/  F               If you need help deciding which documentation best meets,               your needs, call 800-282-6672.           Conventions.  2               The name TCP/IP Services means both:  9               o  Compaq TCP/IP Services for OpenVMS Alpha   7               o  Compaq TCP/IP Services for OpenVMS VAX   E               The name UNIX refers to the Compaq Tru64 UNIX operating                system..  C               The following conventions are used in this manual. In I               addition, please note that all IP addresses are fictitious.   G               Ctrl/x           A sequence such as Ctrl/x indicates that F                                you must hold down the key labeled CtrlH                                while you press another key or a pointing-                                device button.i  I                                                                        xi.                     F               PF1 x            A sequence such as PF1 x indicates thatG                                you must first press and release the key E                                labeled PF1 and then press and release G                                another key or a pointing device button.   D               <Return>         In examples, a key name enclosed in aD                                box indicates that you press a key onH                                the keyboard. (In text, a key name is not2                                enclosed in a box.)  I                                In the HTML version of this document, this.E                                convention appears as brackets, rather.*                                than a box.  @                . . .           A horizontal ellipsis in examples=                                indicates one of the following -                                possibilities:.  D                                o  Additional optional arguments in a>                                   statement have been omitted.  D                                o  The preceding item or items can be=                                   repeated one or more times.   I                                o  Additional parameters, values, or othert=                                   information can be entered..  I               .                A vertical ellipsis indicates the omission F               .                of items from a code example or commandD               .                format; the items are omitted becauseH                                they are not important to the topic being)                                discussed..  >               ( )              In command format descriptions,I                                parentheses indicate that you must encloseeI                                choices in parentheses if you specify moree(                                than one.  G               [ ]              In command format descriptions, brackets H                                indicate optional choices. You can chooseD                                one or more items or no items. Do notE                                type the brackets on the command line..E                                However, you must include the bracketsLB                                in the syntax for OpenVMS directoryA                                specifications and for a substring.H                                specification in an assignment statement.           xiis                     G               |                In command format descriptions, vertical.D                                bars separate choices within bracketsF                                or braces. Within brackets, the choicesD                                are optional; within braces, at leastF                                one choice is required. Do not type theA                                vertical bars on the command line.   E               { }              In command format descriptions, braces I                                indicate required choices; you must choose G                                at least one of the items listed. Do not C                                type the braces on the command line.   H               bold text        This typeface represents the introductionI                                of a new term. It also represents the name.I                                of an argument, an attribute, or a reason.t  >               italic text      Italic text indicates important>                                information, complete titles ofG                                manuals, or variables. Variables include.G                                information that varies in system outputbB                                (Internal error number), in commandE                                lines (/PRODUCER=name), and in command F                                parameters in text (where dd representsH                                the predefined code for the device type).  F               UPPERCASE TEXT   Uppercase text indicates a command, theH                                name of a routine, the name of a file, orG                                the abbreviation for a system privilege.   I               Monospace text   Monospace type indicates code examples and.;                                interactive screen displays.   I                                This typeface indicates UNIX system outputtG                                or user input, commands, options, files,.H                                directories, utilities, hosts, and users.  B                                In the C programming language, this@                                typeface identifies the following?                                elements: keywords, the names of.H                                independently compiled external functions?                                and files, syntax summaries, and.E                                references to variables or identifiersL8                                introduced in an example.  I                                                                      xiii  b  s                F               -                A hyphen at the end of a command formatF                                description, command line, or code lineF                                indicates that the command or statement?                                continues on the following line.   D               numbers          All numbers in text are assumed to beI                                decimal unless otherwise noted. NondecimalrH                                radixes-binary, octal, or hexadecimal-are4                                explicitly indicated.                                                                               xivc                         I                                                                         1 I         _________________________________________________________________   I                                                  New Features and Changes     B               This chapter lists the new features of Compaq TCP/IPC               Services for OpenVMS V5.1. For more information about E               configuring and managing these services, see the Compaq H               TCP/IP Services for OpenVMS Management guide provided with<               the TCP/IP Services for OpenVMS V5.1 software.            1.1 Version 5.1 Features  B               New features in TCP/IP Services Version 5.1 include:  <               o  New kernel, based on Compaq Tru64 UNIX V5.1  ?               o  Support for Internet Protocol Version 6 (IPv6)k  #               o  GATED Enhancements,  <               o  Services that can be restarted individually  5               o  Cluster failover for the BIND serverC  =               o  BIND dynamic updates management enhancements   2               o  Updated SNMP that supports AgentX  D               o  SMTP AntiSPAM (configuration to control mail relay)  *               o  SMTP SFF (Send From File)  $               o  SMTP outbound alias  C               o  Metric server logicals that can be changed without -                  restarting the Metric server   5               o  Cluster failover for the load brokert  I               o  DHCP server can be configured to dynamically update BINDh                  databaset  ,               o  Xterminal support using XDM  F               o  TELNET client enhancements to support SNDLOC and NAWS  3               o  NFS server and client enhancements_  I                                              New Features and Changes 1-1v s  n                New Features and Changes          1.1 Version 5.1 Features    $               o  DHCP client support  (               o  TCP performance options           1.1.1 New Kernel  H               TCP/IP Services Version 5.1 incorporates the kernel portedE               from Compaq Tru64 UNIX Version 5.1. In addition, TCP/IP I               Services provides better performance under conditions whereS;               a large number of connections are being used.   =               Some of the features of the new kernel include:   2               o  SACK (Selective Acknowledgements)  @                  The new version of the kernel supports multiple>                  acknowledgement windows, allowing outstandingB                  acknowledgements even if the sequence numbers areC                  not in order. For example, if 17 packets are sent, F                  but only those numbered 1 through 4, 6 through 9, andD                  10 through 17 have been acknowledged, the remainingF                  acknowledgements can be denoted as "outstanding." TheF                  software allows up to n outstanding acknowledgements,E                  where n is the number in the TCP options header. For H                  example, the number of outstanding acknowledgements for,                  Ethernet is a maximum of 3.  C               o  PAWS (Protection Against Wrapped Sequence numbers)a  C                  The new version of the kernel supplies time stamps.E                  on transactions. The kernel implements the timestampxH                  option defined in RFC 1323 (Windowscale and Timestamp).F                  This feature prevents sequence numbers from wrapping.D                  Without it, sequence numbers can be negative, which5                  causes conflict in acknowledgements.f  "               o  Path MTU over UDP  H                  Previous versions of the kernel supported path MTU over                  TCP only.  -               o  Multiple adapters per subnet   C                  You can configure multiple active network adaptersiB                  in one computer, even if they operate on the sameA                  subnetwork. For example, you can configure a WE0TB                  interface at 192.24.156.20 and a WE1 interface at5                  192.24.156.21 with the same netmask.   $         1-2 New Features and Changes           I                                                  New Features and ChangessI                                                  1.1 Version 5.1 Features     G                  When you establish a connection, the kernel routes thepG                  connection through the interface that has the smallesteD                  number of connections. As a result, connections areG                  load-balanced, leading to greater throughput than on ai=                  system with only one adapter per subnetwork.   E                  You might choose to configure a system with multiplesD                  interfaces in the same subnetwork for the following                  reasons:I  I                  -  The current environment has only a single subnet, buthF                     additional bandwidth is needed to communicate with$                     certain systems.  G                  -  Your site cannot upgrade its network infrastructure B                     to newer, faster technologies, such as GigabitE                     Ethernet, which would improve network throughput.h  G                  -  The source of a bottleneck is a particular system'scE                     network connection, but the switch to which it is H                     connected is under-utilized and has additional portsG                     and bandwidth available. Another connection to thisc<                     system would reduce resource contention.  F                  -  There are no additional IP subnetworks assigned orF                     available for configuration, and the host requiresH                     more bandwidth to access the current subnetwork than6                     one network interface card allows.  G                     For the system to function properly when configured =                     in this manner, it must meet all of these                      conditions:   F                     *  It must not be running a routing daemon (either(                        GATED or ROUTED).  @                     *  It must have access to all remote systemsC                        through each interface that is configured iniE                        the same subnet. For example, you must be able B                        to successfully issue a ping command to theE                        same remote system when each network interface E                        is configured by itself. This implies that all I                        interfaces in the system are connected to the same /                        physical network switch.   I                                              New Features and Changes 1-3P    v                New Features and Changes          1.1 Version 5.1 Features    F                     This feature might affect the operation of networkA                     software or commands that rely on the network @                     interface staying constant for the life of a,                     connection. For example:  F                     *  Multicast transmission might not work properly.  @                     *  Utilities, such as traceroute, might giveD                        inconsistent output, since the interface used:                        might change from packet to packet.  @                     No special settings are required to use this                     feature.  <         1.1.2 Support for Internet Protocol Version 6 (IPv6)  F               This release contains Internet Protocol Version 6 (IPv6)C               support for Transmission Control Protocol (TCP), UserrH               Datagram Protocol (UDP), and raw sockets, and IPv6 supportC               for commands and utilities. This support is for those H               customers who want to start using IPv6 today and for thoseG               who want to test or experiment with IPv6. This support isoI               in addition to the IPv4 support already in TCP/IP Services.i  5               TCP/IP Services supports the following:   A               o  IPv6 base protocol and addressing specificationsr  B               o  Internet Control Message Protocol (ICMP) for IPv6  ,               o  Path MTU Discovery for IPv6  4               o  Stateless Address Autoconfiguration  #               o  Neighbor Discovery                  o  RIPng for IPv6l  A               o  Transition mechanisms for IPv6 hosts and routersc  G               o  DNS extensions to support IPv6 and DNS dynamic updatese  E               o  Basic IPv6 application programming interfaces (APIs)d  H               o  IPv6 over Ethernet and Fiber Distributed Data Interface                  (FDDI)g  H               The following commands and applications have been modified;               to work in both an IPv6 and IPv4 environment:n  <               o  BIND (8.1.2) server for AAAA (IPv6) records  )               o  TELNET server and clienta  $         1-4 New Features and Changes C  u      I                                                  New Features and Changes I                                                  1.1 Version 5.1 Featuresh    &               o  FTP server and client  !               o  RSH/REXEC client                  o  RLOGIN client                 o  SMTPi  :               o  The following TCP/IP management commands:                    -  IFCONFIG                    -  ROUTE                     -  PING                    -  IP6RTRDs                    -  ND6HOSTD                    -  NETSTATn                    -  TRACEROUTE  H                  If you have configured IPv6 on the system, all of theseH                  commands and applications are automatically enabled for'                  IPv6, except for SMTP.h  C                  To enable SMTP for IPv6 as well as IPv4, enter the 5                  following TCP/IP management command:   <                  TCPIP> SET SERVICE SMTP/FLAGS=(LISTEN,IPV6)  G               To configure and enable IPv6, you must run the TCPIP$IP6_cI               SETUP.COM command procedure. For more information, refer toeG               the Compaq TCP/IP Services for OpenVMS Guide to IPv6. EAKoC               users, refer to Section 2.1.1 in these release notes.   3         1.1.2.1 Name Space Configuration Guidelines   F               Compaq recommends that IPv6 connectivity (whether nativeI               or using tunnels) to IPv6-capable systems be enabled before D               you register both IPv6 and IPv4 addresses for the same               node.e  A               During the early stages of an IPv6 deployment, whencA               only partial IPv6 connectivity is available, CompaqeG               recommended that you register separate names or zones forsE               IPv6 addresses. This prevents unintentional use of IPv6yG               addresses for connections to nodes that are not reachable B               using IPv6, thus avoiding problems with intermittentG               connectivity. When general IPv6 connectivity is available   I                                              New Features and Changes 1-5A r  n                New Features and Changes          1.1 Version 5.1 Features    I               throughout the network, both IPv6 and IPv4 addresses can be ,               registered for the same nodes.  F               When both IPv6 and IPv4 addresses are registered for theH               same node, an IPv6-capable application attempts to connectE               using IPv6 first, and, if the connection fails, uses an                IPv4 address.i  C               When there is no IPv6 connectivity to remote systems, B               significant delays are experienced when attempting aD               connection using the IPv6 address before attempting to-               connect using the IPv4 address.   .         1.1.2.2 Using the Local Hosts Database  G               If you have enabled IPv6, local IPv4 addresses are storedt               in two places:  =               o  Traditional RMS-indexed local hosts databasem!                  (TCPIP$HOST.DAT)   /               o  New TCPIP$ETC:IPNODES.DAT filem  I               If there are duplicate entries in these database files, thee0               local hosts database will be used.  C               The local hosts database accepts only IPv4 addresses.aF               The TCPIP$ETC:IPNODES.DAT file stores both IPv6 and IPv4               addresses.  I               Applications like TELNET attempt to resolve addresses using H               the local hosts database first. Therefore, an IPv4 addressH               in the local hosts database will always be used even if an=               IPv6 definition has been configured using BIND.   D               In environments with a mix of IPv4 and IPv6 addresses,E               to ensure applications use IPv6 addresses first, do not I               define the host in the local hosts database. Use either the,H               IPNODES.DAT file or the BIND database to define hosts with               IPv6 addresses.   =         1.1.2.3 Configuring or Deleting Interfaces Under IPv6   C               If you are configuring a new interface or deleting an C               interface when IPv6 has been configured to run on the B               system, you must run the TCPIP$IP6_SETUP.COM commandH               procedure again to reinitialize the interfaces. Otherwise,!               IPv6 will not work.c  $         1-6 New Features and Changes           I                                                  New Features and ChangespI                                                  1.1 Version 5.1 Featuresy              1.1.3 GATED Enhancements  D               TCP/IP Services has updated the gateway routing daemonD               (GATED). In this release, the Compaq implementation isF               based on GateD Unicast Version 4.0.6 from the Gatedaemon,               Project at Cornell University.  H               GateD Unicast Version 4.0.6 supports the following Unicast1               protocols as specified by the IETF:f  >               o  Intradomain Routing: RIP (V1, V2), OSPF, SLSP  7               o  Interdomain Routing: BGP (V3, V4), EGP   )               o  Network Management: SNMPo  C               o  Network MIBs supported:(RIP, EGP, BGP, OSPF, SLSP)r  E               The additions to the GATED routing protocol are new BGP D               features, including route-reflection, communities, and6               destination preference attributes (DPA).  F                 ________________________ Note ________________________  4                 The HELLO Protocol has been removed.  @                 The HELLO protocol was an interior protocol thatA                 used a routing metric based on the length of time E                 it takes a packet to make the trip between the source C                 and the destination. HELLO is not Y2K compliant, is 6                 not documented and should not be used.  F                 ______________________________________________________  "         1.1.4 Restartable Services  F               TCP/IP Services V5.1 provides startup and shutdown filesB               for individual services, allowing system managers toB               stop and start individual services without affectingF               the operation of the remaining TCP/IP Services software.E               This is useful when you change configuration parametersaD               or logical names that require a specific service to beH               restarted. For example, you can shut down the LPD service,F               change its configuration parameters, and then restart itE               without interrupting the other TCP/IP services that are $               running on the system.  I                                              New Features and Changes 1-7                      New Features and Changes          1.1 Version 5.1 Features    C               Each service has its own startup and shutdown command F               procedures, as follows, where service is the name of the               TCP/IP service:i  B               o  SYS$STARTUP:TCPIP$service_STARTUP.COM, a suppliedD                  command procedure that starts the service specified                  by service.  C               o  SYS$STARTUP:TCPIP$service_SHUTDOWN.COM, a supplied_H                  command procedure that shuts down the service specifiedI                  by service without affecting the other services that aren                  running.P  E               For site-specific configuration and parameter settings, F               Compaq recommends that you create the following types ofD               files in the directory pointed to by SYS$STARTUP. NoteG               that these files will be preserved and not overwritten by G               subsequent installations of the TCP/IP Services software:   E               o  SYS$STARTUP:TCPIP$service_SYSTARTUP.COM, an optional4B                  command procedure that you may use to store site-D                  specific startup commands for the service specified                  by service.  F               o  SYS$STARTUP:TCPIP@service_SYSHUTDOWN.COM, an optionalB                  command procedure that you may use to store site-E                  specific shutdown commands for the service specifiedS                  by service.  B               For more information about starting and stopping theB               components of TCP/IP Services, see the Compaq TCP/IP4               Services for OpenVMS Management guide.           1.1.4.1 Obsolete Files  E               Several files have been made obsolete by these changes:   (               o  TCPIP$DNFC_SHUTDOWN.COM  (               o  TCPIP$DNFS_SHUTDOWN.COM  A                  This file has been replaced by TCPIP$NFS_CLIENT_                   SHUTDOWN.COM.  *               o  TCPIP$LOAD_INETDRIVER.COM  B                  This file has been replaced by TCPIP$INET_DRIVER_                  STARTUP.COM.n  #               o  TCPIP$LOAD_PPP.COMt  $         1-8 New Features and Changes e  r      I                                                  New Features and ChangesoI                                                  1.1 Version 5.1 Features     >                  This functionality is included in TCPIP$INET_                  STARTUP.COM.T  -               o  TCPIP$NFS_SERVER_STARTUP.COMr  F                  This file has been replaced by TCPIP$NFS_STARTUP.COM.  *               o  TCPIP$PCNFSD_SHUTDOWN.COM  I                  This file has been replaced by TCPIP$PCNFS_SHUTDOWN.COM.A  *               o  TCPIP$PORTM_SHUTDOWN.COM.  A                  This file has been replaced by TCPIP$PORTMAPPER_e                  SHUTDOWN.COM.  (               o  TCPIP$PWIP_SHUTDOWN.COM  B                  This file has been replaced by TCPIP$PWIP_DRIVER_                  SHUTDOWN.COM.  '               o  TCPIP$PWIP_STARTUP.COMh  B                  This file has been replaced by TCPIP$PWIP_DRIVER_                  STARTUP.COM.   -               o  TCPIP$REMOTE_TTY_STARTUP.COMn  >                  This functionality is included in TCPIP$INET_                  STARTUP.COM.   (               o  TCPIP$SERVICE_SETUP.COM           1.1.4.2 New Files   E               Several new startup and shutdown files are shipped with                this release:   '               o  TCPIP$BIND_STARTUP.COM   (               o  TCPIP$BOOTP_STARTUP.COM  .               o  TCPIP$DHCP_CLIENT_STARTUP.COM  /               o  TCPIP$DHCP_CLIENT_SHUTDOWN.COMi  /               o  TCPIP$DHCP_CLUSTER_STARTUP.COMe  0               o  TCPIP$DHCP_CLUSTER_SHUTDOWN.COM  )               o  TCPIP$FINGER_STARTUP.COMu  -               o  TCPIP$FTP_CLIENT_STARTUP.COM,  .               o  TCPIP$FTP_CLIENT_SHUTDOWN.COM  &               o  TCPIP$FTP_STARTUP.COM  I                                              New Features and Changes 1-9o o  h                New Features and Changes          1.1 Version 5.1 Features    .               o  TCPIP$INET_DRIVER_STARTUP.COM  /               o  TCPIP$INET_DRIVER_SHUTDOWN.COMt  (               o  TCPIP$LOCKD_STARTUP.COM  )               o  TCPIP$LOCKD_SHUTDOWN.COM   -               o  TCPIP$NFS_CLIENT_STARTUP.COMT  .               o  TCPIP$NFS_CLIENT_SHUTDOWN.COM  &               o  TCPIP$NFS_STARTUP.COM  (               o  TCPIP$PCNFS_STARTUP.COM  )               o  TCPIP$PCNFS_SHUTDOWN.COM   -               o  TCPIP$PORTMAPPER_STARTUP.COMw  .               o  TCPIP$PORTMAPPER_SHUTDOWN.COM  (               o  TCPIP$PROXY_STARTUP.COM  )               o  TCPIP$PROXY_SHUTDOWN.COM   .               o  TCPIP$PWIP_DRIVER_STARTUP.COM  /               o  TCPIP$PWIP_DRIVER_SHUTDOWN.COMs  (               o  TCPIP$REXEC_STARTUP.COM  )               o  TCPIP$REXEC_SHUTDOWN.COM   )               o  TCPIP$RLOGIN_STARTUP.COMu  *               o  TCPIP$RLOGIN_SHUTDOWN.COM  &               o  TCPIP$RMT_STARTUP.COM  '               o  TCPIP$RMT_SHUTDOWN.COMa  &               o  TCPIP$RSH_STARTUP.COM  '               o  TCPIP$RSH_SHUTDOWN.COMl  )               o  TCPIP$TELNET_STARTUP.COM   ,               o  TCPIP$TELNETSYM_STARTUP.COM  -               o  TCPIP$TELNETSYM_SHUTDOWN.COMl  '               o  TCPIP$TFPT_STARTUP.COM   '               o  TCPIP$UCP_SHUTDOWN.COM   &               o  TCPIP$XDM_STARTUP.COM  %         1-10 New Features and Changes     n      I                                                  New Features and ChangesoI                                                  1.1 Version 5.1 Featurest    '               o  TCPIP$XDM_SHUTDOWN.COM   A         1.1.4.3 Changes to the TCPIP$CONFIG.COM Command Procedure   B               The TCPIP$CONFIG.COM configuration command procedure1               includes the following new options:e  I               o  TELNETSYM is offered as a separately manageable service.   H               o  Configure the system as a DHCP client instead of a DHCP                  server.           1.1.5 BIND Enhancementse  G               The following sections describe new features of BIND, the 8               TCP/IP Services implementation of the DNS.  ,         1.1.5.1 BIND Server Cluster Failover  C               In previous versions of TCP/IP Services, there was nomE               convenient method for running more than one BIND master F               server in the same OpenVMS cluster. Multiple BIND masterA               servers can share a common database, thus providing I               redundancy and a failover mechanism when one of the servers "               becomes unavailable.  G               For instructions on setting up cluster failover for BIND, H               refer to the Compaq TCP/IP Services for OpenVMS Management               guide.  F                 ________________________ Note ________________________  A                 Do not use BIND dynamic updates in a BIND clustersC                 failover environment. This is not supported and mayrB                 cause problems. Do not enable dynamic updates in aB                 master BIND server that is participating in a BIND%                 failover environment.   F                 ______________________________________________________  -         1.1.5.2 Managing BIND Dynamic Updateso  D               This version of TCP/IP Services includes the following<               improvements to managing BIND dynamic updates:  =               o  A new logical name to preserve the zone file.  G               o  A safety net mechanism to save changes made during the *                  dynamic update procedure.  I                                             New Features and Changes 1-11.                     New Features and Changes          1.1 Version 5.1 Features    H               These features are described in the Compaq TCP/IP Services+               for OpenVMS Management guide.e           1.1.6 Updates to SNMP   C               After you upgrade to this version of TCP/IP Services, A               you must perform two additional steps to ensure thetG               latest version of SNMP is running on the system. With the 7               configuration procedure TCPIP$CONFIG.COM:a                 1. Disable SNMP.                 2. Enable SNMP.6  D               The version of SNMP included with TCP/IP Services V5.1A               includes new API routines to support extended agenteB               functionality (AgentX). Master/subagent interprocessD               communication is TCP-based, rather than UDP-based, forF               increased awareness by agents when cooperating processesF               exit. Also, the logging information for a trace has been               changed.  I               This release of TCP/IP Services supports the following SNMP                RFCs:   C               o  RFCs 1901 through 1908 (SNMPv2C) in the ExtensibleeG                  SNMP Agent, subagent developer tools, and SNMP-relatedd                  commands.  E               o  RFC 2257 (Agent Extensibility) in the Extensive SNMPg4                  Agent and subagent developer tools.  E               o  RFC 2089 (Mapping SNMPv2 to SNMPv1) in the bilingualv'                  extensible SNMP agent.2  A               There are also some OpenVMS specific changes in thedG               areas of logging and configuration options. Configuration F               includes new text files to supplement the UCP mechanism.  F               Error messages are logged in SYS$SYSDEVICE:[TCPIP$SNMP],B               using files with names based on the subagent name. AF               configuration option allows you to specify that messagesF               are to be sent to the terminal window when processes are                run interactively.  G               Because the new AgentX API is TCP-based, the master agent G               can detect immediately when the subagent exits abnormally I               and can perform the necessary cleanup operations. SubagentshH               can do the same when the master agent exits. Logging data,  %         1-12 New Features and ChangesI ,  c      I                                                  New Features and Changes I                                                  1.1 Version 5.1 Features     F               captured when tracing is enabled, reflects data from theF               underlying AgentX protocol. The previous version of SNMP-               was limited to the simpler DPI.r  -         1.1.6.1 Managing the SNMP MIB Browserr  D               The following flags have been added to the MIB browser=               (snmp_request) in this version of the software:u                 o  -i max_ignores   F                  Specifies the number of times the MIB browser listensB                  for a reply packet to a request if it receives anH                  invalid packet (caused by an invalid packet identifier,C                  version, or SNMP version and command combination).nH                  Specify a positive integer for the value (max_ignores).F                  If you specify a negative value, it will be convertedF                  to an unsigned positive integer. If you specify 0, no#                  retries are tried.n  G                  If, after an invalid reply packet is received, a validoI                  reply packet is received, the ignore counter is reset toI*                  the value of max_ignores.  I                  If a timeout occurs after an invalid packet is received, I                  the packet is resent, the resend counter is decremented, E                  and the ignore counter is reset to the value of max_                   ignores.f  I                  You cannot use the -i flag when you perform a query withiH                  the -l or -t flags to automatically increment the inputH                  OID and continue querying a server after a general SNMPH                  error has occurred, as may happen with a faulty server.F                  In this case, the query is terminated even though theH                  end of the MIB selection has not been reached. You mustG                  manually increment the input OID to skip the error andd)                  continue with the query.o                 o  -r max_retriesu  H                  Specifies the number of times the MIB browser resends aI                  request packet if it times out before receiving a reply. H                  Specify a positive integer for the value (max_retries).F                  If you specify a negative value, it will be convertedF                  to an unsigned positive integer. If you specify 0, no#                  retries are tried.a  I                                             New Features and Changes 1-13o    h                New Features and Changes          1.1 Version 5.1 Features    D                  If, after a timeout and a resend, a reply packet isE                  received, the resend counter is reset. After anotherlE                  timeout, the specified number of max_retries will ben                  sent.  "               o  -s sleep_interval  F                  Specifies the number of seconds between iterations ofH                  sending a request (for the -r flag) and listening for aG                  reply (for the -i) flag. The default is 1 second. ThisAG                  flag is ignored if neither the -r flag nor the -i flage                  are specified.r  D                  The -s flag is useful for specifying a time to waitH                  between resends, which might be necessary when a server&                  agent is starting up.  F               The -i, -r, and -s flags apply to individual queries. IfI               you specify the -l or -t flags also, the values for the -i, =               -r, and -s flags are applied to each iteration.            1.1.7 SMTP Features   I               This version of TCP/IP Services includes the following SMTP                features:   I               o  AntiSPAM, allowing you to configure your host to prevent C                  relaying mail. For more information about antiSPAM B                  configuration, see the Compaq TCP/IP Services for*                  OpenVMS Management guide.  B               o  Send from File (SFF), allowing users to mail non-C                  text files and to automate mail programs. For morea2                  information, see Section 1.1.7.1.  D               o  Outbound alias, allowing users to specify the replyC                  address. For more information, see Section 1.1.7.2   )         1.1.7.1 SMTP SFF (Send From File)   D               SMTP allows you to create a mail message in a file andI               send it to the SMTP mailer to be delivered with headers you I               specify. Using this feature, you can create automated toolsnD               that compose and send mail messages. It is also usefulG               for forwarding non-text files (MIME), because it preventscE               the mailer from encapsulating the MIME and SMTP headersiH               in the body of a new mail message. Thus, SMTP can functionH               like the redirect command on your personal computer, which  %         1-14 New Features and Changest .  L      I                                                  New Features and ChangeseI                                                  1.1 Version 5.1 Features_    I               simply takes the message as is, without encapsulating it inoC               another message, and sends it to the person you name.e  F               To redirect a MIME mail message without encapsulation soF               that it is readable to the receiver, follow these steps:  G               1. From OpenVMS MAIL, use EXTRACT/NOHEADER to extract thei                  mail message.  '               2. Exit the MAIL program.c  B               3. Modify the file to include the SMTP commands. ForH                  example, put the address of the recipient into the RCPTG                  TO:<> line. For more information about the SFF format,v'                  see Section 1.1.7.1.1.t  &               4. Send the file to SFF.  F               If you want headers like From:, To:, or Message-ID:, youH               must include them in the file. SFF adds only the Received:8               header, as described in Section 1.1.7.1.3.  C               1.1.7.1.1 Format of the SFF File   You can use SFF to F               send a text file that complies with RFC 822 by includingB               commands (as described in RFC 821) preceding the RFCF               822 message. MIME, by definition, complies with RFC 822;>               therefore, MIME mail can be delivered using SFF.                 For example:            $ TYPE TEST_SMTP_SFF.TXT!         MAIL FROM:<green@abc.com>h         RCPT TO:<green@abc.com>t         DATA,         Date: Sun, 4 Aug 1996 14:48:14 -0400,         Message-Id: <96080414481486@abc.com>A         From: green@abc.com (Charly Green - ABC-Corp engineering)          To: green@abc.come&         Subject: Test of SFF mechanism  !         This is the message text.f  1               The SMTP protocol commands specify:   ,               1. The return path of the mail                 2. The recipients   !               3. The DATA commandP  I                                             New Features and Changes 1-15o s  -                New Features and Changes          1.1 Version 5.1 Features    $               4. The RFC 822 message  H               The commands that precede the RFC 822 messages must appearF               in the file in the order listed above. The MAIL FROM andG               RCPT TO commands form the "envelope," as described in RFCe,               821 and summarized as follows:  I               1. The MAIL FROM command specifies the address to which thesI                  mail is bounced if necessary. There must be one and only '                  one MAIL FROM command.   H                  You can specify a blank MAIL FROM command. For example:                    MAIL FROM:<>   ?               2. The RCPT TO command specifies the address of a F                  recipient. There must be at least one RCPT TO command?                  but there can be more, one for each recipient.   8                  Do not specify a blank RCPT TO command.  E                  Each RCPT TO command must occupy a separate line and F                  may contain only one address. If the mail is to go toI                  multiple addresses, include one RCPT TO command for each                   address.1  F               3. The DATA command follows the last RCPT TO command; itH                  flags the end of the RCPT TO commands and the beginningC                  of the header block. The DATA command is required.c  I               Do not include a Return-Path header in the RFC 822 headers. E               If the mail is to be delivered locally, SMTP includes aMC               Return-Path header based on the MAIL FROM command. IfTB               the mail is relayed to another SMTP host, the returnF               path is determined by the MAIL FROM command on the final               destination host.b  I               1.1.7.1.2 SFF File Requirements   The mail message file canP4               be in either of the following formats:                  o  Variable length  I                  This type of file does not require carriage-return/line-O9                  feed characters at the end of each line.P                 o  Stream_LF  @                  This type of file requires at least a line-feedG                  character at the end of each line. It is not necessarya3                  to add carriage-return characters.   %         1-16 New Features and Changes            I                                                  New Features and Changes I                                                  1.1 Version 5.1 FeaturesP    E               1.1.7.1.3 SFF Security Measures   The ability to createCD               messages with arbitrary headers could be used to spoofH               message headers. To limit this, the SFF mechanism includes.               the following security measures:  E               o  The process must have either BYPASS, SYSPRV, or OPER-                  privilege set.t  H               o  To help you track messages, SFF adds a Received: headerH                  to the headers you supply. This tells you the origin of.                  an attempted spoofed message.  D               You can invoke SFF from an application or from DCL, as               described below.  F               1.1.7.1.4 Invoking SFF from an Application   TCPIP$SMTP_I               MAILSHR.EXE contains a routine called TCPIP$SMTP_SEND_FROM_T8               FILE. This routine is declared as follows:  K         unsigned int TCPIP$SMTP_SEND_FROM_FILE(infile_name,logfd,log_level)          char *infile_name;         FILE *logfd;         int log_level;  1               The arguments for this routine are:                  o  infile_name  F                  Specifies the name of the text file that contains the&                  RFC 822 mail message.                 o  logfd  H                  Specifies the file to which to log diagnostic messages.F                  This file must be opened by the caller before callingG                  this routine. If no log file is specified, output goesU:                  to SYS$OUTPUT. This argument is optional.                 o  log_level  I                  Specifies the level of diagnostics to use: either 1 (on) E                  or 0 (off). The default is 0 (off). This argument isO                  optional.  ,               To call the routine, link with+               TCPIP$SMTP_MAILSHR.EXE/SHARE.   I                                             New Features and Changes 1-17                      New Features and Changes          1.1 Version 5.1 Features    D               1.1.7.1.5 Invoking SFF from DCL   The SMTP_SFF commandG               allows you to invoke SFF. To define SMTP_SFF as a foreignp@               command so that you can use it from DCL, enter the                following command:  ;               $ SMTP_SFF:==$TCPIP$SYSTEM:TCPIP$SMTP_SFF.EXEi  I               This command takes UNIX style parameters and passes them to                SFF.  $               The command format is:  L               SMTP_SFF infile_name [-log logfile_name] [-loglevel log_level]  7               Where the parameters to this command are:                  o  infile_name  E                  Specifies the name of text input file containing theo#                  SMTP mail to send.                  o  logfile_namee  B                  Specifies the name of the log file for diagnostic7                  messages. (The default is SYS$OUTPUT.)                  o  log_level  I                  Specifies the debug log level: either 1 (on) or 0 (off). *                  (The default is 0 (off).)  #         1.1.7.2 SMTP Outbound Alias   B               The new version of TCP/IP Services SMTP supports theH               specification of an outbound alias that is applied to mailH               as it is sent and specifies the network address to which a!               reply will be sent.v  I               1.1.7.2.1 Defining the Outbound Alias   In some cases it issF               desirable to have control over the contents of the From:F               mail header in mail messages that you send. Setting yourF               own From: header is called "outbound alias." To set thisI               up, define the TCPIP$SMTP_FROM logical to the text you wantv&               your From: header to be.  C               For example, you might define the logical as follows:   ;               $ DEFINE TCPIP$SMTP_FROM "bill.smith@xxx.com".  D               This command sets the outbound alias to the following:  &               From: bill.smith@xxx.com  %         1-18 New Features and Changes            I                                                  New Features and ChangessI                                                  1.1 Version 5.1 Featuress    H               Define the TCPIP$SMTP_FROM logical before entering OpenVMS               Mail.   H               If you always want the header to be sent with the outboundG               alias, define the logical in your login command procedurer               (LOGIN.COM).  A               The outbound alias must be a valid address to whichoG               recipients can reply. If it is not valid, recipients will.H               not be able to reply to you and bounced mail messages will"               not get back to you.  I               If you do not define the TCPIP$SMTP_FROM logical, the From: I               address on your mail messages is the same one that you haven               always had.r  E               Use only simple 7-bit ASCII characters in the value youoG               assign to the TCPIP$SMTP_FROM logical. Do not use control                characters.   C               The address you use to define TCPIP$SMTP_FROM must betB               an RFC 822 legal SMTP address; that is, user@domain.C               If the address is not interpreted correctly, the SMTPgF               mailer ignores it and uses the From: address that it has"               constructed for you.  A               1.1.7.2.2 Appending the Personal Name String to thedA               Outbound Alias  If you have defined an OpenVMS MailMG               personal name string, the SMTP mailer appends that string2$               to the outbound alias.  H               For example, a personal name string is defined as follows:  /               Bill L. Smith Phone: 123-456-8000d  @               The TCPIP$SMTP_FROM logical is defined as follows:  ;               $ DEFINE TCPIP$SMTP_FROM "bill.smith@xxx.com"   :               The resulting From: header is the following:  J               From: bill.smith@xxx.com (Bill L. Smith Phone: 123-456-8000)  H               The personal name is appended to the From: address only if7               both of the following conditions are met:g  C               o  The value you give for the TCPIP$SMTP_FROM logicaldD                  does not contain parenthetical phrases (text within                  parentheses).  I                                             New Features and Changes 1-19L i  d                New Features and Changes          1.1 Version 5.1 Features    G               o  The From: address contains the SMTP domain string (the 1                  @domain portion of the address).F  B               To use a different personal name string than the oneD               defined in your OpenVMS mail personal name, define theI               personal name string as part of the TCPIP$SMTP_FROM logical F               in a parenthetical phrase after the user@domain address.H               Separate the address address from the parenthetical phraseH               with a space. Do not use double quotes (") in the personal               name.t  G               For example, you can define the outbound alias logical asc               follows:  (               $ DEFINE TCPIP$SMTP_FROM -M               $_ "bill.smith@xxx.com (Phone: 123-456-8000 FAX: 123-456-9000)"s  >               The SMTP mailer does not allow you to define theA               TCPIP$SMTP_FROM logical using the following syntax:c  )               "personal name" <user@host>   :               Also, do not specify the logical as follows:  O               $ DEFINE TCPIP$SMTP_FROM """personal name"" <bill.smith@xxx.com>"i  5               Instead, define the logical as follows:p  K               $ DEFINE TCPIP$SMTP_FROM "bill.smith@xxx.com (personal name)"l  E               1.1.7.2.3 Appending a Substitute Domain String   If youiG               define TCPIP$SMTP_FROM without an SMTP domain string (the C               @domain portion of the address), SMTP will append therE               substitute domain name to the text you define. If there D               is no substitute domain name defined, the host name is               used.   C               For example, the host is configured with a substitutenI               domain of x.com, and the TCPIP$SMTP_FROM logical is definedc               as follows:   3               $ DEFINE TCPIP$SMTP_FROM "bill.smith"y  5               In this case, the resulting address is:h  $               From: bill.smith@x.com  %         1-20 New Features and Changesn h  n      I                                                  New Features and Changes I                                                  1.1 Version 5.1 Featuresm    F               However, if the host is not configured with a substituteF               domain and the host name is host.x.com, and SMTP_FROM is!               defined as follows:   3               $ DEFINE TCPIP$SMTP_FROM "bill smith"e  5               In this case, the resulting address is:g  )               From: bill.smith@host.x.comt  G               1.1.7.2.4 Disabling Modifications to TCPIP$SMTP_FROM   TosD               disable the modifications that TCPIP SMTP makes to theD               value you assign to TCPIP$SMTP_FROM (such as appendingF               the OpenVMS personal name and @domain to a value with no6               @domain), include the string [VERBATIM].                 For example:  F               $ DEFINE TCPIP$SMTP_FROM "[VERBATIM] bill.smith@xxx.com"  0               This will result in the following:  &               From: bill.smith@xxx.com  C               1.1.7.2.5 TCPIP$SMTP_FROM and the Return-Path: Header F               The address you define will be used for the Return-Path:D               mail header. The Return-Path: header is used to bounceH               undeliverable mail. Note that the version of the text usedF               for the Return-Path header is stripped of comments (suchI               as the personal name string) and will always have a @domain G               string. (See Section 1.1.7.2.3 for more information about 0               the domain name that is supplied.)  F               1.1.7.2.6 X-VMS-True-From: Header   When the TCPIP$SMTP_I               FROM logical is used to set the From: header, the text that I               would normally have been used for the From: header is added F               to the headers as an X-VMS-True-From: header. This is an$               anti-spoofing measure.  G               1.1.7.2.7 Managing Outbound Alias Processing   To disableoF               outbound alias processing and use of the TCPIP$SMTP_FROM;               logical, define the following system logical:   @               $ DEFINE/SYSTEM TCPIP$SMTP_PROHIBIT_USER_HEADERS 1  I                                             New Features and Changes 1-21  t  n                New Features and Changes          1.1 Version 5.1 Features    (         1.1.8 Metric Server Enhancements  E               The Metric server works with the load broker to provide C               load balancing across OpenVMS clusters. The followingSF               enhancements have been made to the Metric server in this               release:  &               o  Dynamic configuration  F                  Logicals names may be defined for CPU rating, computeC                  interval, and debug level. In previous versions ofhG                  TCP/IP Services, modifications to these logicals wouldtF                  take effect only after the Metric server is shut downD                  and restarted. With this release, the Metric serverH                  recognizes changes to the definitions of these logicals                  dynamically.   I                  For more information about metric server logicals, refer1E                  to the Compaq TCP/IP Services for OpenVMS Managementn                  guide.   +               o  Enhanced logging processesr  G                  The Metric server logging processes have been enhanceda?                  to include more messages, and more informativefF                  information provided with messages. The Metric serverF                  messages are organized into the following categories:  *                  -  Informational messages  #                  -  Warning messagem  "                  -  Error messages  "                  -  Debug messages  C                  All these messages are logged to a single file, asF                  follows:   @                  SYS$SPECIFIC:[TCPIP$METRIC]TCPIP$METRIC_RUN.LOG  /               o  Support for multihomed systems,  G                  This feature allows load balancing of incoming traffic C                  across multiple IP addresses. Each IP address on a.G                  system can now participate in the metric. For example,FE                  the load broker can be configured to include, in theuI                  member list, multiple IP addresses from a single system. D                  The load broker will poll each of the addresses andG                  if it is available, the Metric server will respond for I                  each address. Using the load broker algorithm, this willg  %         1-22 New Features and Changesc m         I                                                  New Features and Changes9I                                                  1.1 Version 5.1 Featuresp    H                  update DNS with each of the IP addresses, and hence theI                  load balancing on a system can be shared across multipleoH                  interfaces. Note that the metric is still calculated onF                  a per system basis. So the Metric server will respondE                  with the same metric value for all IP addresses on a1                  single system.t  #               o  Debug logical name.  G                  The name of the logical to set for debug mode has beenoF                  changed. In previous versions of TCP/IP Services, theH                  logical name is TCPIP$METRIC_DBG_LEVEL. The new logical                  is:  '                  TCPIP$METRIC_LOG_LEVEL   D                  As in the previous version, this logical accepts asC                  values 1 and 2, where 2 provides more information.c  *         1.1.9 Load Broker Cluster Failover  F               With this release, you can run the Load Broker (LBROKER)@               on multiple systems in an OpenVMS cluster. This isI               accomplished through a locking mechanism. The first LBROKER G               process to start in the cluster obtains the lock, and anydD               LBROKER processes started afterwards go into a standbyG               state, waiting for the lock to be released. If the system G               running the first LBROKER goes down, the LBROKER releases F               the lock, allowing the next available standby LBROKER toG               obtain the lock. This system then runs the active LBROKER @               process; additional servers may remain on standby.  6               No additional configuration is required.  G               To disable the failover mechanism for the LBROKER, define +               the following system logical:   G               $ DEFINE /SYSTEM TCPIP$LBROKER_ALLOW_CONCURRENT_SERVERS 1   H               When this logical is defined, you can run multiple LBROKERA               processes in an OpenVMS cluster without the locking (               mechanism described above.      I                                             New Features and Changes 1-23l                     New Features and Changes          1.1 Version 5.1 Features    ,         1.1.10 DHCP Dynamically Updates BIND  F               This feature allows DHCP clients to be configured with aG               registered name, which DHCP will use to assign an addressO0               when it updates the BIND database.  E               To configure DHCP dynamic updates to BIND, complete the "               following procedure:  ?               1. Set the following configuration options in thesC                  SERVER.PCY file (or use the DHCP GUI to make these                   changes):  &                  o  accept_client_name  )                  o  assign_name_by_hwaddrn  )                  o  dns_tracks_dhcp_lease   +                  o  name_service_updateable   F               2. Set up the BIND server to accept dynamic updates fromE                  the DHCP server. If you are running DHCP on multiple E                  nodes in an OpenVMS cluster, be sure to perform this F                  step on all the nodes where the DHCP server runs. ForD                  more information about enabling BIND server dynamicI                  updates, refer to the Compaq TCP/IP Services for OpenVMSd"                  Management guide.  +               3. Set up the .DDNSKEYS file.   @                  This file resides in TCPIP$DHCP_CONFIG (if thatF                  logical is defined), or in the DHCP account's defaultA                  directory (SYS$SYSDEVICE:[TCPIP$DHCP]). There isTD                  no file name for the file. It is simply a file withD                  no name and an extension of .DDNSKEYS (for example,.                  TCPIP$DHCP_CONFIG:.DDNSKEYS).  G                  The .DDNSKEYS file contains entries that describe eachII                  of the BIND domains to update with the DHCP server. EachrI                  line represents one entry and has 3 fields, separated byt                  spaces:  ,                  1. The domain to be updated  G                  2. The IP address of the BIND server to which the DHCPo=                     server should send updates for the domainm  E                  3. This field is reserved for future use with secure.$                     dynamic updates.  %         1-24 New Features and Changess g  n      I                                                  New Features and ChangesvI                                                  1.1 Version 5.1 Featuresd    F                  The DHCP server updated BIND for forward and backwardF                  translation; therefore, you need two entries: one forE                  each translation. For backward translation, the BINDa3                  "in-addr.arpa" convention is used.a  I                  For example, to be able to send updates to a BIND serveroH                  at 17.21.208.100 for the domain fu.bar.com, include the                  following:   !                  $ TYPE .DDNSKEYSt*                   fu.bar.com 17.21.208.1002                   21.17.in-addr.arpa 17.21.208.100  ?               4. Set the dns_tracks_dhcp_lease parameter in thea!                  SERVER.PCY file.p  H                  If a dynamic BIND update fails, the DHCP server logs anI                  error and grants the lease of the IP address to the DHCPeE                  client, but does not automatically repeat the failed I                  dynamic DNS update operation. Further, when the lease on H                  the particular IP address is renewed by the client, theI                  DHCP server will not send another dynamic BIND update atoI                  that time, unless the dns_tracks_dhcp_lease parameter is I                  set in the SERVER.PCY file. Therefore, Compaq recommends D                  that you set the dns_tracks_dhcp_lease parameter inG                  the SERVER.PCY file if the server is set up to perform &                  dynamic BIND updates.  #         1.1.11 XDM Terminal Supportd  I               For network displays, such as X terminals, the login server E               supports the X Display Manager Control Protocol (XDMCP) I               1.0, which allows display devices to request that the login ;               server display a login screen on the display.o  G               To use XDMCP, the system must be running DECwindows Motif %               Version 1.2-5 or later.d  C               For information about configuring XDM on your system,_H               refer to the Compaq TCP/IP Services for OpenVMS Management               guide.        I                                             New Features and Changes 1-25S _  M                New Features and Changes          1.1 Version 5.1 Features    )         1.1.12 TELNET Client Enhancementsl  D               The TELNET client component has been enhanced for thisD               release, including support for window sizing (rows andE               columns), and location options. These options depend onF9               appropriate support from the TELNET server.c  I               o  The NAWS (Negotiate About Window Size) option allows theyF                  client to respond to a request from the TELNET serverE                  for information about the local terminal (or window)CE                  size, including the columns and lines per page. ThiscF                  ensures the TELNET terminal (TNA) is set accordingly.  D                  Note the using the SET TERMINAL/INQUIRE command canF                  cause the terminal's width and page size to be reset.  C               o  The SNDLOC option allows the TELNET client to send F                  information that can be used to identify the locationD                  of the TELNET client device on the host. The clientD                  passes the physical terminal name and the user nameC                  to the server. For example, user SMITH on terminalr@                  device _RTA: appears as _RTA2:/SMITH. With thisF                  release, the information appears on the TELNET serverE                  as Locn: _RTA2:/SMITH in the access portname string.n  F                  Note that the RLOGIN protocol obtains the user's nameF                  from the RLOGIN session information provided when theI                  connection is established, and the user name is included C                  in the access portname string as User: <username>.n  1         1.1.13 NFS Server and Client Enhancements   @               This release includes several enhancements to NFS,               including:  .               o  New NFS server that supports:  4                  -  Both NFS V2 and NFS V3 protocols  $                  -  Both UDP and TCP  A               o  Changes to file size processing that may improve                   performance  E               o  NFS server configuration parameters that are managedn                   using sysconfig                 o  File lockingh  '               o  New MOUNT V3 component   %         1-26 New Features and Changes  I  M      I                                                  New Features and ChangesiI                                                  1.1 Version 5.1 Features     @               These features are described in more detail in the!               following sections.o            1.1.13.1 NFS V3 Protocol  D               This release features a new version of the NFS server.H               The new NFS server is compliant with both of the following               RFCs:h  E               o  RFC 1094, Network File System Protocol Specificationi  ?               o  RFC 1813, NFS Version 3 Protocol SpecificationP  H               The NFS server provided with TCP/IP Services V5.1 respondsH               to both the NFS V2 and V3 protocols, as described in these               RFCs.   H               The main improvements offered by using the NFS V3 protocol               include:  ,               o  Increased maximum file size  E                  The maximum file size allowed by the NFS V3 protocol_B                  is 1 terabytes for an OpenVMS files system, and 4F                  gigabytes for a container file system. For the NFS V2H                  protocol, the maximum file size is 2 gigabytes for both8                  the OpenVMS and container file systems.  G                  If your system has files of between 2 and 4 gigabytes, G                  you should upgrade to TCP/IP Services V5.1 only if the ;                  NFS clients are using the NFS V3 protocol.   F                 ________________________ Note ________________________  C                 The TCP/IP Services NFS client does not yet support $                 the NFS V3 protocol.  F                 ______________________________________________________  +               o  Enhanced write performancei  D                  With this release, the NFS server may acknowledge aD                  write operation before the data is actually writtenG                  to disk. Afterwards, the server's response to a commit I                  message confirms that the data has been written to disk.   I                                             New Features and Changes 1-27i y                   New Features and Changes          1.1 Version 5.1 Features    /         1.1.13.2 Extending and Truncating Files   E               The new version of the NFS server determines file sizesN@               differently than in previous versions. The changesE               represent significant performance improvements for someo                users, as follows:  H               o  When writing files sequentially from an OpenVMS client,D                  performance may improve significantly, depending onI                  whether the file is preextended or not. Output files are :                  normally preextended by the COPY utility.  D               o  When copying files from a UNIX client to an OpenVMSG                  server, you can obtain some performance improvement by G                  setting a larger default extend quantity using the DCL H                  command SET VOLUME/EXTENSION. Enter the HELP SET VOLUMEI                  command for more information. This quantity is first set F                  when the volume is initialized. For file copying fromE                  OpenVMS clients, this improvement may also apply for 0                  files that are not preextended.  F               o  When copying or writing files from a UNIX client, theE                  file size is truncated to end-of-file (EOF) when theRD                  NFS server closes the file. The timing of the closeB                  operation depends on the inactivity timer. If theH                  server shuts down, any currently open files will not beI                  truncated to EOF. If any extra blocks are remaining, youSH                  can remove them with the DCL command SET FILE/TRUNCATE.  7         1.1.13.3 NFS Client Reports True Allocated SizeF  A               In previous releases, the OpenVMS NFS client alwaysdC               reported the allocated size as equal to the EOF size.yE               In this release, the client attempts to report the trueaA               allocated size. However, when it explicitly extendssC               or truncates a file, the client assumes that the filerF               size is exactly what it requested until it refreshes itsG               cached file attributes, which may be some time later. ThemE               true allocated size may be larger because of the volumeA(               allocation cluster factor.          %         1-28 New Features and Changesn           I                                                  New Features and Changes.I                                                  1.1 Version 5.1 Featuresh    *         1.1.13.4 MOUNT Retry Default Value  G               The default value for the /RETRIES qualifier to the MOUNTnI               command has been changed to 4. This is the same as the soft H               mount default in most UNIX operating systems. Limiting theB               number of retries limits the maximum allowable wait.  F               To establish a new default, define the following logical               name:e  4               TCPIP$NFS_CLIENT_MOUNT_DEFAULT_RETRIES  F               This logical name modifies the default for the number ofH               times an I/O operation will be attempted. Set this logicalD               to a non-negative integer. Defining this logical to beD               zero (0) restores the "infinite retry, unlimited wait"I               implemented in earlier versions of TCP/IP Services. A value E               of zero results in the equivalent of a UNIX hard mount.   H               You can override the default setting by using the /RETRIES?               qualifier to the TCP/IP management command MOUNT.             1.1.13.5 Network Locking  C               This release supports a partial implementation of NFSeD               network locking, which allows users to lock files. TheG               software coordinates locks among remote users and betweenrB               remote and local users. The file locking features isA               applicable regardless of whether the OpenVMS Record G               Management System (RMS) is used or not. However, NFS doesCB               not coordinate network locking and RMS record locks.  I               This version of NFS does not support byte-range locking. If G               a byte-range lock request is received, it is handled as a                 file lock request.  H               File locking is implemented using the Network Lock ManagerA               (NLM) and the Network Status Monitor (NSM). The NLMdF               coordinates locks made by clients. The NSM recovers lockG               information in case the server or client crashes. The NSMtG               uses the NLM to keep the host list when the client or thea5               server crashes and reboots, as follows:u  H               o  If the client crashes and reboots, it notifies the NSMsE                  on its host list. In turn, the NSMs tell their local =                  NLMs to free any locks held for that client.   I                                             New Features and Changes 1-29c    a                New Features and Changes          1.1 Version 5.1 Features    G               o  If the server crashes, when it reboots it notifies theSH                  NSMs on each client host in its host list. In turn, theG                  client NSMs tell their local NLMs to rerequest all the F                  locks that were granted on their behalf by the server#                  before it crashed.   I               The NSM and the NLM are enabled if you select "LOCKD/STATD" H               from the Server Configuration menu in the TCPIP$CONFIG.COME               configuration procedure. As a result, two processes are E               started when you start TCP/IP Services: TCPIP$LOCKD and                TCPIP$STATD.  B               For more information about managing the file lockingF               feature, refer to the Compaq TCP/IP Services for OpenVMSG               Management guide). Also, see Section 3.7 in these release                notes.  +         1.1.13.6 Managing the MOUNT ServiceE  B               The MOUNT service responds to Version 1 of the MOUNTI               protocol, which is used with Version 2 of the NFS protocol.yH               It also supports Version 3 of the MOUNT protocol, which isH               used with Version 3 of the NFS protocol. The MOUNT serviceE               now runs as a separate process; in previous versions ofoD               TCP/IP Services, MOUNT ran as part of the NFS service.  G               The MOUNT service is started automatically when you start H               the NFS server (for example, using TCPIP$NFS_STARTUP.COM).  H               For information about managing the MOUNT service, refer toF               the Compaq TCP/IP Services for OpenVMS Management guide.  (         1.1.14 DHCP Client Configuration  I               This version of TCP/IP Services allows you to designate therH               system as a DHCP client, to be automatically configured byI               a DHCP server. The same system cannot be both a DHCP cliente                and a DHCP server.  F               The DHCP client software conforms to the following RFCs:  >               o  RFC 2131, Dynamic Host Configuration Protocol  C               o  RFC 2132, DHCP Options and BOOTP Vendor Extensions   G               The DHCP client service is described in the Compaq TCP/IPh4               Services for OpenVMS Management guide.  %         1-30 New Features and Changesm t  h      I                                                  New Features and ChangesiI                                                  1.1 Version 5.1 Features     A               To enable DHCP client functionality, you can eithercF               manually configure the DHCP client, or you can allow the4               software to configure the DHCP client.  >               o  To manually configure the DHCP client and its                  interface:a  >                  1. Install the TCP/IP Services V5.1 software.  I                  2. Run the TCPIP$CONFIG configuration command procedure.o  I                  3. Configure a network interface for control by the DHCPF                     Client.o  A                     The DHCP client requires control of least one D                     network interface. The designated interface willA                     get its IP address, subnet mask and broadcast C                     address automatically from the DHCP server when 1                     TCPIP$STARTUP.COM is invoked.u  <                     From the "Core Environment" menu, selectH                     "Interfaces." For each interface, the procedure asks7                     you to select one of the following:f  7                        1 - Configure interface manuallyG7                        2 - Let DHCP configure interfacei  C                     Select "2" to designate the interface as a DHCP %                     client interface.   H                  4. The procedure then asks whether the interface shouldF                     be designated as the "primary interface." Refer toI                     the Compaq TCP/IP Services for OpenVMS Management for >                     more information about primary interfaces.  B                  5. If you configure an interface to be under DHCPD                     control, the procedure checks to see if you haveI                     enabled DHCP client. (To enable DHCP client, from theNF                     main menu select "Clients". From the Clients menu,)                     select "DHCP Client."   @                     If the DHCP client had not been enabled, theD                     TCPIP$CONFIG procedure automatically invokes theF                     Client menu. Select "Enable service on this node."  B                     The procedure sets up the environment for DHCP&                     client, including:  4                     -  Creates the the DHCP account.  2                     -  Creates the DHCP directory.  I                                             New Features and Changes 1-31m .  2                New Features and Changes          1.1 Version 5.1 Features    I                     -  Loads the CLIENT.PCY file into the DHCP directory.C  D                     -  Loads the HOSTNAME. file, which specifies theF                        host name to request from the DHCP server, intoH                        the DHCP directory. This file is populated by theH                        TCPIP$CONFIG configuration procedure and contains(                        the SCSNODE name.  F               o  To allow the software to automatically configure DHCPE                  client, follow the steps listed below. The procedureaH                  is only valid on a system where TCP/IP Services has not,                  been previously configured.  >                  1. Install the TCP/IP Services V5.1 software.  B                  2. Execute the TCP/IP Services startup procedure,&                     TCPIP$STARTUP.COM.  F                  3. The startup procedure detects the fact that TCP/IPF                     Services have not been configured. It asks whetherF                     you want the DHCP Client to configure the host for&                     you. Answer "Yes".  E                  4. The startup procedure invokes TCPIP$CONFIG, whichnC                     sets up the environment for the DHCP client andiF                     designates any unconfigured interfaces to be underB                     DHCP client control. The procedure enables the<                     following set of services automatically:  !                     -  FTP client   $                     -  TELNET client  $                     -  TELNET server  C                  If there is more than one interface, the procedurerD                  determines whether any interface is configured withB                  a permanent IP address. In this case, none of theD                  interfaces are designated as the primary interface.H                  If there are no interfaces configured with permanent IPH                  addresses, the procedure designates the first interface7                  it discovers as the primary interface.   G                  You can run the TCPIP$CONFIG procedure later to change :                  the interface and service configurations.  %         1-32 New Features and Changess d  n      I                                                  New Features and ChangesoI                                                  1.1 Version 5.1 Featuresd    &         1.1.15 TCP Performance Options  D               This release of TCP/IP Services supports the following?               socket programming options, which may improve thea2               performance of network applications:                 o  TCP_TSOPTENAo  D                  When the TCP_TSOPTENA option is enabled, the senderG                  places a timestamp in each data segment. The receiver,ME                  if configured to accept them, sends these times back.G                  in the acknowledgement (ACK) segments. This allows theEE                  sender to measure the round-trip communication time.                  o  TCP_PAWSN  D                  When the TCP_PAWS (Protect Against Wrapped SequenceI                  numbers) option is enabled, the receiver rejects any oldeG                  duplicate segments it receives. This option is used on I                  synchronized TCP connections only, and requires that thee1                  TSOPTENA option be enabled also.l                 o  TCP_SACKENA  G                  When the TCP_SACKENA (Selective Acknowledgment) optiontE                  is enabled, the receiver can inform the sender about C                  all segments that arrive successfully. This allowseG                  the sender to retransmit only those segments that have I                  actually been lost. This option is useful in cases where /                  multiple segments are dropped.o           1.2 Version 5.1 ChangesT  E               The following sections describe additional changes made ?               from TCP/IP Services Version 5.0A to Version 5.1.h  -         1.2.1 Unsupported Management Commands   @               The following commands are not intended for use byF               customers. Use of these commands may cause unpredictable               results:  #               o  COPY CONFIGURATIONe                 o  GENERATE MAPS  $               o  START COMMUNICATION  #               o  STOP COMMUNICATIONi                 o  STOP MAIL  I                                             New Features and Changes 1-33                      New Features and Changes         1.2 Version 5.1 ChangesF    "               o  STOP NAME_SERVICE                 o  ZERO INTERFACE   F               In addition, the following options and qualifiers are no               longer supported:e  0               o  CONVERT/UNIX BIND [output-file]  @                  Changing the output file name is not supported.  ,               o  SET CONFIG SMTP /POSTMASTER  <                  The /POSTMASTER qualifier is not supported.  C               These commands, qualifiers, and options are no longer B               documented in the Compaq TCP/IP Services for OpenVMS2               Management Command Reference manual.  ,         1.2.2 Changes to Management Commands  G               The following changes have been made to TCP/IP management                commands:o  B               o  The product name as reflected by the SHOW VERSION7                  command has been changed. For example:_  $                  TCPIP> SHOW VERSION  :                  Compaq TCP/IP Services for OpenVMS  . . .  C               o  The behavior of the START COMMUNICATION/INITIALIZE_3                  command was changed. Specifically:   D                  -  This command no longer enables services or loadsI                     communication proxies. These operations are performeda:                     by the service-specific startup files.  ;                  -  If DHCP client has been selected in the E                     TCPIP$CONFIG.COM procedure, this command runs the F                     dhcpconf utility, which invokes DHCP client on the(                     specified interface.  F                 ________________________ Note ________________________  F                 The START COMMUNICATION command is reserved for use by                 Compaq only.  F                 ______________________________________________________  F               o  The SET INTERFACE command accepts two new qualifiers:$                  /PRIMARY and /DHCP.  %         1-34 New Features and ChangesV c  n      I                                                  New Features and Changes I                                                   1.2 Version 5.1 Changes     D               o  The SET CONFIGURATION INTERFACE command accepts twoE                  new qualifiers: /[NO]PRIMARY and /[NO]DHCP. For moreeH                  information, see the Compaq TCP/IP Services for OpenVMS#                  Management manual.s  1         1.2.3 Changes to NFS Server ConfigurationE  A               Under previous versions of TCP/IP Services, you cann;               configure the way the NFS server works using:   <               o  SET NFS_SERVER command. Qualifiers include:  )                  -  /ENABLE=[ERROR|OPCOM]   *                  -  /DISABLE=[ERROR|OPCOM]  "                  -  /GID_DEFAULT=n                    -  /HOSTS=n  %                  -  /INACTIVITY_TIMER   "                  -  /UID_DEFAULT=n                    -  /THREADS=n                    -  /XID=n  =               o  SHOW NFS_SERVER command. Qualifiers include:i  !                  -  /CONTINUOUS=ns                    -  /HOST=host  #                  -  /IDENTIFICATIONt                    -  /PARAMETERSs                    -  /SERVICES   (                  -  /USER_NAME=user-name  3               o  TCPIP$NFS000000000* logical names:   ,                  -  TCPIP$NFS000000000_ERROR  ,                  -  TCPIP$NFS000000000_OPCOM  ,                  -  TCPIP$NFS000000000_HOSTS  *                  -  TCPIP$NFS000000000_UID  *                  -  TCPIP$NFS000000000_GID  1                  -  TCPIP$NFS000000000_INACTIVITYl  I                                             New Features and Changes 1-35l                     New Features and Changes         1.2 Version 5.1 Changes     /                  -  TCPIP$NFS000000000_SECURITYe  .                  -  TCPIP$NFS000000000_THREADS  *                  -  TCPIP$NFS000000000_XID  C               Under TCP/IP Services V5.1, you can configure the NFS                server using:   <               o  SET NFS_SERVER command. Qualifiers include:  "                  o  /UID_DEFAULT=n  "                  o  /GID_DEFAULT=n                    o  /THREADS=n  '                  o  /INACTIVITY_TIMER=na  =               o  SHOW NFS_SERVER command. Qualifiers include:   %                  -  /CLIENT=user-namee  !                  -  /CONTINUOUS=nn  %                  -  /SERVER=host-name   $                  -  /VERSION=[V2|V3]  "               o  SYSCONFIG command  I                  For more information about using SYSCONFIG to modify NFS 8                  server attributes, see Section 1.2.3.2.  F               The following qualifiers, which were used under previousC               versions of TCP/IP Services, are no longer supported:m                  o  /IDENTIFICATION                 o  /PARAMETERS                 o  /SERVICES  F               The NFS server logical names are no longer supported. InG               some cases, you can use SYSCONFIG to change an equivalent I               attribute instead. See Section 1.2.3.2 for more information $               about using SYSCONFIG.  E               The following table lists the NFS server logical names,e?               and, where appropriate, the equivalent attribute:   %         1-36 New Features and Changesl n  i      I                                                  New Features and Changes I                                                   1.2 Version 5.1 Changes   I               ___________________________________________________________ I               Logical_Name___________________Attribute___________________e  :               TCPIP$NFS000000000_ERROR       No equivalent  :               TCPIP$NFS000000000_OPCOM       No equivalent  :               TCPIP$NFS000000000_HOSTS       No equivalent  8               TCPIP$NFS000000000_UID         noproxy_uid  8               TCPIP$NFS000000000_GID         noproxy_gid  2               TCPIP$NFS000000000_INACTIVITY  vnode  <               TCPIP$NFS000000000_SECURITY    noproxy_enabled  8               TCPIP$NFS000000000_THREADS     tcp_threads  :               TCPIP$NFS000000000_XID         No equivalent  I               TCPIP$CFS_KEEP_ALLOC___________No_equivalent_______________M  @         1.2.3.1 Using NFSSTAT to Display Statistical Information  G               You can display NFS and RPC statistical information usingsD               either the SHOW NFS_SERVER command or the UNIX utilityC               NFSSTAT. In order to use the NFSSTAT foriegn command,nF               be sure to run the SYS$MANAGER:TCPIP$DEFINE_COMMANDS.COMG               procedure. For information about using NFSSTAT, enter thea2               following TCP/IP management command:                  TCPIP>HELP NFSSTAT  F               The following table lists the SHOW NFS_SERVER qualifiersA               and equivalent NFSSTAT flags you can use to displaylD               statistical information about NFS and RPC connections:  I         Table_1-1_Displaying_Statistical_Information_with_NFSSTAT________d           SHOW NFS_SERVER I         Qualifier________Meaning______________NFSSTAT_Flag_______________e  A         /CONTINUOUS=n    Specifies the        nfsstat -i intervalf%                          interval (inr%                          seconds) forn%                          updating the &                          statistics on!                          display.t  I                                                  (continued on next page)   I                                             New Features and Changes 1-37i h                   New Features and Changes         1.2 Version 5.1 Changesv    I         Table_1-1_(Cont.)_Displaying_Statistical_Information_with_NFSSTAT            SHOW NFS_SERVERsI         Qualifier________Meaning______________NFSSTAT_Flag_______________V  8         /RPC             Displays             nfsstat -r*                          information about"                          RPC only.  8         /SERVER          Displays             nfsstat -s*                          information about%                          NFS and RPC.   I         /VERSION=(V2|V3) Displays version-    For Version 2 only: nfsstatr0                          specific NFS         -2I                          statistics. You      For Version 3 only: nfsstat 0                          can include either   -3+                          or both arguments.t%                          For example:r  )                          /VERSION=(V2,V3)t  *                          The default is to,                          show statistics forI         _________________both_versions.__________________________________   F               To reset the statistics to zero, use the ZERO NFS_SERVER8               command, or the following NFSSTAT command:                 $ NFSSTAT -z  ?         1.2.3.2 Using SYSCONFIG to Modify NFS Server Attributesi  C               You can modify NFS server attributes using either theqC               TCP/IP management command SET NFS_SERVER, or the UNIX F               utility SYSCONFIG. In order to use the SYSCONFIG foreignC               command, be sure to run the TCPIP$DEFINE_COMMANDS.COM E               procedure. For information about using SYSCONFIG, enter 6               the following TCP/IP management command:  "               TCPIP>HELP SYSCONFIG  F               The following table lists the NFS server attributes thatD               you can modify using the SYSCONFIG command. This tableA               explains the purpose of the attribute and shows thenG               qualifier to the SET NFS_SERVER command that performs theC"               equivalent function.  %         1-38 New Features and Changes  e  r      I                                                  New Features and Changes I                                                   1.2 Version 5.1 Changes     I         Table_1-2_Modifying_NFS_Server_Attributes_with_SYSCONFIG_________P  I         Attribute________Description__________SET_NFS_SERVER_Qualifier___l  <         noproxy_enabled  Enables the use      No equivalent.+                          of the noproxy_uidt(                          and noproxy_gid,                          attributes. If this)                          attribute is noto*                          set to 1, proxies)                          are required forn'                          server access.C  (                          If the value is'                          0, files owneds'                          by a user thatr&                          is not in the+                          proxy database are ,                          assumed to be owned(                          by UID=-2/GID=-(                          2. If the value*                          is 1, files owned)                          by a user not in +                          the proxy databaseo+                          are reported to bet,                          owned by the values+                          of the noproxy_uid (                          and noproxy_gid$                          attributes.  H         noproxy_uid      Specifies the        SET NFS_SERVER/UID_DEFAULT)                          default UID whene)                          a user cannot beo*                          translated by the                          proxy.a  H         noproxy_gid      Specifies the        SET NFS_SERVER/GID_DEFAULT)                          default GID whenl)                          a user cannot beC*                          translated by the                          proxy.t  I                                                  (continued on next page)1    I                                             New Features and Changes 1-39e r                   New Features and Changes         1.2 Version 5.1 Changeso    I         Table_1-2_(Cont.)_Modifying_NFS_Server_Attributes_with_SYSCONFIG_   I         Attribute________Description__________SET_NFS_SERVER_Qualifier___   <         tcp_threads      Specifies the        No equivalent."                          number of'                          concurrent TCP +                          threads within the                            server.  D         udp_threads      Specifies the        SET NFS_SERVER/THREADS"                          number of'                          concurrent UDPw+                          threads within the +                          server. Do not set *                          this attribute to)                          zero. A value of/*                          zero will disable*                          the UDP protocol.  H         vnode_age        Specifies the        SET NFS_SERVER/INACTIVITY_3                          number of seconds    TIMER $                          in the time+                          interval since the )                          last file access !                          request.   ,                          The server keeps an+                          activity timestamp (                          for each opened%                          file to help (                          manage the open(                          file cache. The,                          default setting for)                          this variable is +                          120, or 2 minutes. *                          Be careful not to*                          set this value to*                          a small interval;*                          this might reduceI         _________________performance.____________________________________e        %         1-40 New Features and Changes            I                                                  New Features and ChangesdI                                                   1.2 Version 5.1 Changesi    =         1.2.3.3 Using SYSCONFIG to Display Parameter Settingst  B               To display NFS parameter settings, use the following                SYSCONFIG command:                  $ SYSCONFIG -q nfs  I               To display VFS parameter settings, such as vnode_age, enteru$               the following command:                  $ SYSCONFIG -q vfs  F                 ________________________ Note ________________________  A                 UNIX network commands have been ported to OpenVMS B                 and do not return the same status codes as they doE                 on UNIX. Therefore, you should not write functions orND                 procedures that rely on the UNIX status codes as theF                 result of UNIX network commands entered on the OpenVMS                 system.i  F                 ______________________________________________________  F               For more information about using SYSCONFIG to modify NFSH               server attributes, refer to the Compaq TCP/IP Services for'               OpenVMS Management guide.A  "         1.2.4 TCP/IP Process Names  F               The process names created when services are started haveE               been enhanced to include a reference number. Therefore,oF               when you list the system processes using the SHOW SYSTEMI               command, the TCP/IP Services processes will have names that E               include a number that indicates the number of processesoC               that have been started for each process. For example:o                    I                                             New Features and Changes 1-41                      New Features and Changes         1.2 Version 5.1 Changes              $ SHOW SYSTEMiR         OpenVMS V7.2-1  on node OVMS  31-AUG-2000 17:33:19.75  Uptime  0  00:22:13S         Pid    Process Name    State  Pri      I/O       CPU       Page flts  Pages S         53200081 SWAPPER         HIB     16        0   0 00:00:03.12       0      05          . . .V         5FA0021C TCPIP$BIND_1    LEF      9   362953   0 00:01:02.84     504    381  NV         5FA0021D TCPIP$PORTM_1   LEF     10      878   0 00:00:00.30     300    284  NV         5FA0021E TCPIP$FTP_1     LEF     10     1317   0 00:00:00.31     700    270  N          . . .S         5FA00223 TCPIP$LPD_QUEUE HIB      4       49   0 00:00:00.10     263    130 V         5FA00224 TCPIP$METRIC_1  LEF     10      144   0 00:00:18.23     285    208  NV         5FA00225 TCPIP$NFS_1     HIB     10      147   0 00:00:00.11     397    247  NV         5FA00226 TCPIP$MOUNTD_1  LEF     10     1113   0 00:00:00.80     531    381  NV         5FA00227 TCPIP$NTP_1     LEF      9   254946   0 00:00:41.21     355    270  NV         5FA00228 TCPIP$PCNFSD_1  LEF     10      162   0 00:00:00.16     343    208  NV         5FA00229 TCPIP$POP_1     HIB     10    41260   0 00:00:15.32     719    519  N          . . .  D               If you have commmand procedures that reference process:               names, be sure to modify them appropriately.           1.2.5 FTP Changesp  H               The following sections describe changes to the FTP utility8               since the last release of TCP/IP Services.            1.2.5.1 FTP Passive Mode  C               This release provides the new FTP client commands SET B               PASSIVE, SHOW PASSIVE, and the UNIX command passive.G               Passive mode is useful in cases where a firewall preventsP?               the FTP server from establishing an outbound datap               connection.   F               The value of the new passive parameter has been added toF               the output from the SHOW STATUS and status commands. See0               FTP> HELP SET PASSIVE for details.  '         1.2.5.2 FTP Message Enhancementi  D               The information returned by the FTP STATUS command hasA               been improved. When you use the STATUS command, thehG               message reporting the handling of uppercase and lowercase H               characters in the file name provides more information. For@               example, see the line starting with "Case:" below:  %         1-42 New Features and Changes_ _         I                                                  New Features and Changes I                                                   1.2 Version 5.1 Changes_    
         $ FTP          Error level is WARNING         FTP> STATUSt           Local client's status:         No connected         VMS Plus mode disabledG         Mode = stream, Type = ascii, Form = non_print, Structure = file          Error level is WARNING         Reply display is on          Parsing is ons         Prompting is off         Port command is onM         Case: MPUT will preserve typographical case in destination filenames,M         if possibler           FTP>  .         1.2.6 POP Server Threads Configuration  H               The maximum number of threads that a single POP server canF               process is now configurable. To configure it, define theF               system logical TCPIP$POP_MAXIMUM_THREADS and specify theE               value as the maximum number of threads you want the POPr               server to handle.   E               The minimum value is 1, which turns the POP server into C               a single-threaded server with each new POP connection E               creating a new server process. The maximum value is 15.T?               If the logical is not defined, the default is 15.n  B               This logical may be used to solve resource problems.           1.2.7 LPD ChangesU  A               The following changes affect the way the LPD works:F  )               o  LPD startup and shutdown   D                  The DCL commands to start and stop LPD remote queueF                  definitions entered in the TCPIP$LPRSETUP.EXE programH                  are no longer appended to the TCPIP$LPD_STARTUP.COM andE                  TCPIP$LPD_SHUTDOWN.COM command procedures. With this I                  release, the DCL commands are included in the TCPIP$LPD_GC                  SYSTARTUP.COM and TCPIP$LPD_SYSHUTDOWN.COM command E                  procedures. This resolves the problem with retaining E                  the DCL commands for queue startup and shutdown wheneI                  you upgrade TCP/IP Services. The TCPIP$LPD_SYSTARTUP.COM   I                                             New Features and Changes 1-43                      New Features and Changes         1.2 Version 5.1 Changes     I                  and TCPIP$LPD_SYSHUTDOWN.COM procedures are not replacedd2                  when you install TCP/IP Services.  I                  Note that you must manually save and edit the procedures E                  one more time to save the queue startup and shutdown D                  commands. Save the DCL commands from the TCPIP$LPD_E                  STARTUP.COM procedure to the TCPIP$LPD_SYSTARTUP.COM I                  procedure, and save the DCL commands from the TCPIP$LPD_aG                  SHUTDOWN.COM procedure to the TCPIP$LPD_SYSHUTDOWN.COMfH                  procedure. After this, the DCL commands to start up and8                  shut down the queues will be preserved.  3               o  User name appears on the flag pagen  H                  With this release, when an inbound print job is printedF                  under the LPD account (TCPIP$LPD), the user name thatE                  appears on the flag page and in the display from the G                  SHOW ENTRY command is the remote user name under whichn-                  the print job was submitted.            1.2.8 NTP ChangesY  E               The following lists some of the changes in NTP for thisl)               version of TCP/IP Services:a  C               o  NTP has been updated to support automatic DaylightlD                  Savings Time (DST) adjustments when this feature is:                  provided by the OpenVMS operating system.  F               o  NTP logging can be controlled with a logical name. ToI                  set the logging level, define the following logical name_E                  with a value from 1 to 6, where 6 indicates the most0;                  amount of debugging information available:0  $                  TCPIP$NTP_LOG_LEVEL  H               o  NTP now has dynamic auto-detection for the existence ofI                  the DTSS time service on your system. If DTSS is enabledDH                  at NTP startup time, or if DTSS is enabled while NTP isF                  already running, NTP will not make adjustments to theH                  system clock. Clock adjustements will resume if DTSS isI                  disabled. NTP will continue to be able to service clientLD                  requests and hand out timestamps even when disabledE                  from making clock adjustments. You no longer need toaI                  disable NTP from setting the clock in the TCPIP$NTP.CONF $                  configuration file.  %         1-44 New Features and Changest N  T      I                                                  New Features and ChangesOI                                                   1.2 Version 5.1 Changesn    I               o  The implementation of NTP included with this release hasC/                  enhanced messages, as follows:a  D                  o  A new message has been added. The new message isH                     output to the log file every hour. It contains basicI                     information about the operation of NTP, including thelI                     time offset, the intrinsic clock frequency error (thelG                     drift), and the polling interval. An example of the .                     new message is as follows:  J         28 Jan 14:00:48 offset: 0.012843 sec freq: -3.186 ppm poll: 64 sec  E                  o  Additional information is displayed if you try to E                     run the TCPIP$NTPDATE utility when NTP is already )                     running. For example:e  #         $ NTPDATE:==$TCIPIP$NTPDATE          $ NTPDATE FRED         Socket bind error.K         Verify that the NTP server (TCPIP$NTP) is not running on this host.h)         %SYSTEM-F-DUPLNAM, duplicate namea  E                  In addition to these messages, the NTP log file name I                  has been changed. The NTP messages are now logged to the                    following file:  "                  TCPIP$NTP_RUN.LOG           1.2.9 DHCP Changes  I               If you use DHCP under previous versions of TCP/IP Services, E               please be aware of the following changes in the current                release:  8               o  Change to handling of the DHCP log file  E                  When the DHCP server starts, it creates the log file F                  TCPIP$DHCP_RUN.LOG file. This log file is used duringI                  the beginning of the DHCP server initialization process. H                  By default, the same file name is also used for new log7                  files created as the DHCP server runs.   D                  You can specify a different file name for log filesG                  created while DHCP is running. To specify the log file 4                  name, define the following logical:  <                  $ DEFINE /SYSTEM TCPIP$DHCP_LOG "file name"  I                                             New Features and Changes 1-45  M  f                New Features and Changes         1.2 Version 5.1 Changesb    F                  When you define the TCPIP$DHCP_LOG logical, DHCP willI                  always generate two log files: TCPIP$DHCP_RUN.LOG, whichOH                  includes messages from initialization, and the file youH                  specified, which includes messages from DHCP operation.  F                  If the DHCP server is running on multiple nodes in anF                  OpenVMS cluster where the nodes share the same systemE                  disk (SYS$SYSDEVICE), and the TCPIP$DHCP_LOG logicalSG                  is not defined, it can be difficult to determine whichrE                  version of the TCPIP$DHCP_RUN.LOG file is associatedmI                  with each node. To find out which node generated it, youN+                  must open the file itself.   G                  You can use the TCPIP$DHCP_LOG logical to resolve this &                  problem. For example:  2                  $ DEFINE /SYSTEM TCPIP$DHCP_LOG -B                  $_"TCPIP$DHCP_SERVER_''F$GETSYI("NODENAME")'.LOG"  F                  If you define the logical this way, the resulting logG                  file names reflect the node names from which they were H                  generated. For example, node MOE generates the log file+                  TCPIP$DHCP_SERVER_MOE.LOG.   B               o  Changes in DHCP binary databases require rollover  F                  There have been changes in the internal format of theE                  DHCP binary database files, which are the files that H                  look like DB%.HSH and DB%.BTR. A database rollover mustH                  be performed in order for these files to be used by the2                  TCP/IP Services V5.1 DHCP server.  G                  The rollover is run for you automatically when you run G                  TCPIP$CONFIG if you have DHCP configured as an enabled                   service.n  ?                  The rollover creates a "flag file" to indicate C                  that the rollover has been done and that the files A                  in the directory are in V5.1 format. The file is C                  named TCPIP$DHCP_V50_V51_DBROLL.FLG and resides in A                  the TCPIP$DHCP_CONFIG directory, if you use thatUD                  logical, or in the DHCP account's default directoryF                  (SYS$SYSDEVICE:[TCPIP$DHCP]) otherwise. Do not deleteE                  it. The DHCP server startup procedure will not allow ?                  DHCP server to start if the file is not there.G  %         1-46 New Features and Changes  n  b      I                                                  New Features and Changes I                                                   1.2 Version 5.1 Changes1    G                  You may have formerly used the DHCP server but have it3E                  turned off. If you run TCPIP$CONFIG to turn the DHCP D                  server back on, the rollover procedure will ask youG                  if you want to rollover the existing database files orEI                  delete them and start fresh. It will do what you ask and $                  create a flag file.  ;               o  V5.0 and V5.1 DHCP servers cannot co-exist   E                  Since the servers use different database formats you I                  may not run the V5.0 DHCP server against the same set of I                  files as the V5.1 DHCP server. If you are using multiple H                  nodes in your cluster as DHCP servers they must all run5                  the same version of TCP/IP Services.o  /               o  SERVER.PCY supports new fields   E                  The V5.1 DHCP server supports some new fields in theoC                  SERVER.PCY file. A new SERVER.PCY template file inRE                  SYS$LIBRARY:TCPIP$TEMPLATES.TLB contains comments to D                  describe the new fields. It also contains advice onE                  which fields to set for dynamic DNS updates. You can H                  extract the new SERVER.PCY template file and merge yourG                  existing SERVER.PCY file into it. To extract it, enterp'                  the following command:l  E         $ LIBRARY/EXTRACT=SERVER_PCY SYS$LIBRARY:TCPIP$TEMPLATES.TLB-l         _$/OUT=SERVER.PCY   H                  If you do not extract the new SERVER.PCY file, the DHCPH                  server will continue to function as it always has, withE                  backwards compatability. Some of the comments in the '                  file will be obsolete.            1.2.10 BIND Changese  D               If you are using the BIND server and BIND resolver, beH               aware of the following changes under TCP/IP Services V5.1.  3         1.2.10.1 Editable Network Services Database   B               This version of TCP/IP Services provides an editable<               text version of the network services database,G               TCPIP$ETC:SERVICES.DAT. This database has the same formatgD               as the UNIX /etc/services file. When you configure theE               BIND resolver using TCPIP$CONFIG.COM, the template file,0               TCPIP$ETC:SERVICES.DAT is created.  I                                             New Features and Changes 1-47_ _  _                New Features and Changes         1.2 Version 5.1 Changesm    D               To support use of the TCPIP$ETC:SERVICES.DAT file, the=               following routines are defined in the DECC RTL:e  G               o  struct servent *getservbyname( char *name, char *protoo                  );e  G               o  struct servent *getservbyport( int port, char*proto );e  4               o  struct servent *getservent( void );  2               o  void setservent( int stay_open );  )               o  void endservent( void );S  ?               The getservbyname() and getservbyport() functionshC               search the traditional (RMS indexed) service databaseAA               first. If the requested service is not found there, D               TCPIP$ETC:SERVICES.DAT is searched before returning an7               error to the calling application program.   F                 ________________________ Note ________________________  B                 The TCPIP management commands SET SERVICE and SHOWA                 SERVICE do not operate on this file and will only F                 affect the traditional (RMS indexed) service database.  F                 ______________________________________________________  G               If you are using WKS records in your BIND domain database.G               and also have dynamic updates enabled, the WKS record may1C               get truncated when the database file is automatically C               written to disk by the BIND server. In order to avoid A               this, you should define the specified service(s) in:E               TCPIP$ETC:SERVICES.DAT. For example, if your WKS record                 appears like this:  E               wkstest     IN      WKS     1.2.3.4 tcp ( telnet smtp )8  G               It would get truncated to the following when the database !               is written to disk:7  5               wkstest     IN      WKS     1.2.3.4 tcpQ  8               In this case, add the following entries to+               TCPIP$ETC:TCPIP$SERVICES.DAT:   %         1-48 New Features and Changes     F      I                                                  New Features and Changes I                                                   1.2 Version 5.1 Changes     4               telnet    23/tcp        [telnet_alias]2               smtp      25/tcp        [mail_alias]  F                 ________________________ Note ________________________  ,                 TELNET aliases are optional.  F                 ______________________________________________________  A         1.2.10.2 BIND Server Merges Dynamic Updates Automaticallya  D               The default behaviour of not merging (writing to disk)F               dynamic updates has been changed. Before this release, aF               user would have to define the logical TCPIP$BIND_SERVER_G               MERGE_DYNAMIC_UPDATES to have dynamic updates merged into I               the domain.DB file on an hourly basis. Now this action will H               be performed by default. To disable this behaviour, define$               the following logical:  3               TCPIP$BIND_DONT_MERGE_DYNAMIC_UPDATES            1.2.11 SMTP Changes   F               This release includes the following changes to the SMTP:  E               o  Specifying IP address for alternate gateway The SMTPTD                  alternate gateway now accepts an IP address for theH                  configured alternate gateway. This command is specified                  as follows:  ;                  TCPIP> SET CONFIG SMTP/GATE=ALT=IP-addressg  E                  Where IP-address is the IP address of the configuredcF                  alternate gateway. This syntax is handled differentlyG                  than if you specify a host name. If you specify a hosteI                  name, SMTP performs a MX record lookup to resolve it. If H                  you specify an IP address, however, no MX record lookupE                  is performed. The address is used literally and SMTP G                  connects to the specified address each time mail needs <                  to be routed through the alternate gateway.  +               o  Comment text in To: headeru  E                  This release supports preserving comment text in the B                  To: header. By default, when SMTP composes a mailG                  message, it strips off any comments you may enter intoiH                  the recipient address. This is a problem for users that4                  depend on commands in the To: line.  I                                             New Features and Changes 1-49n c  i                New Features and Changes         1.2 Version 5.1 ChangesP    E                  This release allows the user to tell SMTP to use theeG                  text of the recipient address in the To: header rather F                  than stripping off the comments, which is the default                  behavior.  I                  To turn on the feature, the user defines the TCPIP$SMTP_sE                  USE_VERBATIM_TO logical. Set the logical to either 1eH                  (on) or 0 (off). Compaq recommends that this logical beG                  defined for the specific process, not system-wide. Forl                  example:y  6                  $ DEFINE TCPIP$SMTP_USE_VERBATIM_TO 1  F                  After the logical is defined, you can send an OpenVMS)                  mail message as follows:            $ MAIL Z.Z/SUB=TEST - J         $_SMTP%"""/name=karen/fax=95924121/<default@warpig.cxo.dec.com>"""  I                  Because the logical is defined, the following To: header 0                  is applied to the mail message:  J                  To: /name=karen/fax=95924121/<default@warpig.cxo.dec.com>  G                  If the logical is not defined, the SMTP server appliesn*                  the following To: header:  /                  To: default@warpig.cxo.dec.comu  F                 ________________________ Note ________________________  F                 Be aware of the following limitations and restrictions&                 in using this feature:  D                    o  The address you enter must comply with RFC 822A                       specifications for a To: recipient address.l  B                    o  This change does not affect the address usedD                       in the SMTP dialog RCPT TO command. It affectsC                       the RFC 822 To: header in the message itself. D                       The RCPT TO address will be the address, fully9                       qualified and stripped of comments.   ?                    o  This feature should be used with caution,UD                       because the To: header becomes what you enter.A                       If you enter an unqualified address the To: B                       header will be unqualified, which may not be@                       what you expect and might cause unexpected                       results.  %         1-50 New Features and ChangesL a  u      I                                                  New Features and Changes I                                                   1.2 Version 5.1 Changes     D                    o  Use three double quotes after the SMTP% jacketA                       as in the example above to preserve case ife)                       there is a need to.   F                 ______________________________________________________  B               o  Quotation marks in the OpenVMS Mail personal name  H                  This release supports the use of double quotes ("name")A                  in the OpenVMS personal name. If the SMTP mailertB                  encounters double quotes in the personal name, it8                  changes them to single quotes ('name').  #         1.2.12 Message Improvementss  H               The following changes reflect improvements in the messages/               you receive from TCP/IP Services:N  D               o  Applications started before TCP/IP Services display+                  "Network is down" message.S  I                  In previous versions of TCP/IP Services, if the softwarelA                  had not been started when users attempt to starttD                  applications like TELNET, FTP, and RLOGIN, the HostF                  not available message was displayed. This message wasF                  misleading and did not provide sufficient informationA                  for understanding the problem that prevented the +                  application from starting.b  B                  With the current version of TCP/IP Services, whenD                  applications are started before the TCP/IP ServicesD                  software has been started, the following message is                  displayed:   /                  TCPIP$_NOINET, Network is downh  A                  The following socket routines have been changed:t                    o  accept()  #                  o  gethostbyaddr()   #                  o  gethostbyname()n                    o  select()                    o  socket()  E                  These routines now set ERRNO to ENETDOWN, indicatinguH                  that the TCP/IP Services software has not been started.  I                                             New Features and Changes 1-51  l                   New Features and Changes         1.2 Version 5.1 Changesw    A                  For compatability with existing code, the socketlF                  routines must set ERRNO to a value less than __ERRNO_H                  MAX. Setting VAXC$ERRNO to the TCPIP$_NOINET value usedH                  by applications would cause ERRNO to be set to EVMSERR,G                  which falls outside the required range and breaks code "                  ported from UNIX.  E               o  The TELNET client returns a secondary error code fora                  INVHOST.   F                  If the TELNET client fails because of an invalid hostD                  (INVHOST) error, a second message is displayed thatF                  provides more information. The additional informationF                  can help you determine the actual problem that caused(                  the error. For example:                    $ TELNET JUNK?                  %TELNET-E-IVHOST, Invalid or unknown host junka?                  -TCPIP-E-HOST_NOT_FOUND, no such host is known                   $  H                  This example shows the secondary message ("no such hostG                  is known"), which indicates that the problem is in thenE                  host name entered on the command line, rather than a 6                  temporary failure in network service.  I               o  The TCPIP$STARTUP.COM procedure now issues the followingl!                  timing messages:   S         %TCPIP-I-INFO, TCP/IP Services startup beginning at 18-MAY-1999 18:39:10.40nX         %TCPIP-S-STARTDONE, TCP/IP Services startup completed at 18-MAY-1999 18:39:10:48  C                  In addition, the following message is displayed if1I                  SYS$STARTUP:TCPIP$SYSTARTUP.COM is about to be executed:.  V         %TCPIP-I-INFO, executing site-specific startup SYS$STARTUP:TCPIP$SYSTARTUP.COM  F                  These messages help you determine whether problems inE                  system startup are happening in TCPIP$STARTUP.COM oru                  not.i  =         1.2.13 Adjusting Interrupt Stack Pages on VAX Systems   F               This version of TCP/IP Services requires you to increaseG               the value of the SYSGEN parameter INTSTKPAGES to at least <               12 before starting the network on VAX systems.  %         1-52 New Features and Changesi t         I                                                  New Features and ChangescI                                                   1.2 Version 5.1 Changest             1.2.14 TELNET Changest  F               The display from the TELNET command SHOW DEVICE has beenH               changed to reflect the size of the address string for IPv6D               and full host names. The default display from the SHOWF               DEVICE command now includes two lines of information for'               each device. For example:                   TELNET>SHOW DEVICE:               TNA21:   BG6364:  Temporary Local:  hosta:23E                                           Remote: mynode.abc.com:1024P:               TNA83:   BG5014:  Temporary Local:  hosta:23F                                           Remote: myalpha.abc.com:10798               TNA88:            Temporary Local:  (none)8                                           Remote: (none)  *         1.2.15 Programming Example Changes  E               The example programs supplied with TCP/IP Services haves@               been enhanced and updated. The programming exampleD               files are installed in the directory pointed to by the*               TCPIP$EXAMPLES logical name.  B               For information about using the programming examplesG               provided with TCP/IP Services, refer to the Compaq TCP/IP B               Services for OpenVMS Sockets API and System Services                Programming guide.  *         1.2.16 SHOW DEVICE Command Changes  D               In this release, the behavior of the TCP/IP management.               command SHOW DEVICE has changed.  C               In previous releases of TCP/IP Services, the software E               always attempts to resolve internet addresses using the I               local hosts database. To resolve addresses not in the hosts F               database, you include the /NOLOCAL qualifier to the SHOW               DEVICE command.   H               With the current release, the SHOW DEVICE command does notH               attempt to resolve addresses using the hosts database. TheF               /NOLOCAL qualifier can be used to control both local and*               remote host name resolution.    I                                             New Features and Changes 1-53o t  r                New Features and Changes         1.2 Version 5.1 Changest    6         1.2.17 Server Inactivity Timer Is Not Enforced  D               TCP/IP Services no longer enforces an inactivity timerC               for processes created by the INETACP. This means that-E               once a process is created for a server, the server willmE               endure until that service is shut down. Improvements in H               the OpenVMS operating system have altered the cost/benefitI               ratio of enduring servers so that they should be preferred. D               Enduring servers allow for more predictable and fasterD               responses to connection requests at a very low cost in               system resources.m  G               The TCP/IP management command SHOW SERVICE /FULL shows anmH               entry for the Inactivity field. However, that value has noF               effect. The FTP service is a good example of the changed               behavior.   G               Some system managers have arranged for processes like theeC               FTP server (TCPIP$FTP_SERVER) to exit after the value D               specified in the FTP service inactivity field. The FTPG               server process is created when the FTP service is enabledSB               (typically at system boot). It endures until the FTPE               service is disabled (typically at system reboot). Other H               services handle the creation and maintenance of the server*               process in a similar manner.  C               The FTP server process itself checks the logical name H               TCPIP$FTPD_IDLETIMEOUT and uses that value, or the defaultI               setting, to cause the processes that perform the actual FTPT>               transfers (TCPIP$FTP_CHILD processes) to expire.  %         1.3 Version 5.1 Documentationn  D               The TCP/IP Services for OpenVMS documentation has beenH               revised and expanded to support Version 5.1. The following?               manuals have been added to the documentation set:r  >               o  Compaq TCP/IP Services for OpenVMS Tuning and                   Troubleshooting  E                  This new manual provides system and network managers C                  with information they need to identify and resolve E                  problems. Use this guide to solve general networkingmG                  software problems. For problems restricted to specificeI                  TCP/IP services, refer to the appropriate chapter in the E                  Compaq TCP/IP Services for OpenVMS Management guide.   A               o  Compaq TCP/IP Services for OpenVMS Guide to IPv6   %         1-54 New Features and Changess c  e      I                                                  New Features and Changes I                                             1.3 Version 5.1 Documentationn    D                  This new manual describes the IPv6 environment, theD                  roles of systems in this environment, the types andE                  function of the different IPv6 addresses, and how to .                  connect to the 6bone network.  H               Several existing manuals have been revised to reflect this4               version of TCP/IP Services, including:  D               o  Compaq TCP/IP Services for OpenVMS Installation and                  Configuration  >               o  Compaq TCP/IP Services for OpenVMS Management  F               o  Compaq TCP/IP Services for OpenVMS Management Command                  Reference  C               o  Compaq TCP/IP Services for OpenVMS Sockets API and ,                  System Services Programming  H               o  Compaq TCP/IP Services for OpenVMS SNMP Programming and                  Reference  E               These manuals are provided as part of the field test of D               the TCP/IP Services software. Information presented inH               these manuals is confidential and subject to the terms and+               conditions of the field test.                                       I                                             New Features and Changes 1-55d b                       I                                                                         2 I         _________________________________________________________________C  I                            Installation, Configuration, and Startup NotesF    D               Use this chapter in conjunction with the Compaq TCP/IPA               Services for OpenVMS Installation and Configurations               manual.            2.1 Configuring IPv6  D               The following sections describe procedures specific to2               systems where IPv6 is to be enabled.  3         2.1.1 Information for Users of the IPv6 EAKa  B               The TCP/IP Services external field test (EFT) kit isD               intended to replace the TCP/IP Services V5.0 and V5.0A               software.   H               If you are running any version of the TCP/IP Services V5.0E               IPv6 EAK (early adopter's kit), remove the EAK and then F               install the TCP/IP Services V5.1 software. You must thenI               run the TCPIP$IP6_SETUP.COM command procedure. Refer to the G               Compaq TCP/IP Services for OpenVMS Guide to IPv6 for more                information.  E               There has been a change in the definition of a sockaddr C               structure, which breaks binary compatibility for IPv61G               applications that were compiled using the TCP/IP ServiceseG               V5.0 EAK. You must recompile and relink your applicationst4               after installing TCP/IP Services V5.1.  1         2.1.2 Warning Message in TCPIP$CONFIG.COMi  I               If you have run the TCPIP$IP6_SETUP.COM procedure to enablewH               IPv6, then you run the TCPIP$CONFIG.COM command procedure,E               TCPIP$CONFIG.COM displays the following warning message :               when you select the Core environment option:    I                        Installation, Configuration, and Startup Notes 2-1e           6         Installation, Configuration, and Startup Notes         2.1 Configuring IPv6    0                                          WARNING  Q               This node has been configured for IPv6.  If you make any additional J               changes to the configuration of the interfaces, you must runL               TCPIP$IP6_SETUP again and update your host name information in6               BIND/DNS for the changes to take effect.  3         2.2 Removing Prior Versions of this Producta  D               This section provides important information you shouldF               review before installing the TCP/IP Services Version 5.1               software.r  3         2.2.1 Saving Mail Messages When You Upgraded  E               The new version of SMTP includes control files that aretH               different from previous versions. Before upgrading to thisI               version of TCP/IP Services, run the ANALYZE utility to picke=               up any dead letters on your system, as follows:c  #               $ ANALYZE MAIL/REPAIR   +         2.2.2 Upgrading OpenVMS VAX Systemsn  A               The command procedure SYS$UPDATE:UCX$CLEANUP.COM is I               typically used to clean up a previous version of the TCP/IP D               Services product. However, running this procedure whenH               TCP/IP Services Version 5.1 is installed will remove files9               necessary for the operation of the product.l  G                 _______________________ Caution _______________________R  B                 Do not run UCX$CLEANUP after installing the TCP/IPF                 Services Version 5.1 product on an OpenVMS VAX system.B                 If you run this command procedure, it will corrupt>                 your TCP/IP Services Version 5.1 installation.  F                 ______________________________________________________  @               Compaq strongly recommends you remove this commandD               procedure after installing the TCP/IP Services Version               5.1 kit.      :         2-2 Installation, Configuration, and Startup Notes           I                            Installation, Configuration, and Startup Notes I                2.3 System Page Table Entries Parameter (VAX Systems Only)a    B         2.3 System Page Table Entries Parameter (VAX Systems Only)  D               On VAX systems, make sure the AUTOGEN parameter SPTREQF               is set to at least 6000. Run SYSMAN to check the minimum&               SPTREQ value as follows:           $ RUN SYS$SYSTEM:SYSMAN   %         SYSMAN> parameter show sptreqt?         %SYSMAN, a USE ACTIVE has been defaulted on node VMSVAXs  0         Node VMSVAX:   Parameters in use: ACTIVEP         Parameter Name    Current    Default    Minimum    Maximum Unit  DynamicP         --------------    -------    -------    -------    ------- ----  -------H         SPTREQ               8000       3900       3000         -1 Pages           SYSMAN>u  C               To modify the minimum SPTREQ, run the AUTOGEN commandlE               procedure as described in the OpenVMS System ManagementcH               Utilities Reference Manual: A-L. Modify the minimum SPTREQ               value as follows:                  MIN_SPTREQ = 6000   4         2.4 Some UCX Files Remain After Installation  G               After installing and starting the TCP/IP Services Version G               5.1 product, you may notice some files with a UCX$ prefix G               (most other files provided by this product use the prefix F               TCPIP$). The existence of these files (see Table 2-1) isI               normal and expected. They are required to maintain backward F               compatibility with previous versions of TCP/IP Services.  I         Table_2-1_UCX_Files_Remaining_After_Installation_________________.  I         File____________________________Description______________________a  I         SYS$LIBRARY:UCX$IPC_SHR.EXE     Allows the DEC C Run-Time Library D                                         (RTL) to use TCP/IP sockets.  I                                                  (continued on next page)e      I                        Installation, Configuration, and Startup Notes 2-3            6         Installation, Configuration, and Startup Notes4         2.4 Some UCX Files Remain After Installation    I         Table_2-1_(Cont.)_UCX_Files_Remaining_After_Installation_________   I         File____________________________Description______________________t  I         SYS$LIBRARY:UCX$INETDEF.ADA     The INETDEF files are shipped fornG                                         compatibility with applicationstG                                         developed under TCP/IP Services D                                         Version 4.2. These files areF                                         identical to the files shipped8                                         with Version 4.2  #         SYS$LIBRARY:UCX$INETDEF.BASd  #         SYS$LIBRARY:UCX$INETDEF.FORO  !         SYS$LIBRARY:UCX$INETDEF.H   #         SYS$LIBRARY:UCX$INETDEF.MAR   #         SYS$LIBRARY:UCX$INETDEF.PASc  #         SYS$LIBRARY:UCX$INETDEF.PLIa  #         SYS$LIBRARY:UCX$INETDEF.R32n  D         SYS$COMMON:[SYSEXE]UCX$UCP.EXE  An empty (zero block) markerF                                         file which allows some layeredI                                         products which use an unsupported D                                         test for the presence of theF                                         TCP/IP Services to continue to0                                         operate.  *         SYS$COMMON:[SYSEXE]UCX$SERVICE.DAT  I                                         An empty (zero block) marker file G                                         may be created if the file does H                                         not exist when TCPIP$STARTUP.COMA                                         executes. The file speci- @                                         fied by the logical nameH                                         TCPIP$SERVICE (which defaults toM                                         SYS$COMMON:[SYSEXE]TCPIP$SERVICE.DAT) C                                         contains the actual service 4                                         information.  I                                                  (continued on next page)   :         2-4 Installation, Configuration, and Startup Notes E  U      I                            Installation, Configuration, and Startup Notes I                              2.4 Some UCX Files Remain After Installation     I         Table_2-1_(Cont.)_UCX_Files_Remaining_After_Installation_________   I         File____________________________Description______________________   <         SYS$STARTUP:UCX$STARTUP.COM     These files print an@         SYS$STARTUP:UCX$CONFIG.COM      informational message toD                                         SYS$OUTPUT, then execute theF                                         corresponding TCPIP file. ThisB                                         allows the TCP/IP ServicesF                                         product to continue to operateH                                         until the system manager changesD                                         command files to use the new5                                         TCPIP prefix.t  H         SYS$SYSTEM:UCX$LPD_SMB.EXE      Maintains backward compatibility<                                         for LPD print queue.  E         SYS$SHARE:UCX$ESNMP_SHR.EXE     Shareable images required for E         SYS$SHARE:UCX$ACCESS_SHR.EXE    user-written programs written F         SYS$SHARE:UCX$RPCXDR_SHR.EXE    under previous versions of the0                                         product.  ,         SYS$COMMON:[SYSEXE]UCX$TELNETSYM.EXE  I                                         TELNET print symbiont executable. A                                         This file is identical to I         ________________________________TCPIP$TELNETSYM.EXE._____________   =         2.5 Starting the Product After a Minimum OpenVMS Boot   F               If you boot OpenVMS with the SYSGEN parameter STARTUP_P1G               defined to something other than the default blank string,n9               not all portions of OpenVMS may be started.   C               A check has been added to the TCP/IP Services startup D               procedure SYS$STARTUP:TCPIP$STARTUP.COM to detect when=               OpenVMS has been booted in an alternate manner.   D               If the startup procedure SYS$STARTUP:TCPIP$STARTUP.COMI               detects a MIN, INST, or UPGRADE boot, it displays a message E               and exits, setting $SEVERITY to ERROR. For example, the8G               following message is displayed if a MIN boot is detected.   A               %TCPIP-E-STARTFAIL, failed to start TCP/IP Services =               -TCPIP-E-UNSUPPORTED, option boot not supportedc  B               Where option represents the type of installation you.               started (MIN, INST, or UPGRADE).  I                        Installation, Configuration, and Startup Notes 2-5            6         Installation, Configuration, and Startup Notes=         2.5 Starting the Product After a Minimum OpenVMS BootI    I               This check helps ensure that conditions required for proper 3               operation of TCP/IP Services are met.E  G               For example, if OpenVMS and TCP/IP Services are installedIG               from a CD-ROM or a server, and OpenVMS is booted from the I               same medium, the boot type will be INST. The TCP/IP startuplD               procedure will fail in this case, because TCPIP$CONFIGI               cannot write configuration files to the SYS$SYSTEM: area on &               a CD-ROM or server disk.  8         2.6 Preserving LPD Startup and Shutdown Behavior  B               Your LPD startup and shutdown command procedures mayE               contain site-specific edits. You must manually preserve C               these edits when upgrading to TCP/IP Services Version G               5.1 from a previous version. The procedure for preserving F               your edits differs for OpenVMS Alpha systems and OpenVMSD               VAX systems. Follow the instructions below to preserveG               your site-specific startup and shutdown command procedureS               files.  !         2.6.1 OpenVMS Alpha Users   B               When you install TCP/IP Services Version 5.1 over anE               earlier version of the product, follow the instructions H               displayed on your screen to preserve your edits in the LPD6               startup and shutdown command procedures.  :               The following shows a sample screen display.  ?         The following product will be installed to destination:dN             DEC AXPVMS TCPIP V5.1-9                DISK$ALPHASYS:[VMS$COMMON.]  &         UCX product already installed.  O         *********************************************************************** N         Another version of TCP/IP is installed. You must execute the following@         three commands before continuing with this installation::         $ BACKUP SYS$COMMON:[SYSMGR]UCX$LPD_STARTUP.COM; -6              SYS$COMMON:[SYSMGR]TCPIP$LPD_STARTUP.COM;;         $ BACKUP SYS$COMMON:[SYSMGR]UCX$LPD_SHUTDOWN.COM; - 7              SYS$COMMON:[SYSMGR]TCPIP$LPD_SHUTDOWN.COM;          $ PRODUCT REMOVE UCXO         ***********************************************************************o  :         2-6 Installation, Configuration, and Startup Notes t  c      I                            Installation, Configuration, and Startup NotesiI                          2.6 Preserving LPD Startup and Shutdown Behavior     D               After following these instructions, and completing theF               installation of TCP/IP V5.1, your site-specific edits to>               the LPD startup and shutdown files are found in:  =                  SYS$COMMON:[SYSMGR]TCPIP$LPD_STARTUP.COM_OLD.>                  SYS$COMMON:[SYSMGR]TCPIP$LPD_SHUTDOWN.COM_OLD  6               Now merge your site-specific edits into:  ;                  SYS$COMMON:[SYSMGR]TCPIP$LPD_SYSTARTUP.COMi<                  SYS$COMMON:[SYSMGR]TCPIP$LPD_SYSHUTDOWN.COM           2.6.2 OpenVMS VAX UsersC  A               To preserve your site-specific startup and shutdowngH               information, you must install TCP/IP Services Version 5.1,5               then copy the site-specific edits from:f  7                  SYS$COMMON:[SYSMGR]UCX$LPD_STARTUP.COMo8                  SYS$COMMON:[SYSMGR]UCX$LPD_SHUTDOWN.COM  %               to the following files:e  9                  SYS$COMMON:[SYSMGR]TCPIP$LPD_STARTUP.COMc:                  SYS$COMMON:[SYSMGR]TCPIP$LPD_SHUTDOWN.COM  <         2.6.3 Troubleshooting SMTP and LPD Shutdown Problems  F               If SMTP or LPD shutdown generates errors indicating thatH               the queue manager is not running, check your site-specificF               shutdown command procedure (VMS_SYSHUTDOWN.COM). If thisF               procedure contains the command to stop the queue managerF               (STOP/QUEUE/MANAGER), make sure this command comes afterA               any invokation of the TCPIP$SHUTDOWN.COM procedure.v  F                 ________________________ Note ________________________  @                 It is not necessary to explicitly stop the queue@                 manager. The queue manager will be automatically@                 stopped and started when you restart the system.  F                 ______________________________________________________      I                        Installation, Configuration, and Startup Notes 2-7a e  t      6         Installation, Configuration, and Startup Notes8         2.6 Preserving LPD Startup and Shutdown Behavior    '         2.6.4 Merging Edits (All Users)   I               When merging edits, do not append the commands to start and H               stop the queue UCX$LPD_QUEUE. This queue has been replacedH               with TCPIP$LPD_QUEUE, and the commands for TCPIP$LPD_QUEUEE               will already be in the LPD startup and shutdown commandt               procedure files.  F               After merging the edits, set the value of the /PROCESSORI               qualifier in the LPD client queue startup commands that you F               have just appended to point to TCPIP$LPD_SMB rather than               UCX$LPD_SMB.  K                   LSE Command> SUBSTITUTE/ALL "ucx$lpd_smb" "tcpip$lpd_smb"   '         2.7 SNMP Installation and Setupa  G               The following sections describe procedures for installing "               and setting up SNMP.  -         2.7.1 Verifying the SNMP Installationt  I               A separate installation verification procedure (IVP) exists D               for SNMP. To verify your configuration, complete these               steps:  A               1. Be sure that your process has SYSTEM privileges.a  +               2. Run the command procedure:f  ,                  $ @SYS$MANAGER:TCPIP$CONFIG  G               3. Enter option 7 (Run tests), and then option 2 from the >                  Compaq TCP/IP Services for OpenVMS TEST Menu.  >               4. To run the SNMPIVP any time after exiting theD                  configuration procedure, use the following command:  B                  $ RUN SYS$COMMON:[SYSTEST.TCPIP]TCPIP$SNMPIVP.EXE  ;         2.7.2 Preserving SNMP Startup and Shutdown BehaviorO  H               After you upgrade to TCP/IP Services Version 5.1, you mustI               perform one of the following actions to ensure correct SNMPu               startup:  D               o  If SNMP had been configured under a previous TCP/IPG                  Services installation (UCX) and you want to retain theaI                  previous configuration, run SYS$MANAGER:TCPIP$CONFIG.COMs  :         2-8 Installation, Configuration, and Startup Notes           I                            Installation, Configuration, and Startup Notes I                                           2.7 SNMP Installation and Setup     C                  and select the option to automatically convert UCXh%                  configuration files.o  F               o  After you upgrade to this version of TCP/IP Services,C                  run SYS$MANAGER:TCPIP$CONFIG.COM. If SNMP is stilltD                  enabled, disable SNMP then enable it again. This isF                  necessary for the proper operation of this component.  ?               If you customized versions of the files UCX$SNMP_cF               STARTUP.COM and UCX$SNMP_SHUTDOWN.COM (used to start andC               stop extension subagents), save your customized filesDA               to a different directory before upgrading to TCP/IPVD               Services Version 5.1. If you do not perform this step,I               your customized changes will be lost. Check for versions ofI5               these files in the following locations:                  o  SYS$MANAGER                 o  SYS$STARTUP  )               o  SYS$SYSDEVICE:[UCX$SNMP]l  ?               After you install TCP/IP Services, manually mergeeA               your saved changes into the new files created afterhF               installation. See the Compaq TCP/IP Services for OpenVMS4               Management guide for more information.  ;         2.8 Setting Up the TCP/IP Services Message Database   F               At installation, the TCP/IP Services message database is@               installed at SYS$COMMON:[SYSHLP]TCPIP.MSGHLP$DATA.  D               To get information about TCP/IP messages, include thisE               database with the OpenVMS message database, as follows:   G               1. Define the logical name MSGHLP$LIBRARY to point to all_0                  the databases in the directory:  P                  $ DEFINE/SYSTEM MSGHLP$LIBRARY SYS$COMMON:[SYSHLP]*.MSGHLP$DATA  D               2. Enter the DCL command HELP/MESSAGE to make sure theH                  TCP/IP message database is now recognized. For example:           $ HELP/MESSAGE FTP  C          SESDCN,  FTPD: Session disconnection from 'host' at 'time'_  )           Facility:     TCPIP, FTP Servers  I                        Installation, Configuration, and Startup Notes 2-9t i  t      6         Installation, Configuration, and Startup Notes;         2.8 Setting Up the TCP/IP Services Message Database     T           Explanation:  This message appears when a session is disconnected, statingS                         the name of the client initiating the disconnection and the 2                         time of the disconnection.             User Action:  None.s  $         Press RETURN to continue ...  H                  In this example, Help Message displays all the messages<                  that contain FTP as part of the message ID.  *         2.9 PROXYERROR Messages at Startup  E               If the proxy database is empty when you start up TCP/IP C               Services, the following error messages are displayed:   A               %TCPIP-E-PROXYERROR, error processing proxy request 6               -TCPIP-W-NORECORD, information not found*               -RMS-E-RNF, record not foundA               %TCPIP-E-PROXYERROR, error processing proxy requestu6               -TCPIP-W-NORECORD, information not found*               -RMS-E-RNF, record not found  D               These messages, also displayed if you enter the TCP/IP<               management command LOAD PROXY, may be ignored.                                        ;         2-10 Installation, Configuration, and Startup Notest a  n                    I                                                                         3 I         _________________________________________________________________   I                                                 Problems and RestrictionsT    B               This chapter provides information about problems and>               restrictions in this version of TCP/IP Services.  )         3.1 NFS Problems and Restrictions/  G               The following sections describe problems and restrictions_               with NFS.   $         3.1.1 NFS Lock Requests Fail  C               If the NFS server and the NFS client are in differentlF               domains and unqualified host names are used in requests,D               the lock server (LOCKD) fails to honor the request and'               leaves the file unlocked.   B               When the server attempts to look up a host using itsD               unqualified host name (for example, johnws) instead ofD               the fully qualified host name (for example, johnws.abcI               com), and the host is not in the same domain as the server,                 the request fails.  B               To solve this type of problem, you can do one of the               following:  E               o  When you configure the NFS client, specify the fullylE                  qualified host name, including the domain name. Thise7                  ensures that translation will succeed.   D               o  Add an entry to the NFS server's hosts database forB                  the client's unqualified host name. Only that NFSF                  server will be able to translate this host name. ThisI                  solution will not work if the client obtains its address '                  dynamically from DHCP.       I                                             Problems and Restrictions 3-1     $      !         Problems and RestrictionsO)         3.1 NFS Problems and Restrictionso    2         3.1.2 NFS Client Problems and Restrictions  G               To get proper timestamps, when the system time is changedsI               for Daylight Savings Time (DST), dismount all DNFS devices.rH               (The TCP/IP management command SHOW MOUNT should show zero9               mounted devices.) Then remount the devices.   1         3.2 DHCP Client Problems and RestrictionsT  H               The TCP/IP managent command SET [NO]INTERFACE command doesD               not tell the DHCP client to release an IP address whenG               writing over an IP address configured by DHCP or deletingT@               the interface. This causes the following problems:  I               o  The system has a lease on an IP address that it does not F                  need because the interface has either been deleted orG                  reconfigured. The leased IP address should be returnedD<                  to the pool for use by another DHCP client.  G               o  The DHCP client process is not told that the interface B                  is no longer under DHCP control. Depending on theE                  specific SET [NO]INTERFACE command that was entered, )                  the following may occur:o  E                  -  If the interface was manually reconfigured with amI                     different IP address using the SET INTERFACE command,iI                     when the DHCP client tries to extend the lease on the_G                     IP address it will reset the interface's address toT&                     the one from DHCP.  >                  -  If the interface was deleted using the SETF                     NOINTERFACE command, when the DHCP client tries toG                     extend the lease on the IP address, the client will I                     incur an error and log it because it will not be able ,                     to get to the interface.  F               To avoid these problems, when you issue any command thatG               would change the IP address of an interface that is undereI               DHCP control, COMPAQ suggests you first enter the following$               DCL command:  '               $ DHCPCONF ifname RELEASE   D               For more information about using the DHCPCONF utility,H               refer to the Compaq TCP/IP Services for OpenVMS Management               guide.  %         3-2 Problems and Restrictions$ R  C      I                                                 Problems and Restrictions I                                        3.3 IPv6 Problems and Restrictions     *         3.3 IPv6 Problems and Restrictions  H               The following sections describe problems that are known to4               exist in the IPv6-enabled environment.           3.3.1 IPv6 Proxy Lookup   E               Communication proxies are not supported under IPv6. The I               client applications included with TCP/IP Services have been E               programmed to resolve proxy requests to IPv4 addresses. C               However, clients requesting IPv6 addresses will fail.   -         3.3.2 IPv6 Requires the BIND Resolveru  F               If you are using IPv6 as described in Section 1.1.2, youC               must enable the BIND resolver. If you do not have the C               BIND resolver configured, you can enable it using the D               TCPIP$CONFIG.COM procedure. From the Core menu, selectH               BIND Resolver. If you do not have access to a BIND server,I               specify the node address 127.0.0.0 as your BIND server. You G               must specify the BIND server to enable the BIND resolver.   4         3.4 RLOGIN Does Not Create Virtual Terminals  E               For a proxy login, the RLOGIN service does not create a I               virtual terminal. For more information, refer to the Compaqa;               TCP/IP Services for OpenVMS Management guide.   0         3.5 TELNET Devices Remain After Shutdown  ?               During shutdown the following message may appear:   H                     WARNING - The following TN devices are still active:                       TNA8:f  E               The TN device persists until the next startup, when theCB               same message may appear. You can safely ignore theseH               messages. They appear because TN devices are deleted usingH               a timer that is deactivated during the shutdown procedure.          I                                             Problems and Restrictions 3-3h Y  Y      !         Problems and Restrictions :         3.6 TELNETSYM Autostart Queues in OpenVMS Clusters    :         3.6 TELNETSYM Autostart Queues in OpenVMS Clusters  =               Autostartable TELNETSYM queues may be restarteduF               automatically if a member node in the cluster goes down.I               The queue manager attempts to start the TELNETSYM queues oneG               all the nodes for which the queues are defined. If one ofsI               the nodes is not running TCP/IP Services, the queue managerwG               will report a failure trying to start TELNETSYM queues onn               that node.  =         3.7 File Locking Requires Compaq C RTL ECO3 or Higherh  H               You must have ECO3 to Compaq C RTL, or a later version, inH               order to use file locking (described in Section 1.1.13.5).E               With earlier versions, the TCPIP$STATD service will notnC               start. This problem is specific to VAX systems and to (               OpenVMS Alpha Version 7.1.  .         3.8 PRODUCT REMOVE TCPIP Error Message  1               When you use the following command:S  $               $ PRODUCT REMOVE TCPIP  4               You may encounter an error similar to:  c         %PCSI-W-OPTREF, product DEC AXPVMS TCPIP T5.1-9R is referenced by DEC AXPVMS OPENVMS V7.2-1   F               This occurs only on systems where the TCP/IP product wasF               installed at the same time as the Operating System. ThisI               error may be ignored, and you can continue with the removal G               of TCPIP. Note that this also applies to the UCX product.M                 For example:           $ PRODUCT REMOVE TCPIP  0         The following product has been selected:B             DEC AXPVMS TCPIP T5.1-9R               Layered Product  *         Do you want to continue? [YES] YES        %         3-4 Problems and Restrictionsi           I                                                 Problems and RestrictionsBI                                    3.8 PRODUCT REMOVE TCPIP Error Messagei    T         %PCSI-W-OPTREF, product DEC AXPVMS TCPIP T5.1-9R is referenced by DEC AXPVMS         OPEt         NVMS V7.2-1lT         -PCSI-W-OPTRF1, this software dependency is expressed within a configurationO         -PCSI-W-OPTRF2,   option that is currently selected for the referencing          productpT         -PCSI-W-OPTRF3, if you want to reconfigure the referencing product or reviewT         -PCSI-W-OPTRF4,   its configuration requirements, answer NO to the followingS         -PCSI-W-OPTRF5,   question to terminate this operation; if you are sure you          wantN         -PCSI-W-OPTRF6,   to remove the referenced product, then answer YES to         proceedd*         Do you want to continue? [YES] YES  ?         The following product will be removed from destination:$N             DEC AXPVMS TCPIP T5.1-9R               DISK$ALPHASYS:[VMS$COMMON.]           Portion done:PG         0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%M  /         The following product has been removed:dB             DEC AXPVMS TCPIP T5.1-9R               Layered ProductP         %PCSIUI-I-COMPWERR, operation completed after explicit continuation from         errors  $         3.9 Startup DUPLNAM Messages  C               When you start TCP/IP Services, the following DUPLNAMd"               messages may appear:  :         %TCPIP-S-STARTDONE, TCPIP$TELNET startup completeda         %TCPIP-E-DYNPROXERR, cannot add record to proxy database  (TCPIP$PROXY) in dynamic memory_)         -SYSTEM-F-DUPLNAM, duplicate name a         %TCPIP-E-DYNPROXERR, cannot add record to proxy database  (TCPIP$PROXY) in dynamic memorye)         -SYSTEM-F-DUPLNAM, duplicate name A         %TCPIP-I-LOADSERV, loading TCPIP server proxy information I         %TCPIP-I-SERVLOADED, auxiliary server loaded with 0 proxy records @         -TCPIP-I-SERVSKIP, skipped 0 communication proxy records9         -TCPIP-I-SERVTOTAL, total of 8 proxy records readaX         %TCPIP-S-STARTDONE, TCP/IP Services startup completed at  7-JUN-2000 16:03:51.48  G               These messages can be safely ignored. They are the result D               of a change in the current version of TCP/IP Services.    I                                             Problems and Restrictions 3-5m s  r      !         Problems and Restrictionsa$         3.9 Startup DUPLNAM Messages    I               In previous versions of TCP/IP Services, the proxy databasetI               required that all names for a particular host be entered innH               the hosts database. For example, the host names johnws andF               johnws.abc.com needed to be in the hosts database if anyD               NFS requests were made using either of the host names.  I               With this release of TCP/IP Services, the proxy informationtE               that is loaded includes all of a server's addresses andSG               alias names automatically. Therefore, the first entry for H               a host which is loaded succeeds, and all of the subsequentI               matching entries which only differ in the host's alias name:-               will generate DUPLNAM messages.h  D               Proxy records for the host under both (or more) of theE               host's names will succeed as it did before, because allrA               names (including the duplicates) are indeed loaded.   E               Note that because there is now only one record for each G               host, the removal of a proxy entry under any of the hostsoI               names will remove all of the addresses and aliases for thatSG               host. Subsequent removal attempts under any of the host's 4               other names will also return an error.           3.10 Security Driver  E               Support for the security driver is no longer available.r  !         3.11 Command Restrictions   H               The following restrictions apply to the management control               program commands:(  H               o  In this release of TCP/IP Services, the /HOST qualifierA                  to the SHOW DEVICE_SOCKET command does not work.g  4               o  The SHOW CFS command does not work.  @               o  The INCOMING and OUTGOING arguments to the /NFSC                  qualifier on the REMOVE PROXY command do not work.   :               o  The ROUTE FLUSH command is not supported.  F               o  There is no support for zeroing counters. In previousH                  releases, this was accomplished with the ZERO INTERFACE#                  /COUNTERS command.i  %         3-6 Problems and Restrictionsl N  t      I                                                 Problems and Restrictions I                                                 3.11 Command Restrictions     F                  If you want to see changes over a period of time, youB                  must take a snapshot with a timestamp, wait, takeB                  another snapshot with a timestamp and compare the                  difference.  '               o  SET INTERFACE /CLUSTERs  B                  You must set the cluster network mask and clusterF                  broadcast masks when you define a cluster alias usingI                  the SET INTERFACE /CLUSTER command. In earlier releases, H                  you could add or modify the network and broadcast masks/                  after defining the alias name.c                 o  SET INTERFACE  D                  If you fail to enter all of the required parametersC                  and qualifiers with the SET INTERFACE command, the G                  management control program may behave in an unexpectedtE                  manner. To correct any problems, exit the managementnH                  control program, restart, and reenter the SET INTERFACE                  command.s  '               o  SET NAME_SERVICE /PATHw  I                  This command requires the SYSNAM privilege. If you enter E                  the command without the appropriate privilege at thebF                  process level, the command will not work but you willH                  not be notified. If you enter the command at the systemI                  level, the command will not work but you will receive ani                  error message.   $               o  SET SERVICE command  E                  When you modify parameters to a service, disable andaC                  reenable the service for the modifications to take,                  effect.  (               o  DISABLE SERVICE command  G                  For most services, this command disables the specifiedeE                  service but does not stop the current process if oneaG                  exists. This allows you to perform an orderly shutdownaA                  of the service, preventing new connections while :                  allowing current connections to continue.  9                  To stop and restart the current process:   A                  1. Wait until the process exits or stop it using C                     the service-specific shutdown command procedure 1                     (TCPIP$service_SHUTDOWN.COM).   I                                             Problems and Restrictions 3-7c           !         Problems and Restrictions !         3.11 Command Restrictions,    B                  2. Restart the service using the service-specific=                     startup command procedure (TCPIP$service_                       STARTUP.COM.  G                  Note that, for the NFS server, TELNET, and RLOGIN, thenC                  DISABLE SERVICE command stops the current process.   E                  To stop DHCP, enter the dhcpsigterm command (definedaF                  in SYS$MANAGER:TCPIP$DHCP_SETUPCOMMANDS.COM). See theH                  Compaq TCP/IP Services for OpenVMS Management guide for"                  more information.  G               For information about TCP/IP management commands that are 4               not supported, refer to Section 1.2.1.  *         3.12 NTP Problems and Restrictions  C               The NTP server has a stratum limit of 15. It will notcC               synchronize to any time server that reports a stratumtE               of 15 or greater. This may cause problems if you try todD               synchronize to a server running the UCX NTP server, ifE               that server has been designated as "free-running" (withkI               the "local-master" command). For proper operation in such a I               case, the "local-master" designation must be specified withq+               a stratum no greater than 14.            3.13 Error Messages   @               Some error messages may contain extra blank lines.                 $ FTP host-nameuZ               %TCPIP-E-FTP_HSTINF, cannot get host information for host-name from database  *               -RMS-E-RNF, record not found               $   *         3.14 FTP Problems and Restrictions  C               This section describes FTP problems and restrictions.            3.14.1 GET/FDL Command  I               When connected to a system that is not running OpenVMS, theo&               following command fails:  "               FTP> GET/FDL a/b/c.d  =               In error, FTP attempts to return the file /FDL.a  %         3-8 Problems and Restrictions     A      I                                                 Problems and Restrictions I                                        3.14 FTP Problems and Restrictionst    D               The workaround to this problem is to enter the command+               using the following sequence:                  FTP> cd a/b/               FTP> GET/FDL c.d  G         3.14.2 Extended File Specifications in a Mixed Operating Systemr                Environment  H               With FTP, file names must be valid on the target operatingD               system. It may help to clarify this requirement in theG               context of Extended File Specification names when certain,8               characters in a file name must be escaped.  F               For example, the file A^;b.Dat;3 requires a caret escapeE               before the first semicolon. The transfer and display ofRD               this file name between systems running OpenVMS VersionG               7.2, with parse-style for the process set to EXTENDED andIG               referencing an ODS5 disk, exhibits expected behavior. TheCH               file is displayed as A^;b.Dat;3, and the following command@               results in the file A^;b.Dat; on the local system:                 FTP> get A^;b.Dat   D               The number to the right of the ending semicolon variesG               depending on the version of any previously existing files ,               of that name in the directory.  H               When operating between an OpenVMS system and a system thatI               is not running OpenVMS, the FTP server displays the file as -               A^;b.Dat.3 (.3 rather than ;3).t  H               When entering a GET command for a file A;b.Dat from a UNIXD               system, for example, you must specify the caret in the#               output specification:e  (               FTP> GET A;b.Dat  A^;b.Dat  C               The following command results in a file specification                error:                 FTP> GET A;b.Dat  G               When entering a PUT command, you must manually remove thet:               caret escapes from the output specification:  (               FTP> PUT A^;b.Dat  A;b.Dat  I                                             Problems and Restrictions 3-9            !         Problems and Restrictionss+         3.15 DHCP Problems and Restrictionso    +         3.15 DHCP Problems and Restrictionst  H               The following problems or restrictions are associated with#               this version of DHCP:   >               o  If your network is subnetted in a format that=                  is not consistent with the standard A, B, or :                  C netmask address, make sure you edit theE                  SYS$SYSDEVICE:[TCPIP$DHCP]NETMASKS. file and include G                  an entry for each network. Each entry in the file must-H                  include two fields: the network address and the netmask&                  address. For example:  ,                  #    Network        Netmask  4                       192.1.1.0      255.255.255.2244                       192.1.1.96     255.255.255.240  >               o  To ensure an orderly shutdown of DHCP, invoke9                  SYS$STARTUP:TCPIP$SHUTDOWN.COM from youro6                  SYS$STARTUP:SYSHUTDOWN.COM procedure.  G                  The DHCPSIGTERM command is issued from the TCPIP$DHCP_tG                  SHUTDOWN.COM procedure. When you shut down the system,eG                  the system shutdown procedure runs TCPIP$SHUTDOWN.COM,6I                  which in turn runs TCPIP$DHCP_SHUTDOWN.COM. This process ,                  ensure an orderly shutdown.  H               o  A synchronization problem can occur if BIND lookups are                  slow.  D                  Before the DHCP server assigns a name to a host, itF                  performs a reverse lookup call (gethostbyaddr) to seeG                  if there is already a name associated with the address F                  in BIND. If the call is slow to respond, the client'sE                  repeated requests are ignored, causing the client to E                  change the XID and send additional requests. You canoD                  trace this behavior to the XID field, where the XIDD                  field of the client reply is different from the XID6                  field of the previous client request.  G                  To avoid this synchronization problem, define the hostuC                  and IP address in the local hosts database. Enter:N  8                  TCPIP> SET HOST host/ADDRESS=IP_address  I               o  In the Server/Security tab of the DHCP GUI, the PrintinguG                  parameter is not functioning. At this time, you cannote$                  print from the GUI.  &         3-10 Problems and Restrictions           I                                                 Problems and Restrictions I                                   3.16 PPP/SLIP Problems and Restrictions     /         3.16 PPP/SLIP Problems and Restrictions   E               The following sections describe problems in the PPP andT               SLIP services.  1         3.16.1 Running PPP on OpenVMS Version 7.1u  E               If you are running PPP on OpenVMS Version 7.1, you musthF               have a remedial kit for the ASNDRIVER installed. WithoutG               this kit, PPP may cause a system crash. This kit includessG               the ASNDRIVER and other fixes. Please see the kit's covere&               letter for more details.  ;               You can access the kit and cover letter from:   Z               ftp://ftp.service.digital.com/public/vms/axp/v7.1/alppppd01_071.A-DCX_AXPEXEX               ftp://ftp.service.digital.com/public/vms/axp/v7.1/alppppd01_071.CVRLET_TXT  5         3.16.2 PPPD CONNECT Causes the System to Fail   I               When this version of TCP/IP Services is started, shut down, E               and then started again, then a remote user dials in and D               issues the PPPD CONNECT command, the system fails. TheB               problem is fixed in remedial kits for SYS$PPPDRIVER.  7         3.17 Configuring Your Host as a Dialup Providera  F               The TCP/IP Services product requires the use of a uniqueB               IP address when creating a network interface. If youC               mistakenly assign an IP address that has already been E               assigned to another interface, your PPP connection will D               work but upon termination, any other applications with+               active connections will hang.a  >               You must restart TCP/IP Services if this occurs.  *         3.18 RCP Problems and Restrictions  -               RCP has the following problems:   C               o  The RCP command requires that directories, whetheruD                  specified explicitly or implicitly, be specified asE                  [directory] (with square bracket delimiters). Use ofr;                  angle bracket delimiters is not supported.3  I                                            Problems and Restrictions 3-11E X  S      !         Problems and RestrictionsS*         3.18 RCP Problems and Restrictions    I                  For example, the following commands specify the implicit %                  directory correctly:s  *                  $ SET DEFAULT DISK:[USER]'                  $ RCP A.DAT  XYZ:A.DATy  I                  The following command shows a correct (for RCP) explicitR)                  directory specification:r  .                  $ RCP DISK:[DIR]A.DAT XYZ.DAT  F                  Note that the following commands specify an incorrect>                  implicit directory and may not work reliably:  *                  $ SET DEFAULT DISK:<USER>&                  $ RCP A.DAT XYZ:A.DAT  E                  RCP may exit with a memory access violation (ACCVIO) ?                  when an incorrect logical name and a directory G                  specification of the angle bracket form are (implicity7F                  or explicitly) specified at the same time to RCP. For                  example:T  =                  $ DEFINE/JOB/EXEC SYS$LOGIN_DEVICE SYS$LOGINP6                  $ SET DEFAULT SYS$LOGIN_DEVICE:<USER>'                  $ RCP A.DAT  XYZ:A.DAT   E                  In this example, the first command (DEFINE/JOB/EXEC)lI                  does not contain the trailing colon (:) after the deviceTH                  name. As a result, the RCP command specifies an invalid'                  logical and directory.Y  E               o  When the OpenVMS host running RCP is the source of a H                  file, RCP converts the file into STREAM_LF format. ThisF                  is the equivalent of an FTP or KERMIT ASCII transfer.B                  If the file is actually a binary file, such as anH                  executable file, RCP inserts extra linefeed characters.F                  In most cases, this renders the binary file unusable.  7                  The workaround is to do the following:P          &         3-12 Problems and Restrictions -  -      I                                                 Problems and RestrictionstI                                        3.18 RCP Problems and Restrictionsi    @                  $ dir/full abc.bin  ! note file characteristics,                  $ copy abc.bin abc_copy.bin                  $8                  $ ! Cause $RCP to skip file conversion.?                  $ set file/attributes=(rfm:stmlf) abc_copy.bin                   $?                  $ rcp  abc_copy.bin remote_host:remote_abc.binh:                  $ ! If the remote host is an OpenVMS hostJ                  $ ! then, on the remote host, restore the file attributes<                  $ ! Say the file abc.bin was really abc.exeH                  $  set file remote_abc.exe/attribute=(rfm:fix, lrl:512).                  $ ! $backup expects LRL:32256                  $                  $ ! Donea  D               o  OpenVMS file attributes are lost when RCP transfersA                  files between two OpenVMS systems running TCP/IP F                  Services for OpenVMS. All output files are created in"                  STREAM_LF format.  B         3.19 REUSEADDR Behaviour change in V4.2 to V5.x Transition  B               Using the REUSEADDR socket option produces differentH               results on TCP/IP Services Version 4.2 and TCP/IP Services               Version 5.x.  H               Under Version 4.2, a TCP/IP server with a passive (listen)F               socket was able to run under multiple processes with theE               same IP address and port number. Under Version 5.x, the E               same circumstances result in the following fatal error:e  #               Failed to bind socket /               %SYSTEM-F-DUPLNAM, duplicate namer           3.20 POP Problemsn  H               The following problems with the Post Office Protocol (POP):               server exist in TCP/IP Services Version 5.x:  E               o  Both the TCP/IP Services and IUPOP3 POP servers haveCG                  problems parsing addresses that include personal namesO-                  enclosed in quotation marks.       I                                            Problems and Restrictions 3-13G g  n      !         Problems and Restrictionsr         3.20 POP Problemsd    E               o  Both the TCP/IP Services and IUPOP3 POP servers have.G                  problems parsing addresses that contain a space withins                  the address.i           3.21 SMTP Problems  I               With TCP/IP Services Version 5.x, corruption might occur ind!               SMTP control files.   C               Intermittently, the SMTP server signals an error on a D               particular control file. The most common error messageE               returned is SYSTEM-F-BADPARAM, although the problem canmF               sometimes result in the access violation message SYSTEM-D               F-ACCVIO. During most of the occurrences, the symbiontH               process crashes, leaving a dump file. If you do not deleteI               the queue entry for the control file that caused the crash, H               the entry will be the first entry processed when the queueI               is started after the crash, which causes the queue to crash H               again. If the job is put on hold and the TCP/IP managementE               command SHOW MAIL/FULL is issued, the SHOW MAIL commandR/               either signals an error or hangs.   I               This problem is due to a periodic corruption that occurs inRG               SMTP control files and happens more frequently with high-eH               use systems (1000 or more control files processed per day)5               than with systems processing less mail.t  D               To work around the problem, run the SMTP queue watcherB               command file TCPIP$EXAMPLES:TCPIP$RESTART_SMTPQ.COM.C               The header comments of this file describe its use andm               operation.  =               The following describes additional problems and                workarounds:  F               o  SMTP does not recognize mail to the cluster alias (IPD                  address or DNS name) as local. V4.x versions of the                  product do.                    Workaround:  G                  Add the name of the cluster alias to the local aliasese                  file.  E               o  The ANALYZE MAIL command does not find control files F                  stored in TCPIP$SMTP_COMMON when TCPIP$SMTP_COMMON is;                  not pointing to SYS$SPECIFIC:[TCPIP$SMTP].   &         3-14 Problems and Restrictions e  r      I                                                 Problems and RestrictionsrI                                                        3.21 SMTP Problemsh                      Workaround:  D                  Manually submit the control file to the SMTP queue.  ;         3.22 Status Returned by RSH and REXEC Command Filese  F               The RSH and REXEC command files return the status of theB               RSH or REXEC execution, not the status of the remoteD               command execution. The INETACP uses this return statusH               to determine if it should append an INETACP error message.  G               The remote command executed returns its own error messagen6               by means of SYS$OUTPUT and or SYS$ERROR.           3.23 $QIO Programming   C               The function IO$_WRITEVBLK will return the error SS$_F8               EXQUOTA under the following circumstances:  E               o  The process is set /NORESOURCE_WAIT (see SET PROCESSp!                  /RESOURCE_WAIT).d  H               o  The socket does not have enough space available (withinE                  its send quota) to be able to buffer all of the datag.                  being written at that moment.  I               If both of these conditions occur, the SS$_EXQUOTA error is G               returned. In addition, the data to be written will not belA               queued for transmission; it is rejected as a whole.l  D               This error affects the various socket routines used toH               transmit data: send(), sendto(), and sendmsg().  The C RTLG               returns an error indication on the call, and sets "errno"CC               to EVMSERR (65535); the OpenVMS specific "vaxc$errno"r9               contains the underlying error, SS$_EXQUOTA.d           3.24 SNMP Problems  I               This section details restrictions to the SNMP component fort               this release.o          I                                            Problems and Restrictions 3-15e a  o      !         Problems and Restrictions          3.24 SNMP Problems    !         3.24.1 Incomplete Restartt  E               When the SNMP master and subagents fail or are stopped,oD               TCP/IP Services is often able to restart all processesG               automatically. However, under certain conditions subagentoF               processes may not restart; that is, the DCL command SHOWI               SYSTEM display does not include TCPIP$OS_MIBS and TCPIP$HR_nH               MIB. If this situation occurs, restart SNMP by issuing the!               following commands:L  0               $ @SYS$STARTUP:TCPIP$SNMP_SHUTDOWN/               $ @SYS$STARTUP:TCPIP$SNMP_STARTUP            3.24.2 SNMP IVP Error   A               On slow systems, the SNMP Installation VerificationiD               Procedure can fail because a subagent does not respondC               to the test query. The error messages look like this:                 . . .5               Shutting down the SNMP service... done.e  B               Creating temporary read/write community SNMPIVP_153.  &               Enabling SET operations.  0               Starting the SNMP service... done.  C               SNMPIVP: unexpected text in response to SNMP request:o8               "- no such name - returned for variable 1"P               See file SYS$SYSDEVICE:[TCPIP$SNMP]TCPIP$SNMP_REQUEST.DAT for more               details.<               sysContact could not be retrieved.  Status = 0:               The SNMP IVP has NOT completed successfully.)               SNMP IVP request completed.n*               Press Return to continue ...  G               These types of messages in the IVP can be safely ignored.i  2         3.24.3 Using Existing MIB Subagent Modules  H               If an existing subagent does not execute properly, you mayE               need to relink it against the current version of TCP/IPaG               Services to produce a working image. Some subagents (suchsE               as those for OpenVMS support of Compaq Insight Manager)eE               also require a minimum version of OpenVMS and a minimumo)               version of TCP/IP Services.s  &         3-16 Problems and Restrictions S  h      I                                                 Problems and RestrictionstI                                                        3.24 SNMP ProblemsX    D               The following general restrictions and cautions apply:  F               o  In general, only executable images linked against theD                  following versions of the eSNMP shareable image are3                  upward compatible with TCPIP V5.1:T  E                  -  UCX$ESNMP_SHR.EXE from TCP/IP Services V4.2 ECO 4r  H                  -  TCPIP$ESNMP_SHR.EXE from TCP/IP Services V5.0A ECO 1  D                  Images built under versions other than these can beC                  relinked with one of the shareable images, or withr=                  TCPIP$ESNMP_SHR.EXE in TCP/IP Services V5.1.c  E               o  The underlying eSNMP API changed from DPI in V5.0 to D                  AgentX in V5.1. Therefore, executable images linkedA                  against older object library versions of the APIuC                  (*$ESNMP.OLB) must be relinked, either against the G                  new object library or against the new shareable image.tC                  Linking against the shareable image insures futurenH                  upward compatibility and results in smaller image size.  F                 ________________________ Note ________________________  >                 Although images may run without a relink, suchF                 backward compatibility is not supported and may result8                 in inaccurate data or run-time problems.  F                 ______________________________________________________  I               o  Programs that rely on TCP/IP Services Version 4.2 kernel H                  data structures or access functions may run but may notF                  return valid data. Such programs should be rewritten.  E               o  Executable images linked against UCX$ACCESS_SHR.EXE,hD                  UCX$IPC_SHR.EXE, UCX$RPCXDR_SHR.EXE, or other olderI                  shareable images, may not run even when relinked. It maynI                  be necessary to recompile, or rewrite and recompile suchi                  programs.  F               o  If you have executable images linked against versionsI                  other than those listed above and cannot relink, contactr/                  Compaq support for assistance.n  F               o  If you have problems running executable images linkedF                  against TCP/IP Services V4.2 ECO 4 or TCP/IP ServicesF                  V5.0A ECO 1, verify that the version of the shareableB                  image is the latest by entering the following DCL                  command:e  I                                            Problems and Restrictions 3-17            !         Problems and Restrictionss         3.24 SNMP Problems    F                  $ DIRECTORY/DATE/PROTECTION SYS$SHARE:*$ESNMP_SHR.EXE  G                  The creation dates of the files with the prefix TCPIP$ G                  and UCX$ should be within a few seconds of each other,aE                  and only one version of each file should exist. MakecC                  sure both images include the file protection W:RE.U  E                  Also, you can use the following command to check the                   version:   )                  $ TCPIP SHOW VERSION/ALL   H                  The second column in the line for image TCPIP$ESNMP_SHRE                  under the category "Network Management" displays the 6                  version. For example, for field test:  L         TCPIP$ESNMP_SHR;1      T5.1-9Q      22-NOV-2000  SYS$COMMON:[SYSLIB]  E               o  TCP/IP Services V5.0A ECO 1 and TCP/IP Services V5.1 I                  both provide an updated version of the UCX$ESNMP_SHR.EXE H                  shareable image to provide compatibility with subagentsG                  linked under TCP/IP Services V4.2 ECO 4. Do not delete                   this file.   8         3.24.4 Restrictions to RFC-Defined Functionality  D               o  SNMP requests are not implemented for the following&                  MIB-II group objects:  0                  ipRouteMetric1 - ipRouteMetric5                  tcpMaxConn   I               o  SNMP requests are not implemented for the following Hoste'                  Resources MIB objects:   !                  hrPartitionTabled                  hrPrinterTablei                  hrSWInstalled#                  hrSWInstalledTablel  H               o  SNMP set requests are not implemented for the following&                  MIB-II group objects:      &         3-18 Problems and Restrictions r  e      I                                                 Problems and RestrictionsnI                                                        3.24 SNMP Problemst                      ipDefaultTTLs                  ipRouteAgey                  ipRouteDest                  ipRouteIfIndexo                  ipRouteMask                  ipRouteNextHops                  ipRouteType  H               o  SNMP set requests are not implemented for the following,                  Host Resources MIB objects:  '                  hrFSLastFullBackupDateT*                  hrFSLastPartialBackupDate                  hrStorageSize                  hrSWRunStatus                  hrSystemDate[*                  hrSystemInitialLoadDevice.                  hrSystemInitialLoadParameters  H               o  In the SNMP group (1.3.6.1.2.1.11), data elements noted=                  as obsolete in RFC 1907 are not implemented.s  4         3.24.5 SNMP Restrictions and Characteristics  H               The restrictions and characteristics of SNMP are describedE               below. For more information, refer to the Compaq TCP/IPFH               Services for OpenVMS SNMP Programming and Reference guide.  D               o  The SNMP server responds correctly to SNMP requestsD                  directed to a cluster alias. Note, however, that anF                  unexpected host might be reached when querying from aI                  TCP/IP Services Version 4.x system that is a member of aaC                  cluster group but is not the current impersonator.$  F               o  The SNMP master agent and subagents will not start upF                  if the value of logical name TCPIP$INET_HOST does notE                  yield an IP address of a functional interface on themE                  host when used in a DNS query. This problem does not F                  occur if the server host is configured correctly withF                  a permanent network connection (for example, EthernetE                  or FDDI, or both). The problem can occur when a host E                  is connected through PPP and the IP address used for H                  the PPP connection does not match the IP address of the.                  TCPIP$INET_HOST logical name.  I                                            Problems and Restrictions 3-19     W      !         Problems and Restrictionso         3.24 SNMP Problems    G               o  Under certain conditions observed primarily on OpenVMS H                  VAX systems, the master agent or subagent exits with anH                  error from an internal select() socket call. Under mostF                  circumstances, looping does not occur. To control theF                  number of iterations should looping occur, define the<                  TCPIP$SNMP_SELECT_ERROR_LIMIT logical name.  >               o  The MIB browser provided with TCP/IP ServicesE                  (TCPIP$SNMP_REQUEST.EXE) supports getnext processing H                  of OIDs that include the 32-bit OpenVMS process ID as aI                  component. However, other MIB browsers might not providei                  this support.  I                  For example, the following OIDs and values are supported                   on OpenVMS:  ?                  1.3.6.1.2.1.25.4.2.1.1.1321206828 = 1321206828_?                  1.3.6.1.2.1.25.4.2.1.1.1321206829 = 1321206829 ?                  1.3.6.1.2.1.25.4.2.1.1.1321206830 = 1321206830   :                  These examples are from hrSWRunTable; the<                  hrSWRunPerfTable might be affected as well.  G               o  sysObjectID is returned in the following format. (This$<                  is the same behavior as Compaq Tru64 UNIX.)  ?                  1.3.6.1.2.1.1.2.0 = 1.3.6.1.4.1.36.2.15.x3.7.1n  A                  where 1.3.6.1.4.1.36.2.15.x3.7.1 corresponds to:n  O         iso.org.dod.internet.private.enterprises.dec.ema.sysobjectids.openvms.-n)         major-version-id.minor-version-id   <               o  The sysORTable is implemented (see RFC 1907<                  for details). Elements are under OID prefix#                  1.3.6.1.2.1.1.9.1.I  G                  When both the TCPIP$OS_MIBS and TCPIP$HR_MIB subagents C                  are running, a get request on the sysORTable is as)E                  follows. Except where noted, the OIDs conform to RFCe                  1907:  B                  1.3.6.1.2.1.1.9.1.2.1 = 1.3.6.1.4.1.36.15.3.3.1.1B                  1.3.6.1.2.1.1.9.1.2.2 = 1.3.6.1.4.1.36.15.3.3.1.2N                  1.3.6.1.2.1.1.9.1.3.1 = Base o/s agent (OS_MIBS) capabilitiesM                  1.3.6.1.2.1.1.9.1.3.2 = Base o/s agent (HR_MIB) capabilitiesf7                  1.3.6.1.2.1.1.9.1.4.1 = 31 = 0 d 0:0:0S7                  1.3.6.1.2.1.1.9.1.4.2 = 36 = 0 d 0:0:0S  &         3-20 Problems and Restrictions           I                                                 Problems and RestrictionscI                                                        3.24 SNMP Problems     B                  This example is from the MIB browser (TCPIP$SNMP_                  REQUEST.EXE).  E               o  The hrDeviceTable now includes template devices (foreF                  example, DNFS0 for NFS and DAD0 for virtual devices).  F               o  For network devices, only the template devices (those3                  with unit number 0) are displayed.r  @               o  The hrDeviceTable includes all devices known toA                  the OpenVMS host except those with the following !                  characteristics.T                    -  Off-line                    -  Remote  =                  -  UCB marked delete-on-zero-reference-counte  "                  -  Mailbox device  :                  -  Device with remote terminal (DEV$M_RTT#                     characteristic)   2                  -  Template terminal-class device  0                  -  LAT device (begins with _LT)  =                  -  Virtual terminal device (begins with _VT)n  ;                  -  Pseudoterminal device (begins with _FT)e  F               o  Data items in the hrDevTable group have the following                  restrictions:  5                  -  hrDeviceID: Always null OID (0.0)   ,                  -  hrDeviceErrors coded as:  I                     _____________________________________________________oI                     Code________Condition________________________________   H                     warning     If error logging is in progress (OpenVMS8                     (3)         UCB value UCB$M_ERLOGIP)  I                     running     If status indicates software is valid andqI                     (2)         no error logging in progress (OpenVMS UCB.2                                 value UCB$M_VALID)  8                     unknown     Any other OpenVMS statusI                     (1)__________________________________________________r  I                                            Problems and Restrictions 3-21(           !         Problems and Restrictionsl         3.24 SNMP Problems    D               o  On systems running versions of the operating systemH                  prior to OpenVMS 7.1-2, counters for the MIB-II ifTableG                  do not wrap back to 9 after reaching the maximum valueoG                  (232- 1), as defined in RFC 1155. Instead, they behaveM  D                  like the gauge type and remain at the maximum valueD                  until cleared by an external event such as a system>                  reboot. The counters affected are as follows:                    ifInDiscards                   ifInErrorso                  ifInNUcastPktsa                  ifInOctetsn                  ifInUcastPkts"                  ifInUnknownProtos                  ifOutErrors                   ifOutNUcastPkts                  ifOutOctets                  ifOutUcastPkts   C                  Note that for SNMPv2, these counters are data type F                  Counter32. The following ifTable members are always -G                  1 for OpenVMS: ifOutDiscards (Counter32) and ifOutQLen                   (Gauge32).   G               o  Under certain conditions, a subagent makes a duplicate C                  entry in sysORTable when it restarts. For example:c  B                  1.3.6.1.2.1.1.9.1.2.1 = 1.3.6.1.4.1.36.15.3.3.1.1B                  1.3.6.1.2.1.1.9.1.2.2 = 1.3.6.1.4.1.36.15.3.3.1.2N                  1.3.6.1.2.1.1.9.1.2.1 = Base o/s agent (OS_MIBS) capabilitiesN                  1.3.6.1.2.1.1.9.1.2.2 = Base o/s agent (OS_MIBS) capabilities:                  1.3.6.1.2.1.1.9.1.4.1 = 3256 = 0 d 0:0:32:                  1.3.6.1.2.1.1.9.1.4.2 = 3256 = 0 d 0:0:32  E                  In this example, the TCPIP$OS_MIBS subagent made two A                  entries with different ID numbers (OIDs with thebD                  prefix 1.3.6.1.2.1.1.9.1.2) that may show differentD                  sysORUpTime (1.3.6.1.2.1.1.9.1.4). The snmp_requestD                  program translates the value in centiseconds to dayF                  (d) plus hours:minutes:seconds notation, dropping anyF                  fractions of seconds. The HR_MIB subagent has not yetF                  successfully started and registered its capabilities.H                  If it starts, its entries in this example would use the-                  next available index number.s  &         3-22 Problems and Restrictions           I                                                 Problems and RestrictionsdI                                                        3.24 SNMP Problemse    B               o  hrFSMountPoint (1.3.6.1.2.1.25.3.8.1.2) is DNFSn.C                  The device may change between restarts, or after ap*                  dismount/mount procedure.  G               o  In the hrFSTable group, if no file systems are mountedtH                  through NFS or no information is accessible, a "no suchI                  instance" status is returned for a get request. BrowsersoB                  respond differently to this message. For example,C                  TCPIP$SNMP_REQUEST.EXE responds with no output and 4                  returns directly to the DCL prompt.  A                  After an NFS mount, the following information isnF                  returned in response to a get request. The data itemsA                  implemented for OpenVMS (refer to RFC 1514) are:o                    -  hrFSIndex.  :                  -  hrFSMountPoint: local DNFS device name  I                  -  hrFSRemoteMountPoint: In UNIX format, the remote file                      system name   H                  -  hrFSType: OID 1.3.6.1.2.1.25.3.9.1, if remote systemF                     is running TCP/IP Services, and the file system isH                     not a UNIX style container file system. hrFSNFS, OIDF                     1.3.6.1.2.1.25.3.9.14, if OpenVMS TCP/IP container,                     file system or UNIX host  7                  -  hrFSAccess (as defined in RFC 1514)s  >                  -  hrFSBootable: always HRM_FALSE (integer 2)  .                  -  hrFSStorageIndex: always 0  A                  -  hrFSLastFullBackupDate: unknown time. Encoded4D                     according to RFC 1514 as hexadecimal value 00 008                     01 01 00 00 00 00 (January 1, 0000).  @                  -  hrFSLastPartialBackupDate: unknown time. NotG                     available for OpenVMS systems. Instead, hexadecimal C                     value 00-00-01-01-00-00-00-00 (January 1, 0000)                      applies.  F               o  hrProcessorFrwID (OID prefix 1.3.6.1.2.1.25.3.3.1.1):  E                  -  Is not implemented on OpenVMS VAX. Always returns ,                     standard null OID (0.0).  2                     1.3.6.1.2.1.25.3.3.1.1.1 = 0.0  I                                            Problems and Restrictions 3-23a e  i      !         Problems and Restrictions          3.24 SNMP Problems    D                  -  For OpenVMS Alpha, an example is as follows. TheC                     example corresponds to firmware version 5.56-7.C  N                     1.3.6.1.2.1.25.3.3.1.1.1 = 1.3.6.1.2.1.25.3.3.1.1.1.5.56.7  I               o  Data items in the hrDiskStorage table have the following1                  restrictions:  <                  -  hrDiskStorageMedia: Always "unknown" (2)  ?                  -  hrDiskStorageRemoveble: Always "false" (2).P@                     Note the incorrect spelling of Removeable in;                     hrDiskStorageRemoveble (from RFC 1514).   :               o  hrStorageType always contain the value of;                  hrStorageFixedDisk (1.3.6.1.2.1.25.2.1.4).P  I               o  You can ignore the following warnings that appear in the                   log files:r  (                  -  On subagent startup:  F         {executable-image-name} WARNING {source-file-name} line {nnn}:<         Default esnmp timeout hrSWRunStatusset to 3 seconds.  @                  -  If a null OID value (0.0) for an instance isG                     retrieved in response to a Get, GetNext, or GetBulkh                     request:  F         {executable-image-name} WARNING {source-file-name} line {nnn}:3         Null Varbind or object, or, bad object type_  )         3.24.6 Upgrading Requires Restart_  G               After upgrading to TCP/IP Services V5.1, you must disableeH               and then enable SNMP using TCPIP$CONFIG. When prompted forI               "this node" or "all nodes", select the option that reflects )               the previous configuration.   >         3.24.7 Communication Controller Data Not Fully Updated  A               When you upgrade TCP/IP Services and then modify anmF               existing communication controller, programs that use theI               communication controller may not have access to the updated                information.  I               To ensure programs like the MIB browser (snmp_request) haveiH               access to the new data about the communication controller:  E               1. Delete the communication controller using the TCP/IPeD                  management command DELETE COMMUNICATION_CONTROLLER.  &         3-24 Problems and Restrictions 1  e      I                                                 Problems and RestrictionsnI                                                        3.24 SNMP Problems     B               2. Reset the communication controller by running the8                  TCPIP$CONFIG.COM procedure and exiting.  A               3. Restart the program (such as SNMP). For example:P  1                  $ @SYS$STARTUP:SNMP_SHUTDOWN.COMe0                  $ @SYS$STARTUP:SNMP_STARTUP.COM  F               4. Use the TCP/IP management command LIST COMMUNICATION_7                  CONTROLLER to display the information.   %         3.24.8 SNMP MIB Browser Usage   D               If you use either the -l (loop mode) or -t (tree mode)H               flag, you cannot also specify the -m (maximum repititions)F               flag or the -n (nonrepeaters) flag. The latter flags are8               incompatible with loop mode and tree mode.  -         3.24.9 Duplicate Subagent Identifiers   F               With this version of TCP/IP Services, it is possible forB               two subagents to have the same identifier parameter.D               However, be aware that this makes it more difficult toG               determine the cause of problems reported in the log file.   (         3.24.10 Invalid Response to Trap  G               The SNMP master agent sends an invalid response packet toEF               a subagent that sends a trap with a long protocol packetB               payload. For example, a long protocol packet payloadF               might include seven octet string varbinds, each with 255               characters.   I               The invalid response packet causes the subagent to restart. D               However, the master agent sends the trap to registeredE               trap listeners. The chess program example exhibits thisl               problem.  7         3.25 eSNMP Programming and Subagent Development   B               The following notes pertain to eSNMP programming and#               subagent development.   D               o  In the documentation, the terms extension subagent,H                  custom subagent, and user-written subagent refer to anyF                  subagent other than the standard subagents for MIB-IIG                  and the Host Resources MIB, which are provided as part 0                  of the TCP/IP Services product.  I                                            Problems and Restrictions 3-25  R  e      !         Problems and Restrictions 7         3.25 eSNMP Programming and Subagent Developmentr    A               o  For overall architecture information and details D                  about the eSNMP API, refer to the Compaq Tru64 UNIX4                  documentation at the following URL.  )                  www.tru64unix.compaq.comt  I                  The eSNMP software for OpenVMS is derived from the Tru64i                  UNIX product.  E               o  In the [.SNMP] subdirectory of TCPIP$EXAMPLES, files H                  with the .C, .H, .COM, .MY, and .AWK extensions contain7                  additional comments and documentation.t  H               o  The TCPIP$SNMP_REQUEST.EXE, TCPIP$SNMP_TRAPSND.EXE, andG                  TCPIP$SNMP_TRAPSND.EXE programs are useful for testingr7                  during extension subagent development.   I               o  For information about prototypes and definitions for the F                  routines in the eSNMP API, see the TCPIP$SNMP:ESNMP.H                  file.  F         3.26 DIGITAL TCP/IP Services for OpenVMS User's Guide Problems              and Restrictions   H               The DIGITAL TCP/IP Services for OpenVMS User's Guide guideF               has not been updated for the release of TCP/IP Services.H               The following errors and changes affect the DIGITAL TCP/IP0               Services for OpenVMS User's Guide:  G               o  The manual does not reflect the use of quotation marksmF                  to preserve the casing of user names, as described in7                  Section 1.2.11 in these release notes.o  I               o  The example showing the use of the RSH /ESCAPE_CHARACTER F                  qualifier needs to be improved. The following shows a                   better example:  :         $ RSH TRUNIX /USER_NAME=EVT /ESCAPE_CHARACATER="@"         Password:PI         Last successful login for evt: Wed Nov 18 15:50:22 1998 from OVMSlJ         Last unsuccessful login for evt: Tue Oct 13 14:16:51 1998 on ttyp3  D         Digital UNIX V3.2C  (Rev. 148); Tue Apr  2 18:32:54 EST 1996:         Digital UNIX V3.2D-1 Worksystem Software (Rev. 41)  5                         Digital Equipment Corporation )                         Internal Use Onlyc  &         3-26 Problems and Restrictions s  c      I                                                 Problems and Restrictions I  TCP/IP       Services for OpenVMS User's Guide Problems and RestrictionsL    A         trunix.ucx.lkg.dec.com>@.   (character string not echoed)P1         %RSH-S-LCLCLOSED, Local connection closedE  A                  In this example, the escape character closed thedH                  connection from the local side as opposed to the remote/                  system closing the connection.   F               o  The manual indicates that the default setting for theC                  RSH command is /NOTRUNCATION_USER_NAME. This is an E                  invalid qualifier, which will be removed the manual.1  E               o  The messages displayed in response to the FTP Client2@                  command MPUT have been improved as described in                   Section 4.1.12.                                                              I                                            Problems and Restrictions 3-27$                         I                                                                         41I         _________________________________________________________________.  I                                                               Correctionse    ?               This chapter describes software and documentation >               corrections. It contains the following sections:  @               o  Section 4.1 lists changes and software problems+                  corrected in this release.   D               o  Section 4.2 lists problem reports addressed in this                  release.             4.1 Software Corrections  G               This section describes the changes and problems corrected /               since the product's last release.1  G               In addition, please see Section 1.2 for information about2;               other software changes made for this release.9  3         4.1.1 UCP Problems Fixed Since Last Release   F               The TCP/IP management command SET ROUTE allows the /MASKF               qualifier to be used when specifying a CIDR mask withoutH               requiring the /NETWORK qualifier. The resulting route that,               is created may not be useable.  A               If you specify the /MASK qualifier on the SET ROUTE D               command, you must also include the /NETWORK qualifier.  =         4.1.2 TELNET Server Problems Fixed Since Last Release   H               When the TELNET server is configured for virtual terminalsH               (VTAs), and the TELNET command UNBIND specifies an inboundC               TELNET connection whose VT device has been associatedtD               with the specified TN device, the system fails with an               INVEXCEPTN error.e    I                                                           Corrections 4-1  e  t               Corrections           4.1 Software Corrections    I               The driver has been enhanced to verify the arguments to the F               TELNET commands BIND and UNBIND. The situation describedB               in this section fails correctly with the status SS$_               DEVREQERR.  9         4.1.3 TELNETSYM Problems Fixed Since Last Releasel  I               The limit of 16 queues (streams) for each TELNETSYM process E               has been updated to 32 to reflect the new queue manager-D               limit. TELNETSYM now supports up to 32 queues for each               symbiont process.t  3         4.1.4 IPC Problems Fixed Since Last Release   6               The gethostaddr routine was not working.  4         4.1.5 DHCP Problems Fixed Since Last Release  ?               o  Sometimes the DHCP client process hangs and is F                  unresponsive to any commands except DHCPSIGTERM. ThisF                  happens only when the TCPIP$DHCP_DEBUG logical is not                  defined.   F               o  The lt field from a DHCPCAP entry keyed on the subnet3                  and vendor class was being missed.   3         4.1.6 POP Problems Fixed Since Last Release   H               o  The POP server will no longer incorrectly set the Date:I                  header for non-SMTP (such as DECnet) mail messages based_H                  on the current system time and date. The date used willF                  be based on the mail message's delivery time into the                   user's mailbox.  I               o  The POP server now flushes the log file on each write to I                  it. This ensures that the log is always current with theT1                  state of the POP server process.r  4         4.1.7 SMTP Problems Fixed Since Last Release  H               o  Mail that contains 8-bit characters may be converted byG                  some mailers to a MIME quoted-printable format that isbC                  displayed with encoded characters by OpenVMS mail.u  H                  To prevent the conversion by mailers, set the following                  logical:   )                  TCPIP$SMTP_8BITMIME_HACKI           4-2 Correctionsi U  t      I                                                               Corrections I                                                  4.1 Software Correctionst    D                  This Boolean logical tells the local mail server toG                  accept the ESMTP 8BITMIME request from the remote SMTPlG                  client, preventing the mail client from converting theuF                  8-bit characters and allowing OpenVMS mail to display&                  the message properly.  F               o  A mail message with an empty Reply-To header causes aI                  strange header to appear in the OpenVMS MAIL From: line.   B                  SMTP ignores empty sender headers (Repy-To, From,5                  Sender) when it formats the message.   =         4.1.8 BIND Resolver Problems Fixed Since Last Releaseg  F               SMTP failed with an access violation while attempting toH               do an MX lookup when both of the following conditions were8               true in the TCPIP$GET_MX resolver routine:  H               1. There were no NS records returned from the query to the                  BIND server.   F               2. UCP passed an allowed but improperly handled value of2                  zero for "server" to the routine.  :         4.1.9 Management Problems Fixed Since Last Release  @               The following corrections have been made to TCP/IP"               management commands:  H               o  The SET CONFIGURATION INTERFACE command fails to createC                  a default broadcast mask when you create a clustere/                  interface record. For example:            $ TCPIP 0         TCPIP> SET CONFIGURATION INTERFACE WE0 -<         _TCPIP> /CLUSTER=16.20.208.68 /C_NETWORK=255.255.0.0  5         TCPIP> SHOW CONFIGURATION INTERFACE WE0 /FULL            Interface: WE0T           IP_Addr: 16.20.208.68      NETWRK: 255.255.0.0       BRDCST: 16.20.255.255F            C_Addr: 16.20.208.68    C_NETWRK: 255.255.0.0     C_BRDCST:               Flags:(             Receive buffer:            0  I                                                           Corrections 4-3     t               Correctionsn          4.1 Software Corrections    B               o  The SET INTERFACE command permits the creation ofE                  multiple pseudointerfaces having identical interface G                  names. In addition, the SET INTERFACE command does not D                  correctly create pseudointerfaces with unit numbersI                  greater than 9 (valid unit numbers range from 0 to 255).s  I                  For example, this SET INTERFACE commands fails to createV                  WFA10:e  =                  $ TCPIP SET INTERFACE WFA10 /HOST=10.10.0.10o  D                  Output from the SHOW INTERFACE command demonstratesG                  this. (The WFA1 interface shown below should have been #                  created as WFA10.).           $ TCPIP SHOW INTERFACEJ                                                                    PacketsQ         Interface   IP_Addr         Network mask          Receive    Send     MTU   Q          LO0        127.0.0.1       255.0.0.0               18355   18355    4096eQ          WF0        16.20.208.100   255.255.0.0           5104314 5068074    4470 Q          WFA1       10.10.0.10      255.255.0.0           5104314 5068074    4470-  C                  This SET INTERFACE command results in creating twoa<                  pseudointerfaces that have identical names:  4         $ TCPIP SET INTERFACE WFA11 /HOST=10.10.0.11  D                  Output from the SHOW INTERFACE command demonstratesI                  this. (The second WFA1 interface shown below should have )                  been created as WFA11).)            $ TCPIP SHOW INTERFACEJ                                                                    PacketsQ         Interface   IP_Addr         Network mask          Receive    Send     MTUp  Q          LO0        127.0.0.1       255.0.0.0               18367   18367    4096.Q          WF0        16.20.208.100   255.255.0.0           5144574 5077124    4470 Q          WFA1       10.10.0.10      255.255.0.0           5144574 5077124    4470dQ          WFA1       10.10.0.11      255.255.0.0           5144574 5077124    4470h                    Note that:e  C                  o  Pseudointerfaces cannot be modified; that is, a D                     pseudointerface must be deleted and then created=                     to change its associated network address.t  H                  o  Use of the /HOST qualifier is required when creating%                     pseudointerfaces."           4-4 Corrections  i  t      I                                                               CorrectionslI                                                  4.1 Software Corrections1    H               o  The TCP/IP management command START ROUTING/SUPPLY doesF                  not supply the route. The workaround was to use GATED"                  with RIP enabled.  I               o  Specifying a remote host by IP address on an RSH commandnE                  could trigger an access violation error when no hostiF                  name could be found in the local or BIND database for                   the IP address.  9         4.1.10 PPP/SLIP Problems Fixed Since Last Release   @               The following command sequence crashes the system:  J               $ TCPIP SET INTERFACE PP0 /SERIAL=TTA1 /NETWORK_MASK=x.x.x.x  3               $ TCPIP SET INTERFACE PP0/SERIAL=TTB0 >               %TCPIP-E-INVINTER, error defining interface: PP0:               -TCPIP-I-ACPQIO, failure on internet ACP QIO6               -SYSTEM-W-NOMSG, Message number 0000FCE0  ;         4.1.11 FTP Server Problems Fixed Since Last Release   G               o  In previous versions of TCP/IP Services, when a clientuF                  address is not known to the name server, an excessiveF                  delay after the password prompt can occur. This delayE                  is caused by possible multiple name server timeouts,eB                  multiple retires, and multiple name servers. This,                  problem has been corrected.  F                  Define the following logical to correct this problem:  9                  -  TCPIP$FTP_SERVER_NAME_SERVICE_TIMEOUTr  A                     Specify the number of seconds for the timeoutt@                     interval. For more information, refer to theG                     description of the SET NAME_SERVICE/TIMEOUT command H                     in the Compaq TCP/IP Services for OpenVMS Management-                     Command Reference manual.   7                  -  TCPIP$FTP_SERVER_NAME_SERVICE_RETRYc  H                     Specify the number of times the BIND resolver shouldI                     attempt to contact a BIND server if the first attempt.                     fails.  D                  These logical names are used only if the FTP serverD                  will be using host names (that is, the logical nameH                  TCPIP$FTP_SERVER_LOG_CLIENT_BY_ADDRESS is not defined).  I                                                           Corrections 4-5e e  h               Correctionse          4.1 Software Corrections    F               o  TELNET, RLOGIN, RSH, and REXEC examine the log optionC                  address bit in the service database. If the bit iseE                  set, they display host names as numeric presentationnI                  addresses (for example, n.n.n.n or IPv6 address). If thebH                  bit is clear and the name is in the local host databaseH                  or the BIND resolver knows the host name, they use thatF                  name. The default is to the numeric form. This bit isB                  set by $TCPIP SET SERVICE FTP/LOG_OPTION=address.  H                  The FTP server has been modified to lookup and use thisC                  bit. In particular, SYS$REM_NODE and SYS$REM_NODE_.F                  FULLNAME in the FTP child process will always containE                  a numeric presentation address when this bit is set.   F                  In situations where numeric addresses are appropriateG                  in the FTP server and other log files, you may want todI                  set this logical. Setting it makes the FTP session login G                  operation slightly faster and less expensive because ao(                  name lookup is avoided.  H               o  Previously, the TCPIP FTP Client would ignore a logical@                  name of TCPIP$FTP_HELP defined for an alternate@                  component help library and access only the file-                  SYS$HELP:TCPIP$FTP_HELP.HLB.n  F                  This condition has been corrected. This allows accessC                  to multiple alternate, possibly language specific,r*                  component help libraries.  F               o  In previous versions of TCP/IP Services, when FTP wasE                  connected to a non-VMS_PLUS remote host or node, theeF                  following sequence would yield an uppercase file nameE                  for the first MPUT and a lowercase file name for ther.                  second (and later) and MPUTs:  4         $ FTP host-name/USER=user-name/PASS=password6         FTP> MPUT A.dat  ! Yields A.DAT at destination'         FTP> PUT A.dat   ! Yields a.dat K         FTP> MPUT A.dat  ! Yields a.dat rather than expected/previous A.DATM  I                  This problem occurs for several commands, in addition tos                  PUT.   E                  This behaviour has been corrected so that the secondSF                  MPUT command will now yield a file name with the same#                  case as the first.   D                  This problem occurs only with the above sequence ofF                  commands and when there is no TCPIP$FTPINIT.INI file.           4-6 Corrections  t  e      I                                                               CorrectionsTI                                                  4.1 Software Correctionsr    H                  Use the FTP CASE OFF and CASE ON commands to change theI                  typographical case used by MPUT to lowercase and back toe                  uppercase.n  G               o  Files with no "type" in a RENAME operation could causeOB                  memory to be accessed which should not have been.  E               o  Inaccurate use of RMS_POSTED in the appe_ascii() anduD                  recv_ascii() routines causes the FTP client to lose1                  synchronization with the server.i  ;         4.1.12 FTP Client Problems Fixed Since Last Releasei  I               The following corrections have been made to the FTP client.m  I               o  The FTP Client does not properly take input from commandaG                  files with Fortran RMS record attributes. This problem I                  is observed on systems running versions of OpenVMS prior9B                  to Version 7.1 and certain versions of DEC C RTL.  E               o  The text returned by the FTP command STATUS has been)6                  improved to make the following clear:  I                  -  The specified variable affects only the MPUT command.e  I                  -  The CASE ON command really means "as is," rather thanb)                     "force to uppercase."c  H                     The CASE OFF command means "force to lowercase," but6                     CASE ON does not mean the inverse.  E                  -  The MPUT command may not always be able to complys,                     with your case settings.  ?         4.1.13 Load Balancing Problems Fixed Since Last Releaseo  B               The following corrections have been made to the load,               balancing component (LBROKER).  A               o  The LBROKER log file contains the host name thatT1                  generated the file. For example:c  ,                  TCPIP$LBROKER_host-name.LOG  H               o  The following NOTICE-level LBROKER log file message has:                  been changed to be a DEBUG level message:  7                  NOTICE: updated DNS RRset cluster_name   F                  This will now only be displayed if the TCPIP$LBROKER_:                  LOG_LEVEL logical is set to 1 or greater.  I                                                           Corrections 4-7  _  _               Corrections_          4.1 Software Corrections    H               o  In the LBROKER configuration file you may specify "max-I                  members," which tells the load broker how many A records G                  to send to the BIND server. The problem occured if you G                  specified a count of 1. Instead of sending one record,t;                  it sent all of them from the members list.o  ?                  With TCP/IP Services V5.1, max-members behaves ?                  as expected when specified as 1 in the LBROKERs$                  configuration file.  4         4.1.14 NTP Problems Fixed Since Last Release  I               The following logical name allows you to specify debug mode                for NTP:  !               TCPIP$NTP_LOG_LEVEL   H               This logical should be defined with /SYSTEM and can assumeG               a value in the range 1-6 (with 6 being the most verbose).b  6         4.2 Reported Problems Fixed Since Last Release  G               Compaq uses the IPMT (Integrated Problem Management Tool)sE               to track problems reported by customers. When a problemqD               report is created, it is given a unique identificationI               number, starting with "CFS." When the problem is logged forn>               engineering attention, it receives a PTR number.  F               This section describes problems which have been reportedB               and fixed, providing the CFS and PTR identifiers for               each.s  I               Table_4-1_Management_Problems_Fixed_Since_Last_Release_____n  I               CFS_Number__PTR_Number_______Description___________________   F               CFS.70983   70-5-1158        The SHOW PROTOCOL UDP/PARAMH                                            command does not show receive2                                            quotas.  ;                                            The SET PROTOCOL B                                            UDP/QUOTA=RECEIVE=valueA                                            command does not work.e  I                                                  (continued on next page)N           4-8 Corrections  a  e      I                                                               CorrectionsMI                            4.2 Reported Problems Fixed Since Last Release     D               Table 4-1 (Cont.) Management Problems Fixed Since LastI               __________________Release__________________________________i  I               CFS_Number__PTR_Number_______Description___________________a  F               CFS.72192   70-5-1195        The following TCPIP commandG                                            doesn't work if the /ADDRESSnF                                            qualifier value specifies aG                                            network address with subnet:e  R                                            TCPIP> SET NETWORK net /ADDRESS=x.x.x.x  E                                            For example, the following G                                            SET NETWORK command (without >                                            subnet info) works:  F                           $ TCPIP SET NETWORK VMSNET /ADDRESS=18.0.0.0  E                                            However, the following SETeG                                            NETWORK command (with subnett7                                            info) fails:e  H                           $ TCPIP SET NETWORK VMSNET /ADDRESS=16.66.66.0#                           %TCPIP-E-tH                           NETWORKERROR, error processing network request#                           -TCPIP-E- G                           INVQUAL, invalid qualifier value for /ADDRESSa#                           -TCPIP-I-hI               ____________ADR_HOST,_internet_address_specifies_a_host____   I               Table_4-2_BIND_Server_Problems_Fixed_Since_Last_Release____   I               CFS_Number__PTR_Number_______Description___________________n  I               CFS.72317   70-5-1198        The restriction that you couldtD                                            only have one BIND serverF                                            enabled among nodes sharingH                                            a system disk in a cluster no9                                            longer exists.V  I                                                  (continued on next page)         I                                                           Corrections 4-9a    a               Correctionsr6         4.2 Reported Problems Fixed Since Last Release    E               Table 4-2 (Cont.) BIND Server Problems Fixed Since LastaI               __________________Release__________________________________   I               CFS_Number__PTR_Number_______Description___________________   B               CFS.75957   70-5-1382        The BIND server was notD                                            rolling over the databaseH                                            file when the maximum versionG                                            number of 32767 was reached. D                                            This specifically appliedE                                            to a slave server that was G                                            increasing the database fileaI                                            version number by performing aaH                                            zone transfer. Master serversE                                            already had a form of this B                                            rollover functionality.  C               CFS.73712   70-5-1274        BIND did not support theIB                                            dynamic updating of SRV<                                            resource records.  I               CFS.68483   70-5-1079        The BIND server reports syntax5H               CFS.66892   70-5-1022        errors when CIDR notation wasI                                            used in the configuration filecI               _____________________________(TCPIP$BIND.CONF).____________t  I               Table_4-3_NFS_Client_Problems_Fixed_Since_Last_Release_____   I               CFS_Number__PTR_Number_______Description___________________   C               CFS.68919   70-5-1094        Beginning with VMS V7.2, C                                            running BACKUP on an NFS G                                            client device results in the ;                                            following error:l  Z               _____________________________-SYSTEM-F-BADATTRIB,_bad_attribute control list  I               Table_4-4_TELNET_Server_Problems_Fixed_Since_Last_Release__r  I               CFS_Number__PTR_Number_______Description___________________   F               CFS.67834   70-5-1053        System crash in TN$NETWORK_I               _____________________________DISCONNECT()._________________              4-10 Corrections    e      I                                                               Corrections I                            4.2 Reported Problems Fixed Since Last Release.    I               Table_4-5_PPP/SLIP_Problems_Fixed_Since_Last_Release_______0  I               CFS_Number__PTR_Number_______Description___________________   E               CFS.69244   70-5-1108        An accepted socket doesn'tpE                                            inherit the probe and dropFG                                            settings (tcp_keepidle, tcp_FI                                            keepintvl, tcp_keepcnt) of the ;                                            listener socket.A  A               CFS 76412   70-5-1399        TCP/IP Services limits E                                            the number of SLIP and PPPA;                                            interfaces to 9.   I                                            For more information, refer to4I                                            the Compaq TCP/IP Services for7G                                            OpenVMS Management guide for1I               _____________________________TCP/IP_Services_Version_5.1.__   I               Table_4-6_NTP_Problems_Fixed_Since_Last_Release____________   I               CFS_Number__PTR_Number_______Description___________________   D               CFS.75496   70-5-1382        Problems occur when usingC                                            TCPIP$NTPTRACE against afE                                            TCP/IP Services NTP serveruF                                            that had been designated asI               _____________________________"free-running."_______________                                   I                                                          Corrections 4-11a