Compaq_TCP/IP_Services_for_OpenVMS__________________ Release Notes January 2001 This document describes new features and changes to the software; installation, upgrade, and compatibility information; new and existing software problems and restrictions; and software and documentation corrections. Revision/Update Information: These release notes supersede the TCP/IP Services for OpenVMS V5.0A Release Notes. Software Version: Compaq TCP/IP Services for OpenVMS Version 5.1 Operating Systems: OpenVMS Alpha Versions 7.1, 7.2-1 OpenVMS VAX Versions 7.1, 7.2 Compaq Computer Corporation Houston, Texas ________________________________________________________________ © 2001 Compaq Computer Corporation COMPAQ, VAX, VMS, and the Compaq logo Registered in U.S. Patent and Trademark Office. DECnet, OpenVMS, PATHWORKS, and Tru64 are trademarks of Compaq Information Technologies Group, L.P. in the United States and other countries. UNIX is a trademark of The Open Group in the United States and other countries. All other product names mentioned herein may be trademarks of their respective companies. Confidential computer software. Valid license from Compaq required for possession, use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. Compaq shall not be liable for technical or editorial errors or omissions contained herein. The information in this document is provided "as is" without warranty of any kind and is subject to change without notice. The warranties for Compaq products are set forth in the express limited warranty statements accompanying such products. Nothing herein should be construed as constituting an additional warranty. This document was prepared using DECdocument, Version 3.3- 1b. _________________________________________________________________ Contents Preface................................................... vii 1 New Features and Changes 1.1 Version 5.1 Features.......................... 1-1 1.1.1 New Kernel................................ 1-2 1.1.2 Support for Internet Protocol Version 6 (IPv6).................................... 1-4 1.1.2.1 Name Space Configuration Guidelines..... 1-5 1.1.2.2 Using the Local Hosts Database.......... 1-6 1.1.2.3 Configuring or Deleting Interfaces Under IPv6.................................... 1-6 1.1.3 GATED Enhancements........................ 1-7 1.1.4 Restartable Services...................... 1-7 1.1.4.1 Obsolete Files.......................... 1-8 1.1.4.2 New Files............................... 1-9 1.1.4.3 Changes to the TCPIP$CONFIG.COM Command Procedure............................... 1-11 1.1.5 BIND Enhancements......................... 1-11 1.1.5.1 BIND Server Cluster Failover............ 1-11 1.1.5.2 Managing BIND Dynamic Updates........... 1-11 1.1.6 Updates to SNMP........................... 1-12 1.1.6.1 Managing the SNMP MIB Browser........... 1-13 1.1.7 SMTP Features............................. 1-14 1.1.7.1 SMTP SFF (Send From File)............... 1-14 1.1.7.1.1 Format of the SFF File................. 1-15 1.1.7.1.2 SFF File Requirements.................. 1-16 1.1.7.1.3 SFF Security Measures.................. 1-17 1.1.7.1.4 Invoking SFF from an Application....... 1-17 1.1.7.1.5 Invoking SFF from DCL.................. 1-18 1.1.7.2 SMTP Outbound Alias..................... 1-18 1.1.7.2.1 Defining the Outbound Alias............ 1-18 iii 1.1.7.2.2 Appending the Personal Name String to the Outbound Alias..................... 1-19 1.1.7.2.3 Appending a Substitute Domain String... 1-20 1.1.7.2.4 Disabling Modifications to TCPIP$SMTP_FROM........................ 1-21 1.1.7.2.5 TCPIP$SMTP_FROM and the Return-Path: Header................................. 1-21 1.1.7.2.6 X-VMS-True-From: Header................ 1-21 1.1.7.2.7 Managing Outbound Alias Processing..... 1-21 1.1.8 Metric Server Enhancements................ 1-22 1.1.9 Load Broker Cluster Failover.............. 1-23 1.1.10 DHCP Dynamically Updates BIND............. 1-24 1.1.11 XDM Terminal Support...................... 1-25 1.1.12 TELNET Client Enhancements................ 1-26 1.1.13 NFS Server and Client Enhancements........ 1-26 1.1.13.1 NFS V3 Protocol......................... 1-27 1.1.13.2 Extending and Truncating Files.......... 1-28 1.1.13.3 NFS Client Reports True Allocated Size.................................... 1-28 1.1.13.4 MOUNT Retry Default Value............... 1-29 1.1.13.5 Network Locking......................... 1-29 1.1.13.6 Managing the MOUNT Service.............. 1-30 1.1.14 DHCP Client Configuration................. 1-30 1.1.15 TCP Performance Options................... 1-33 1.2 Version 5.1 Changes........................... 1-33 1.2.1 Unsupported Management Commands........... 1-33 1.2.2 Changes to Management Commands............ 1-34 1.2.3 Changes to NFS Server Configuration....... 1-35 1.2.3.1 Using NFSSTAT to Display Statistical Information............................. 1-37 1.2.3.2 Using SYSCONFIG to Modify NFS Server Attributes.............................. 1-38 1.2.3.3 Using SYSCONFIG to Display Parameter Settings................................ 1-41 1.2.4 TCP/IP Process Names...................... 1-41 1.2.5 FTP Changes............................... 1-42 1.2.5.1 FTP Passive Mode........................ 1-42 1.2.5.2 FTP Message Enhancement................. 1-42 1.2.6 POP Server Threads Configuration.......... 1-43 1.2.7 LPD Changes............................... 1-43 1.2.8 NTP Changes............................... 1-44 1.2.9 DHCP Changes.............................. 1-45 iv 1.2.10 BIND Changes.............................. 1-47 1.2.10.1 Editable Network Services Database...... 1-47 1.2.10.2 BIND Server Merges Dynamic Updates Automatically........................... 1-49 1.2.11 SMTP Changes.............................. 1-49 1.2.12 Message Improvements...................... 1-51 1.2.13 Adjusting Interrupt Stack Pages on VAX Systems................................... 1-52 1.2.14 TELNET Changes............................ 1-53 1.2.15 Programming Example Changes............... 1-53 1.2.16 SHOW DEVICE Command Changes............... 1-53 1.2.17 Server Inactivity Timer Is Not Enforced... 1-54 1.3 Version 5.1 Documentation..................... 1-54 2 Installation, Configuration, and Startup Notes 2.1 Configuring IPv6.............................. 2-1 2.1.1 Information for Users of the IPv6 EAK..... 2-1 2.1.2 Warning Message in TCPIP$CONFIG.COM....... 2-1 2.2 Removing Prior Versions of this Product....... 2-2 2.2.1 Saving Mail Messages When You Upgrade..... 2-2 2.2.2 Upgrading OpenVMS VAX Systems............. 2-2 2.3 System Page Table Entries Parameter (VAX Systems Only)................................. 2-3 2.4 Some UCX Files Remain After Installation...... 2-3 2.5 Starting the Product After a Minimum OpenVMS Boot.......................................... 2-5 2.6 Preserving LPD Startup and Shutdown Behavior...................................... 2-6 2.6.1 OpenVMS Alpha Users....................... 2-6 2.6.2 OpenVMS VAX Users......................... 2-7 2.6.3 Troubleshooting SMTP and LPD Shutdown Problems.................................. 2-7 2.6.4 Merging Edits (All Users)................. 2-8 2.7 SNMP Installation and Setup................... 2-8 2.7.1 Verifying the SNMP Installation........... 2-8 2.7.2 Preserving SNMP Startup and Shutdown Behavior.................................. 2-8 2.8 Setting Up the TCP/IP Services Message Database...................................... 2-9 2.9 PROXYERROR Messages at Startup................ 2-10 v 3 Problems and Restrictions 3.1 NFS Problems and Restrictions................. 3-1 3.1.1 NFS Lock Requests Fail.................... 3-1 3.1.2 NFS Client Problems and Restrictions...... 3-2 3.2 DHCP Client Problems and Restrictions......... 3-2 3.3 IPv6 Problems and Restrictions................ 3-3 3.3.1 IPv6 Proxy Lookup......................... 3-3 3.3.2 IPv6 Requires the BIND Resolver........... 3-3 3.4 RLOGIN Does Not Create Virtual Terminals...... 3-3 3.5 TELNET Devices Remain After Shutdown.......... 3-3 3.6 TELNETSYM Autostart Queues in OpenVMS Clusters...................................... 3-4 3.7 File Locking Requires Compaq C RTL ECO3 or Higher........................................ 3-4 3.8 PRODUCT REMOVE TCPIP Error Message............ 3-4 3.9 Startup DUPLNAM Messages...................... 3-5 3.10 Security Driver............................... 3-6 3.11 Command Restrictions.......................... 3-6 3.12 NTP Problems and Restrictions................. 3-8 3.13 Error Messages................................ 3-8 3.14 FTP Problems and Restrictions................. 3-8 3.14.1 GET/FDL Command........................... 3-8 3.14.2 Extended File Specifications in a Mixed Operating System Environment.............. 3-9 3.15 DHCP Problems and Restrictions................ 3-10 3.16 PPP/SLIP Problems and Restrictions............ 3-11 3.16.1 Running PPP on OpenVMS Version 7.1........ 3-11 3.16.2 PPPD CONNECT Causes the System to Fail.... 3-11 3.17 Configuring Your Host as a Dialup Provider.... 3-11 3.18 RCP Problems and Restrictions................. 3-11 3.19 REUSEADDR Behaviour change in V4.2 to V5.x Transition.................................... 3-13 3.20 POP Problems.................................. 3-13 3.21 SMTP Problems................................. 3-14 3.22 Status Returned by RSH and REXEC Command Files......................................... 3-15 3.23 $QIO Programming.............................. 3-15 3.24 SNMP Problems................................. 3-15 3.24.1 Incomplete Restart........................ 3-16 3.24.2 SNMP IVP Error............................ 3-16 3.24.3 Using Existing MIB Subagent Modules....... 3-16 3.24.4 Restrictions to RFC-Defined Functionality............................. 3-18 vi 3.24.5 SNMP Restrictions and Characteristics..... 3-19 3.24.6 Upgrading Requires Restart................ 3-24 3.24.7 Communication Controller Data Not Fully Updated................................... 3-24 3.24.8 SNMP MIB Browser Usage.................... 3-25 3.24.9 Duplicate Subagent Identifiers............ 3-25 3.24.10 Invalid Response to Trap.................. 3-25 3.25 eSNMP Programming and Subagent Development.... 3-25 3.26 DIGITAL TCP/IP Services for OpenVMS User's Guide Problems and Restrictions............... 3-26 4 Corrections 4.1 Software Corrections.......................... 4-1 4.1.1 UCP Problems Fixed Since Last Release..... 4-1 4.1.2 TELNET Server Problems Fixed Since Last Release................................... 4-1 4.1.3 TELNETSYM Problems Fixed Since Last Release................................... 4-2 4.1.4 IPC Problems Fixed Since Last Release..... 4-2 4.1.5 DHCP Problems Fixed Since Last Release.... 4-2 4.1.6 POP Problems Fixed Since Last Release..... 4-2 4.1.7 SMTP Problems Fixed Since Last Release.... 4-2 4.1.8 BIND Resolver Problems Fixed Since Last Release................................... 4-3 4.1.9 Management Problems Fixed Since Last Release................................... 4-3 4.1.10 PPP/SLIP Problems Fixed Since Last Release................................... 4-5 4.1.11 FTP Server Problems Fixed Since Last Release................................... 4-5 4.1.12 FTP Client Problems Fixed Since Last Release................................... 4-7 4.1.13 Load Balancing Problems Fixed Since Last Release................................... 4-7 4.1.14 NTP Problems Fixed Since Last Release..... 4-8 4.2 Reported Problems Fixed Since Last Release.... 4-8 vii Tables 1 TCP/IP Services Documentation............. viii 1-1 Displaying Statistical Information with NFSSTAT................................... 1-37 1-2 Modifying NFS Server Attributes with SYSCONFIG................................. 1-39 2-1 UCX Files Remaining After Installation.... 2-3 4-1 Management Problems Fixed Since Last Release................................... 4-8 4-2 BIND Server Problems Fixed Since Last Release................................... 4-9 4-3 NFS Client Problems Fixed Since Last Release................................... 4-10 4-4 TELNET Server Problems Fixed Since Last Release................................... 4-10 4-5 PPP/SLIP Problems Fixed Since Last Release................................... 4-11 4-6 NTP Problems Fixed Since Last Release..... 4-11 viii _________________________________________________________________ Preface The Compaq TCP/IP Services for OpenVMS product is the Compaq implementation of the TCP/IP protocol suite and internet services for OpenVMS Alpha and OpenVMS VAX systems. TCP/IP Services provides a comprehensive suite of functions and applications that support industry-standard protocols for heterogeneous network communications and resource sharing. For installation instructions, see the manual Compaq TCP/IP Services for OpenVMS Installation and Configuration. The release notes provide version-specific information that supersedes the information in the documentation set. The features, restrictions, and corrections in this version of the software are described in the release notes. Always read the release notes before installing the software. Intended Audience These release notes are intended for experienced OpenVMS and UNIX system managers and assumes a working knowledge of OpenVMS system management, TCP/IP networking, TCP/IP 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 Compaq TCP/IP Services for OpenVMS Installation and Configuration manual. o Managers of OpenVMS layered products o OpenVMS system managers vii o Network managers Related Documents Table 1 lists the documents available with this version of TCP/IP Services. Table_1_TCP/IP_Services_Documentation____________________________ Manual____________________Contents_______________________________ DIGITAL TCP/IP Services This manual provides conceptual for OpenVMS Concepts and information about networking and the Planning TCP/IP protocol including a description of the Compaq implementation of the Berkeley Internet Name Domain (BIND) service and the Network File System (NFS). It outlines general planning issues to consider before configuring your system to use the TCP/IP Services software. This manual also describes the manuals in the documentation set, provides a glossary of terms and acronyms for the TCP/IP Services software product, and documents how to contact the InterNIC Registration Service to register domains and access Request for Comments (RFCs). Compaq TCP/IP Services This text file describes new features for OpenVMS Release and changes to the software including Notes installation, upgrade, configuration, and compatibility information. These notes also describe new and existing software problems and restrictions, and software and documentation corrections. Print this text file at the beginning of the installation procedure and read it before you install TCP/IP Services. (continued on next page) viii Table_1_(Cont.)_TCP/IP_Services_Documentation____________________ Manual____________________Contents_______________________________ Compaq TCP/IP Services This manual explains how to install and for OpenVMS Installation configure the TCP/IP Services product. and Configuration DIGITAL TCP/IP Services This manual describes how to use for OpenVMS User's Guide the applications available with TCP/IP Services such as remote file operations, email, TELNET, TN3270, and network printing. This manual explains how to use these services to communicate with systems on private internets or on the worldwide Internet. Compaq TCP/IP Services This manual describes how to configure for OpenVMS Management and manage the TCP/IP Services product. Use this manual with the Compaq TCP/IP Services for OpenVMS Management Command Reference manual. Compaq TCP/IP Services This manual describes the TCP/IP for OpenVMS Management Services management commands. Command Reference Use this manual with the Compaq TCP/IP Services for OpenVMS Management manual. Compaq TCP/IP Services This reference card lists the TCP/IP for OpenVMS Management management commands by component and Command Quick Reference describes the purpose of each command. Card Compaq TCP/IP Services This reference card contains for OpenVMS UNIX Command information about commonly performed Reference Card network management tasks and their corresponding TCP/IP management and Compaq Tru64 UNIX command formats. (continued on next page) ix Table_1_(Cont.)_TCP/IP_Services_Documentation____________________ Manual____________________Contents_______________________________ DIGITAL TCP/IP Services This manual presents an overview of for OpenVMS ONC RPC high-level programming using open Programming network computing remote procedure calls (ONC RPC). This manual also describes the RPC programming interface and how to use the RPCGEN protocol compiler to create applications. Compaq TCP/IP Services This manual describes how to use the for OpenVMS Sockets Sockets API and OpenVMS system services API and System Services to develop network applications. Programming Compaq TCP/IP Services This manual describes the Simple for OpenVMS SNMP Network Management Protocol (SNMP) Programming and and the SNMP application programming Reference interface (eSNMP). It describes the subagents provided with TCP/IP Services, utilities provided for managing subagents, and how to build your own subagents. Compaq TCP/IP Services This manual provides information for OpenVMS Tuning and about how to isolate the causes of Troubleshooting network problems and how to tune the TCP/IP Services software for the best performance. Compaq TCP/IP Services This manual describes the IPv6 for OpenVMS Guide to environment, the roles of systems IPv6 in this environment, the types and function of the different IPv6 addresses, and how to configure TCP/IP __________________________Services_to_access_the_6bone_network.__ For additional information about Compaq OpenVMS products and services, access the Compaq website at the following location: http://www.openvms.compaq.com/ x For a comprehensive overview of the TCP/IP protocol suite, you might find the book Internetworking with TCP/IP: Principles, Protocols, and Architecture, by Douglas Comer, useful. Reader's Comments Compaq welcomes your comments on this manual. Please send comments to either of the following addresses: Internet openvmsdoc@compaq.com Mail Compaq Computer Corporation OSSG Documentation Group, ZKO3-4/U08 110 Spit Brook Rd. Nashua, NH 03062-2698 How to Order Additional Documentation Visit the following World Wide Web address for information about how to order additional documentation: http://www.openvms.compaq.com/ If you need help deciding which documentation best meets your needs, call 800-282-6672. Conventions The name TCP/IP Services means both: o Compaq TCP/IP Services for OpenVMS Alpha o Compaq TCP/IP Services for OpenVMS VAX The name UNIX refers to the Compaq Tru64 UNIX operating system. The following conventions are used in this manual. In addition, please note that all IP addresses are fictitious. Ctrl/x A sequence such as Ctrl/x indicates that you must hold down the key labeled Ctrl while you press another key or a pointing device button. xi PF1 x A sequence such as PF1 x indicates that you must first press and release the key labeled PF1 and then press and release another key or a pointing device button. In examples, a key name enclosed in a box indicates that you press a key on the keyboard. (In text, a key name is not enclosed in a box.) In the HTML version of this document, this convention appears as brackets, rather than a box. . . . A horizontal ellipsis in examples indicates one of the following possibilities: o Additional optional arguments in a statement have been omitted. o The preceding item or items can be repeated one or more times. o Additional parameters, values, or other information can be entered. . A vertical ellipsis indicates the omission . of items from a code example or command . format; the items are omitted because they are not important to the topic being discussed. ( ) In command format descriptions, parentheses indicate that you must enclose choices in parentheses if you specify more than one. [ ] In command format descriptions, brackets indicate optional choices. You can choose one or more items or no items. Do not type the brackets on the command line. However, you must include the brackets in the syntax for OpenVMS directory specifications and for a substring specification in an assignment statement. xii | In command format descriptions, vertical bars separate choices within brackets or braces. Within brackets, the choices are optional; within braces, at least one choice is required. Do not type the vertical bars on the command line. { } In command format descriptions, braces indicate required choices; you must choose at least one of the items listed. Do not type the braces on the command line. bold text This typeface represents the introduction of a new term. It also represents the name of an argument, an attribute, or a reason. italic text Italic text indicates important information, complete titles of manuals, or variables. Variables include information that varies in system output (Internal error number), in command lines (/PRODUCER=name), and in command parameters in text (where dd represents the predefined code for the device type). UPPERCASE TEXT Uppercase text indicates a command, the name of a routine, the name of a file, or the abbreviation for a system privilege. Monospace text Monospace type indicates code examples and interactive screen displays. This typeface indicates UNIX system output or user input, commands, options, files, directories, utilities, hosts, and users. In the C programming language, this typeface identifies the following elements: keywords, the names of independently compiled external functions and files, syntax summaries, and references to variables or identifiers introduced in an example. xiii - A hyphen at the end of a command format description, command line, or code line indicates that the command or statement continues on the following line. numbers All numbers in text are assumed to be decimal unless otherwise noted. Nondecimal radixes-binary, octal, or hexadecimal-are explicitly indicated. xiv 1 _________________________________________________________________ New Features and Changes This chapter lists the new features of Compaq TCP/IP Services for OpenVMS V5.1. For more information about configuring and managing these services, see the Compaq TCP/IP Services for OpenVMS Management guide provided with the TCP/IP Services for OpenVMS V5.1 software. 1.1 Version 5.1 Features 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) o GATED Enhancements o Services that can be restarted individually o Cluster failover for the BIND server o BIND dynamic updates management enhancements o Updated SNMP that supports AgentX o SMTP AntiSPAM (configuration to control mail relay) o SMTP SFF (Send From File) o SMTP outbound alias o Metric server logicals that can be changed without restarting the Metric server o Cluster failover for the load broker o DHCP server can be configured to dynamically update BIND database o Xterminal support using XDM o TELNET client enhancements to support SNDLOC and NAWS o NFS server and client enhancements New Features and Changes 1-1 New Features and Changes 1.1 Version 5.1 Features o DHCP client support o TCP performance options 1.1.1 New Kernel TCP/IP Services Version 5.1 incorporates the kernel ported from Compaq Tru64 UNIX Version 5.1. In addition, TCP/IP Services provides better performance under conditions where a large number of connections are being used. Some of the features of the new kernel include: o SACK (Selective Acknowledgements) The new version of the kernel supports multiple acknowledgement windows, allowing outstanding acknowledgements even if the sequence numbers are not in order. For example, if 17 packets are sent, but only those numbered 1 through 4, 6 through 9, and 10 through 17 have been acknowledged, the remaining acknowledgements can be denoted as "outstanding." The software allows up to n outstanding acknowledgements, where n is the number in the TCP options header. For example, the number of outstanding acknowledgements for Ethernet is a maximum of 3. o PAWS (Protection Against Wrapped Sequence numbers) The new version of the kernel supplies time stamps on transactions. The kernel implements the timestamp option defined in RFC 1323 (Windowscale and Timestamp). This feature prevents sequence numbers from wrapping. Without it, sequence numbers can be negative, which causes conflict in acknowledgements. o Path MTU over UDP Previous versions of the kernel supported path MTU over TCP only. o Multiple adapters per subnet You can configure multiple active network adapters in one computer, even if they operate on the same subnetwork. For example, you can configure a WE0 interface at 192.24.156.20 and a WE1 interface at 192.24.156.21 with the same netmask. 1-2 New Features and Changes New Features and Changes 1.1 Version 5.1 Features When you establish a connection, the kernel routes the connection through the interface that has the smallest number of connections. As a result, connections are load-balanced, leading to greater throughput than on a system with only one adapter per subnetwork. You might choose to configure a system with multiple interfaces in the same subnetwork for the following reasons: - The current environment has only a single subnet, but additional bandwidth is needed to communicate with certain systems. - Your site cannot upgrade its network infrastructure to newer, faster technologies, such as Gigabit Ethernet, which would improve network throughput. - The source of a bottleneck is a particular system's network connection, but the switch to which it is connected is under-utilized and has additional ports and bandwidth available. Another connection to this system would reduce resource contention. - There are no additional IP subnetworks assigned or available for configuration, and the host requires more bandwidth to access the current subnetwork than one network interface card allows. For the system to function properly when configured in this manner, it must meet all of these conditions: * It must not be running a routing daemon (either GATED or ROUTED). * It must have access to all remote systems through each interface that is configured in the same subnet. For example, you must be able to successfully issue a ping command to the same remote system when each network interface is configured by itself. This implies that all interfaces in the system are connected to the same physical network switch. New Features and Changes 1-3 New Features and Changes 1.1 Version 5.1 Features This feature might affect the operation of network software or commands that rely on the network interface staying constant for the life of a connection. For example: * Multicast transmission might not work properly. * Utilities, such as traceroute, might give 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) This release contains Internet Protocol Version 6 (IPv6) support for Transmission Control Protocol (TCP), User Datagram Protocol (UDP), and raw sockets, and IPv6 support for commands and utilities. This support is for those customers who want to start using IPv6 today and for those who want to test or experiment with IPv6. This support is in addition to the IPv4 support already in TCP/IP Services. TCP/IP Services supports the following: o IPv6 base protocol and addressing specifications o Internet Control Message Protocol (ICMP) for IPv6 o Path MTU Discovery for IPv6 o Stateless Address Autoconfiguration o Neighbor Discovery o RIPng for IPv6 o Transition mechanisms for IPv6 hosts and routers o DNS extensions to support IPv6 and DNS dynamic updates o Basic IPv6 application programming interfaces (APIs) o IPv6 over Ethernet and Fiber Distributed Data Interface (FDDI) The following commands and applications have been modified to work in both an IPv6 and IPv4 environment: o BIND (8.1.2) server for AAAA (IPv6) records o TELNET server and client 1-4 New Features and Changes New Features and Changes 1.1 Version 5.1 Features o FTP server and client o RSH/REXEC client o RLOGIN client o SMTP o The following TCP/IP management commands: - IFCONFIG - ROUTE - PING - IP6RTRD - ND6HOSTD - NETSTAT - TRACEROUTE If you have configured IPv6 on the system, all of these commands and applications are automatically enabled for IPv6, except for SMTP. To enable SMTP for IPv6 as well as IPv4, enter the following TCP/IP management command: TCPIP> SET SERVICE SMTP/FLAGS=(LISTEN,IPV6) To configure and enable IPv6, you must run the TCPIP$IP6_ SETUP.COM command procedure. For more information, refer to the Compaq TCP/IP Services for OpenVMS Guide to IPv6. EAK users, refer to Section 2.1.1 in these release notes. 1.1.2.1 Name Space Configuration Guidelines Compaq recommends that IPv6 connectivity (whether native or using tunnels) to IPv6-capable systems be enabled before you register both IPv6 and IPv4 addresses for the same node. During the early stages of an IPv6 deployment, when only partial IPv6 connectivity is available, Compaq recommended that you register separate names or zones for IPv6 addresses. This prevents unintentional use of IPv6 addresses for connections to nodes that are not reachable using IPv6, thus avoiding problems with intermittent connectivity. When general IPv6 connectivity is available New Features and Changes 1-5 New Features and Changes 1.1 Version 5.1 Features throughout the network, both IPv6 and IPv4 addresses can be registered for the same nodes. When both IPv6 and IPv4 addresses are registered for the same node, an IPv6-capable application attempts to connect using IPv6 first, and, if the connection fails, uses an IPv4 address. When there is no IPv6 connectivity to remote systems, significant delays are experienced when attempting a connection using the IPv6 address before attempting to connect using the IPv4 address. 1.1.2.2 Using the Local Hosts Database If you have enabled IPv6, local IPv4 addresses are stored in two places: o Traditional RMS-indexed local hosts database (TCPIP$HOST.DAT) o New TCPIP$ETC:IPNODES.DAT file If there are duplicate entries in these database files, the local hosts database will be used. The local hosts database accepts only IPv4 addresses. The TCPIP$ETC:IPNODES.DAT file stores both IPv6 and IPv4 addresses. Applications like TELNET attempt to resolve addresses using the local hosts database first. Therefore, an IPv4 address in the local hosts database will always be used even if an IPv6 definition has been configured using BIND. In environments with a mix of IPv4 and IPv6 addresses, to ensure applications use IPv6 addresses first, do not define the host in the local hosts database. Use either the IPNODES.DAT file or the BIND database to define hosts with IPv6 addresses. 1.1.2.3 Configuring or Deleting Interfaces Under IPv6 If you are configuring a new interface or deleting an interface when IPv6 has been configured to run on the system, you must run the TCPIP$IP6_SETUP.COM command procedure again to reinitialize the interfaces. Otherwise, IPv6 will not work. 1-6 New Features and Changes New Features and Changes 1.1 Version 5.1 Features 1.1.3 GATED Enhancements TCP/IP Services has updated the gateway routing daemon (GATED). In this release, the Compaq implementation is based on GateD Unicast Version 4.0.6 from the Gatedaemon Project at Cornell University. GateD Unicast Version 4.0.6 supports the following Unicast protocols as specified by the IETF: o Intradomain Routing: RIP (V1, V2), OSPF, SLSP o Interdomain Routing: BGP (V3, V4), EGP o Network Management: SNMP o Network MIBs supported:(RIP, EGP, BGP, OSPF, SLSP) The additions to the GATED routing protocol are new BGP features, including route-reflection, communities, and destination preference attributes (DPA). ________________________ Note ________________________ The HELLO Protocol has been removed. The HELLO protocol was an interior protocol that used a routing metric based on the length of time it takes a packet to make the trip between the source and the destination. HELLO is not Y2K compliant, is not documented and should not be used. ______________________________________________________ 1.1.4 Restartable Services TCP/IP Services V5.1 provides startup and shutdown files for individual services, allowing system managers to stop and start individual services without affecting the operation of the remaining TCP/IP Services software. This is useful when you change configuration parameters or logical names that require a specific service to be restarted. For example, you can shut down the LPD service, change its configuration parameters, and then restart it without interrupting the other TCP/IP services that are running on the system. New Features and Changes 1-7 New Features and Changes 1.1 Version 5.1 Features Each service has its own startup and shutdown command procedures, as follows, where service is the name of the TCP/IP service: o SYS$STARTUP:TCPIP$service_STARTUP.COM, a supplied command procedure that starts the service specified by service. o SYS$STARTUP:TCPIP$service_SHUTDOWN.COM, a supplied command procedure that shuts down the service specified by service without affecting the other services that are running. For site-specific configuration and parameter settings, Compaq recommends that you create the following types of files in the directory pointed to by SYS$STARTUP. Note that these files will be preserved and not overwritten by subsequent installations of the TCP/IP Services software: o SYS$STARTUP:TCPIP$service_SYSTARTUP.COM, an optional command procedure that you may use to store site- specific startup commands for the service specified by service. o SYS$STARTUP:TCPIP@service_SYSHUTDOWN.COM, an optional command procedure that you may use to store site- specific shutdown commands for the service specified by service. For more information about starting and stopping the components of TCP/IP Services, see the Compaq TCP/IP Services for OpenVMS Management guide. 1.1.4.1 Obsolete Files Several files have been made obsolete by these changes: o TCPIP$DNFC_SHUTDOWN.COM o TCPIP$DNFS_SHUTDOWN.COM This file has been replaced by TCPIP$NFS_CLIENT_ SHUTDOWN.COM. o TCPIP$LOAD_INETDRIVER.COM This file has been replaced by TCPIP$INET_DRIVER_ STARTUP.COM. o TCPIP$LOAD_PPP.COM 1-8 New Features and Changes New Features and Changes 1.1 Version 5.1 Features This functionality is included in TCPIP$INET_ STARTUP.COM. o TCPIP$NFS_SERVER_STARTUP.COM This file has been replaced by TCPIP$NFS_STARTUP.COM. o TCPIP$PCNFSD_SHUTDOWN.COM This file has been replaced by TCPIP$PCNFS_SHUTDOWN.COM. o TCPIP$PORTM_SHUTDOWN.COM. This file has been replaced by TCPIP$PORTMAPPER_ SHUTDOWN.COM. o TCPIP$PWIP_SHUTDOWN.COM This file has been replaced by TCPIP$PWIP_DRIVER_ SHUTDOWN.COM. o TCPIP$PWIP_STARTUP.COM This file has been replaced by TCPIP$PWIP_DRIVER_ STARTUP.COM. o TCPIP$REMOTE_TTY_STARTUP.COM This functionality is included in TCPIP$INET_ STARTUP.COM. o TCPIP$SERVICE_SETUP.COM 1.1.4.2 New Files 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.COM o TCPIP$DHCP_CLUSTER_STARTUP.COM o TCPIP$DHCP_CLUSTER_SHUTDOWN.COM o TCPIP$FINGER_STARTUP.COM o TCPIP$FTP_CLIENT_STARTUP.COM o TCPIP$FTP_CLIENT_SHUTDOWN.COM o TCPIP$FTP_STARTUP.COM New Features and Changes 1-9 New Features and Changes 1.1 Version 5.1 Features o TCPIP$INET_DRIVER_STARTUP.COM o TCPIP$INET_DRIVER_SHUTDOWN.COM o TCPIP$LOCKD_STARTUP.COM o TCPIP$LOCKD_SHUTDOWN.COM o TCPIP$NFS_CLIENT_STARTUP.COM 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.COM 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.COM o TCPIP$REXEC_STARTUP.COM o TCPIP$REXEC_SHUTDOWN.COM o TCPIP$RLOGIN_STARTUP.COM o TCPIP$RLOGIN_SHUTDOWN.COM o TCPIP$RMT_STARTUP.COM o TCPIP$RMT_SHUTDOWN.COM o TCPIP$RSH_STARTUP.COM o TCPIP$RSH_SHUTDOWN.COM o TCPIP$TELNET_STARTUP.COM o TCPIP$TELNETSYM_STARTUP.COM o TCPIP$TELNETSYM_SHUTDOWN.COM o TCPIP$TFPT_STARTUP.COM o TCPIP$UCP_SHUTDOWN.COM o TCPIP$XDM_STARTUP.COM 1-10 New Features and Changes New Features and Changes 1.1 Version 5.1 Features o TCPIP$XDM_SHUTDOWN.COM 1.1.4.3 Changes to the TCPIP$CONFIG.COM Command Procedure The TCPIP$CONFIG.COM configuration command procedure includes the following new options: o TELNETSYM is offered as a separately manageable service. o Configure the system as a DHCP client instead of a DHCP server. 1.1.5 BIND Enhancements The following sections describe new features of BIND, the TCP/IP Services implementation of the DNS. 1.1.5.1 BIND Server Cluster Failover In previous versions of TCP/IP Services, there was no convenient method for running more than one BIND master server in the same OpenVMS cluster. Multiple BIND master servers can share a common database, thus providing redundancy and a failover mechanism when one of the servers becomes unavailable. For instructions on setting up cluster failover for BIND, refer to the Compaq TCP/IP Services for OpenVMS Management guide. ________________________ Note ________________________ Do not use BIND dynamic updates in a BIND cluster failover environment. This is not supported and may cause problems. Do not enable dynamic updates in a master BIND server that is participating in a BIND failover environment. ______________________________________________________ 1.1.5.2 Managing BIND Dynamic Updates 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 o A safety net mechanism to save changes made during the dynamic update procedure. New Features and Changes 1-11 New Features and Changes 1.1 Version 5.1 Features These features are described in the Compaq TCP/IP Services for OpenVMS Management guide. 1.1.6 Updates to SNMP After you upgrade to this version of TCP/IP Services, you must perform two additional steps to ensure the latest version of SNMP is running on the system. With the configuration procedure TCPIP$CONFIG.COM: 1. Disable SNMP. 2. Enable SNMP. The version of SNMP included with TCP/IP Services V5.1 includes new API routines to support extended agent functionality (AgentX). Master/subagent interprocess communication is TCP-based, rather than UDP-based, for increased awareness by agents when cooperating processes exit. Also, the logging information for a trace has been changed. This release of TCP/IP Services supports the following SNMP RFCs: o RFCs 1901 through 1908 (SNMPv2C) in the Extensible SNMP Agent, subagent developer tools, and SNMP-related commands. o RFC 2257 (Agent Extensibility) in the Extensive SNMP Agent and subagent developer tools. o RFC 2089 (Mapping SNMPv2 to SNMPv1) in the bilingual extensible SNMP agent. There are also some OpenVMS specific changes in the areas of logging and configuration options. Configuration includes new text files to supplement the UCP mechanism. Error messages are logged in SYS$SYSDEVICE:[TCPIP$SNMP], using files with names based on the subagent name. A configuration option allows you to specify that messages are to be sent to the terminal window when processes are run interactively. Because the new AgentX API is TCP-based, the master agent can detect immediately when the subagent exits abnormally and can perform the necessary cleanup operations. Subagents can do the same when the master agent exits. Logging data, 1-12 New Features and Changes New Features and Changes 1.1 Version 5.1 Features captured when tracing is enabled, reflects data from the underlying AgentX protocol. The previous version of SNMP was limited to the simpler DPI. 1.1.6.1 Managing the SNMP MIB Browser The following flags have been added to the MIB browser (snmp_request) in this version of the software: o -i max_ignores Specifies the number of times the MIB browser listens for a reply packet to a request if it receives an invalid packet (caused by an invalid packet identifier, version, or SNMP version and command combination). Specify a positive integer for the value (max_ignores). If you specify a negative value, it will be converted to an unsigned positive integer. If you specify 0, no retries are tried. If, after an invalid reply packet is received, a valid reply packet is received, the ignore counter is reset to the value of max_ignores. If a timeout occurs after an invalid packet is received, the packet is resent, the resend counter is decremented, and the ignore counter is reset to the value of max_ ignores. You cannot use the -i flag when you perform a query with the -l or -t flags to automatically increment the input OID and continue querying a server after a general SNMP error has occurred, as may happen with a faulty server. In this case, the query is terminated even though the end of the MIB selection has not been reached. You must manually increment the input OID to skip the error and continue with the query. o -r max_retries Specifies the number of times the MIB browser resends a request packet if it times out before receiving a reply. Specify a positive integer for the value (max_retries). If you specify a negative value, it will be converted to an unsigned positive integer. If you specify 0, no retries are tried. New Features and Changes 1-13 New Features and Changes 1.1 Version 5.1 Features If, after a timeout and a resend, a reply packet is received, the resend counter is reset. After another timeout, the specified number of max_retries will be sent. o -s sleep_interval Specifies the number of seconds between iterations of sending a request (for the -r flag) and listening for a reply (for the -i) flag. The default is 1 second. This flag is ignored if neither the -r flag nor the -i flag are specified. The -s flag is useful for specifying a time to wait between resends, which might be necessary when a server agent is starting up. The -i, -r, and -s flags apply to individual queries. If 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 This version of TCP/IP Services includes the following SMTP features: o AntiSPAM, allowing you to configure your host to prevent relaying mail. For more information about antiSPAM configuration, see the Compaq TCP/IP Services for OpenVMS Management guide. o Send from File (SFF), allowing users to mail non- text files and to automate mail programs. For more information, see Section 1.1.7.1. o Outbound alias, allowing users to specify the reply address. For more information, see Section 1.1.7.2 1.1.7.1 SMTP SFF (Send From File) SMTP allows you to create a mail message in a file and send it to the SMTP mailer to be delivered with headers you specify. Using this feature, you can create automated tools that compose and send mail messages. It is also useful for forwarding non-text files (MIME), because it prevents the mailer from encapsulating the MIME and SMTP headers in the body of a new mail message. Thus, SMTP can function like the redirect command on your personal computer, which 1-14 New Features and Changes New Features and Changes 1.1 Version 5.1 Features simply takes the message as is, without encapsulating it in another message, and sends it to the person you name. To redirect a MIME mail message without encapsulation so that it is readable to the receiver, follow these steps: 1. From OpenVMS MAIL, use EXTRACT/NOHEADER to extract the mail message. 2. Exit the MAIL program. 3. Modify the file to include the SMTP commands. For example, put the address of the recipient into the RCPT TO:<> line. For more information about the SFF format, see Section 1.1.7.1.1. 4. Send the file to SFF. If you want headers like From:, To:, or Message-ID:, you must include them in the file. SFF adds only the Received: header, as described in Section 1.1.7.1.3. 1.1.7.1.1 Format of the SFF File You can use SFF to send a text file that complies with RFC 822 by including commands (as described in RFC 821) preceding the RFC 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: RCPT TO: DATA Date: Sun, 4 Aug 1996 14:48:14 -0400 Message-Id: <96080414481486@abc.com> From: green@abc.com (Charly Green - ABC-Corp engineering) To: green@abc.com Subject: Test of SFF mechanism This is the message text. The SMTP protocol commands specify: 1. The return path of the mail 2. The recipients 3. The DATA command New Features and Changes 1-15 New Features and Changes 1.1 Version 5.1 Features 4. The RFC 822 message The commands that precede the RFC 822 messages must appear in the file in the order listed above. The MAIL FROM and RCPT TO commands form the "envelope," as described in RFC 821 and summarized as follows: 1. The MAIL FROM command specifies the address to which the mail is bounced if necessary. There must be one and only one MAIL FROM command. You can specify a blank MAIL FROM command. For example: MAIL FROM:<> 2. The RCPT TO command specifies the address of a recipient. There must be at least one RCPT TO command but there can be more, one for each recipient. Do not specify a blank RCPT TO command. Each RCPT TO command must occupy a separate line and may contain only one address. If the mail is to go to multiple addresses, include one RCPT TO command for each address. 3. The DATA command follows the last RCPT TO command; it flags the end of the RCPT TO commands and the beginning of the header block. The DATA command is required. Do not include a Return-Path header in the RFC 822 headers. If the mail is to be delivered locally, SMTP includes a Return-Path header based on the MAIL FROM command. If the mail is relayed to another SMTP host, the return path is determined by the MAIL FROM command on the final destination host. 1.1.7.1.2 SFF File Requirements The mail message file can be in either of the following formats: o Variable length This type of file does not require carriage-return/line- feed characters at the end of each line. o Stream_LF This type of file requires at least a line-feed character at the end of each line. It is not necessary to add carriage-return characters. 1-16 New Features and Changes New Features and Changes 1.1 Version 5.1 Features 1.1.7.1.3 SFF Security Measures The ability to create messages with arbitrary headers could be used to spoof message headers. To limit this, the SFF mechanism includes the following security measures: o The process must have either BYPASS, SYSPRV, or OPER privilege set. o To help you track messages, SFF adds a Received: header to the headers you supply. This tells you the origin of an attempted spoofed message. You can invoke SFF from an application or from DCL, as described below. 1.1.7.1.4 Invoking SFF from an Application TCPIP$SMTP_ MAILSHR.EXE contains a routine called TCPIP$SMTP_SEND_FROM_ FILE. This routine is declared as follows: unsigned int TCPIP$SMTP_SEND_FROM_FILE(infile_name,logfd,log_level) char *infile_name; FILE *logfd; int log_level; The arguments for this routine are: o infile_name Specifies the name of the text file that contains the RFC 822 mail message. o logfd Specifies the file to which to log diagnostic messages. This file must be opened by the caller before calling this routine. If no log file is specified, output goes to SYS$OUTPUT. This argument is optional. o log_level Specifies the level of diagnostics to use: either 1 (on) or 0 (off). The default is 0 (off). This argument is optional. To call the routine, link with TCPIP$SMTP_MAILSHR.EXE/SHARE. New Features and Changes 1-17 New Features and Changes 1.1 Version 5.1 Features 1.1.7.1.5 Invoking SFF from DCL The SMTP_SFF command allows you to invoke SFF. To define SMTP_SFF as a foreign command so that you can use it from DCL, enter the following command: $ SMTP_SFF:==$TCPIP$SYSTEM:TCPIP$SMTP_SFF.EXE This command takes UNIX style parameters and passes them to SFF. The command format is: SMTP_SFF infile_name [-log logfile_name] [-loglevel log_level] Where the parameters to this command are: o infile_name Specifies the name of text input file containing the SMTP mail to send. o logfile_name Specifies the name of the log file for diagnostic messages. (The default is SYS$OUTPUT.) o log_level Specifies the debug log level: either 1 (on) or 0 (off). (The default is 0 (off).) 1.1.7.2 SMTP Outbound Alias The new version of TCP/IP Services SMTP supports the specification of an outbound alias that is applied to mail as it is sent and specifies the network address to which a reply will be sent. 1.1.7.2.1 Defining the Outbound Alias In some cases it is desirable to have control over the contents of the From: mail header in mail messages that you send. Setting your own From: header is called "outbound alias." To set this up, define the TCPIP$SMTP_FROM logical to the text you want your From: header to be. For example, you might define the logical as follows: $ DEFINE TCPIP$SMTP_FROM "bill.smith@xxx.com" This command sets the outbound alias to the following: From: bill.smith@xxx.com 1-18 New Features and Changes New Features and Changes 1.1 Version 5.1 Features Define the TCPIP$SMTP_FROM logical before entering OpenVMS Mail. If you always want the header to be sent with the outbound alias, define the logical in your login command procedure (LOGIN.COM). The outbound alias must be a valid address to which recipients can reply. If it is not valid, recipients will not be able to reply to you and bounced mail messages will not get back to you. If you do not define the TCPIP$SMTP_FROM logical, the From: address on your mail messages is the same one that you have always had. Use only simple 7-bit ASCII characters in the value you assign to the TCPIP$SMTP_FROM logical. Do not use control characters. The address you use to define TCPIP$SMTP_FROM must be an RFC 822 legal SMTP address; that is, user@domain. If the address is not interpreted correctly, the SMTP mailer ignores it and uses the From: address that it has constructed for you. 1.1.7.2.2 Appending the Personal Name String to the Outbound Alias If you have defined an OpenVMS Mail personal name string, the SMTP mailer appends that string to the outbound alias. For example, a personal name string is defined as follows: Bill L. Smith Phone: 123-456-8000 The TCPIP$SMTP_FROM logical is defined as follows: $ DEFINE TCPIP$SMTP_FROM "bill.smith@xxx.com" The resulting From: header is the following: From: bill.smith@xxx.com (Bill L. Smith Phone: 123-456-8000) The personal name is appended to the From: address only if both of the following conditions are met: o The value you give for the TCPIP$SMTP_FROM logical does not contain parenthetical phrases (text within parentheses). New Features and Changes 1-19 New Features and Changes 1.1 Version 5.1 Features o The From: address contains the SMTP domain string (the @domain portion of the address). To use a different personal name string than the one defined in your OpenVMS mail personal name, define the personal name string as part of the TCPIP$SMTP_FROM logical in a parenthetical phrase after the user@domain address. Separate the address address from the parenthetical phrase with a space. Do not use double quotes (") in the personal name. For example, you can define the outbound alias logical as follows: $ DEFINE TCPIP$SMTP_FROM - $_ "bill.smith@xxx.com (Phone: 123-456-8000 FAX: 123-456-9000)" The SMTP mailer does not allow you to define the TCPIP$SMTP_FROM logical using the following syntax: "personal name" Also, do not specify the logical as follows: $ DEFINE TCPIP$SMTP_FROM """personal name"" " Instead, define the logical as follows: $ DEFINE TCPIP$SMTP_FROM "bill.smith@xxx.com (personal name)" 1.1.7.2.3 Appending a Substitute Domain String If you define TCPIP$SMTP_FROM without an SMTP domain string (the @domain portion of the address), SMTP will append the substitute domain name to the text you define. If there is no substitute domain name defined, the host name is used. For example, the host is configured with a substitute domain of x.com, and the TCPIP$SMTP_FROM logical is defined as follows: $ DEFINE TCPIP$SMTP_FROM "bill.smith" In this case, the resulting address is: From: bill.smith@x.com 1-20 New Features and Changes New Features and Changes 1.1 Version 5.1 Features However, if the host is not configured with a substitute domain and the host name is host.x.com, and SMTP_FROM is defined as follows: $ DEFINE TCPIP$SMTP_FROM "bill smith" In this case, the resulting address is: From: bill.smith@host.x.com 1.1.7.2.4 Disabling Modifications to TCPIP$SMTP_FROM To disable the modifications that TCPIP SMTP makes to the value you assign to TCPIP$SMTP_FROM (such as appending the OpenVMS personal name and @domain to a value with no @domain), include the string [VERBATIM]. For example: $ DEFINE TCPIP$SMTP_FROM "[VERBATIM] bill.smith@xxx.com" This will result in the following: From: bill.smith@xxx.com 1.1.7.2.5 TCPIP$SMTP_FROM and the Return-Path: Header The address you define will be used for the Return-Path: mail header. The Return-Path: header is used to bounce undeliverable mail. Note that the version of the text used for the Return-Path header is stripped of comments (such as the personal name string) and will always have a @domain string. (See Section 1.1.7.2.3 for more information about the domain name that is supplied.) 1.1.7.2.6 X-VMS-True-From: Header When the TCPIP$SMTP_ FROM logical is used to set the From: header, the text that would normally have been used for the From: header is added to the headers as an X-VMS-True-From: header. This is an anti-spoofing measure. 1.1.7.2.7 Managing Outbound Alias Processing To disable outbound alias processing and use of the TCPIP$SMTP_FROM logical, define the following system logical: $ DEFINE/SYSTEM TCPIP$SMTP_PROHIBIT_USER_HEADERS 1 New Features and Changes 1-21 New Features and Changes 1.1 Version 5.1 Features 1.1.8 Metric Server Enhancements The Metric server works with the load broker to provide load balancing across OpenVMS clusters. The following enhancements have been made to the Metric server in this release: o Dynamic configuration Logicals names may be defined for CPU rating, compute interval, and debug level. In previous versions of TCP/IP Services, modifications to these logicals would take effect only after the Metric server is shut down and restarted. With this release, the Metric server recognizes changes to the definitions of these logicals dynamically. For more information about metric server logicals, refer to the Compaq TCP/IP Services for OpenVMS Management guide. o Enhanced logging processes The Metric server logging processes have been enhanced to include more messages, and more informative information provided with messages. The Metric server messages are organized into the following categories: - Informational messages - Warning message - Error messages - Debug messages All these messages are logged to a single file, as follows: SYS$SPECIFIC:[TCPIP$METRIC]TCPIP$METRIC_RUN.LOG o Support for multihomed systems This feature allows load balancing of incoming traffic across multiple IP addresses. Each IP address on a system can now participate in the metric. For example, the load broker can be configured to include, in the member list, multiple IP addresses from a single system. The load broker will poll each of the addresses and if it is available, the Metric server will respond for each address. Using the load broker algorithm, this will 1-22 New Features and Changes New Features and Changes 1.1 Version 5.1 Features update DNS with each of the IP addresses, and hence the load balancing on a system can be shared across multiple interfaces. Note that the metric is still calculated on a per system basis. So the Metric server will respond with the same metric value for all IP addresses on a single system. o Debug logical name The name of the logical to set for debug mode has been changed. In previous versions of TCP/IP Services, the logical name is TCPIP$METRIC_DBG_LEVEL. The new logical is: TCPIP$METRIC_LOG_LEVEL As in the previous version, this logical accepts as values 1 and 2, where 2 provides more information. 1.1.9 Load Broker Cluster Failover With this release, you can run the Load Broker (LBROKER) on multiple systems in an OpenVMS cluster. This is accomplished through a locking mechanism. The first LBROKER process to start in the cluster obtains the lock, and any LBROKER processes started afterwards go into a standby state, waiting for the lock to be released. If the system running the first LBROKER goes down, the LBROKER releases the lock, allowing the next available standby LBROKER to obtain the lock. This system then runs the active LBROKER process; additional servers may remain on standby. No additional configuration is required. To disable the failover mechanism for the LBROKER, define the following system logical: $ DEFINE /SYSTEM TCPIP$LBROKER_ALLOW_CONCURRENT_SERVERS 1 When this logical is defined, you can run multiple LBROKER processes in an OpenVMS cluster without the locking mechanism described above. New Features and Changes 1-23 New Features and Changes 1.1 Version 5.1 Features 1.1.10 DHCP Dynamically Updates BIND This feature allows DHCP clients to be configured with a registered name, which DHCP will use to assign an address when it updates the BIND database. To configure DHCP dynamic updates to BIND, complete the following procedure: 1. Set the following configuration options in the SERVER.PCY file (or use the DHCP GUI to make these changes): o accept_client_name o assign_name_by_hwaddr o dns_tracks_dhcp_lease o name_service_updateable 2. Set up the BIND server to accept dynamic updates from the DHCP server. If you are running DHCP on multiple nodes in an OpenVMS cluster, be sure to perform this step on all the nodes where the DHCP server runs. For more information about enabling BIND server dynamic updates, refer to the Compaq TCP/IP Services for OpenVMS Management guide. 3. Set up the .DDNSKEYS file. This file resides in TCPIP$DHCP_CONFIG (if that logical is defined), or in the DHCP account's default directory (SYS$SYSDEVICE:[TCPIP$DHCP]). There is no file name for the file. It is simply a file with no name and an extension of .DDNSKEYS (for example, TCPIP$DHCP_CONFIG:.DDNSKEYS). The .DDNSKEYS file contains entries that describe each of the BIND domains to update with the DHCP server. Each line represents one entry and has 3 fields, separated by spaces: 1. The domain to be updated 2. The IP address of the BIND server to which the DHCP server should send updates for the domain 3. This field is reserved for future use with secure dynamic updates. 1-24 New Features and Changes New Features and Changes 1.1 Version 5.1 Features The DHCP server updated BIND for forward and backward translation; therefore, you need two entries: one for each translation. For backward translation, the BIND "in-addr.arpa" convention is used. For example, to be able to send updates to a BIND server at 17.21.208.100 for the domain fu.bar.com, include the following: $ TYPE .DDNSKEYS fu.bar.com 17.21.208.100 21.17.in-addr.arpa 17.21.208.100 4. Set the dns_tracks_dhcp_lease parameter in the SERVER.PCY file. If a dynamic BIND update fails, the DHCP server logs an error and grants the lease of the IP address to the DHCP client, but does not automatically repeat the failed dynamic DNS update operation. Further, when the lease on the particular IP address is renewed by the client, the DHCP server will not send another dynamic BIND update at that time, unless the dns_tracks_dhcp_lease parameter is set in the SERVER.PCY file. Therefore, Compaq recommends that you set the dns_tracks_dhcp_lease parameter in the SERVER.PCY file if the server is set up to perform dynamic BIND updates. 1.1.11 XDM Terminal Support For network displays, such as X terminals, the login server supports the X Display Manager Control Protocol (XDMCP) 1.0, which allows display devices to request that the login server display a login screen on the display. To use XDMCP, the system must be running DECwindows Motif Version 1.2-5 or later. For information about configuring XDM on your system, refer to the Compaq TCP/IP Services for OpenVMS Management guide. New Features and Changes 1-25 New Features and Changes 1.1 Version 5.1 Features 1.1.12 TELNET Client Enhancements The TELNET client component has been enhanced for this release, including support for window sizing (rows and columns), and location options. These options depend on appropriate support from the TELNET server. o The NAWS (Negotiate About Window Size) option allows the client to respond to a request from the TELNET server for information about the local terminal (or window) size, including the columns and lines per page. This ensures the TELNET terminal (TNA) is set accordingly. Note the using the SET TERMINAL/INQUIRE command can cause the terminal's width and page size to be reset. o The SNDLOC option allows the TELNET client to send information that can be used to identify the location of the TELNET client device on the host. The client passes the physical terminal name and the user name to the server. For example, user SMITH on terminal device _RTA: appears as _RTA2:/SMITH. With this release, the information appears on the TELNET server as Locn: _RTA2:/SMITH in the access portname string. Note that the RLOGIN protocol obtains the user's name from the RLOGIN session information provided when the connection is established, and the user name is included in the access portname string as User: . 1.1.13 NFS Server and Client Enhancements This release includes several enhancements to NFS, including: o New NFS server that supports: - Both NFS V2 and NFS V3 protocols - Both UDP and TCP o Changes to file size processing that may improve performance o NFS server configuration parameters that are managed using sysconfig o File locking o New MOUNT V3 component 1-26 New Features and Changes New Features and Changes 1.1 Version 5.1 Features These features are described in more detail in the following sections. 1.1.13.1 NFS V3 Protocol This release features a new version of the NFS server. The new NFS server is compliant with both of the following RFCs: o RFC 1094, Network File System Protocol Specification o RFC 1813, NFS Version 3 Protocol Specification The NFS server provided with TCP/IP Services V5.1 responds to both the NFS V2 and V3 protocols, as described in these RFCs. The main improvements offered by using the NFS V3 protocol include: o Increased maximum file size The maximum file size allowed by the NFS V3 protocol is 1 terabytes for an OpenVMS files system, and 4 gigabytes for a container file system. For the NFS V2 protocol, the maximum file size is 2 gigabytes for both the OpenVMS and container file systems. If your system has files of between 2 and 4 gigabytes, you should upgrade to TCP/IP Services V5.1 only if the NFS clients are using the NFS V3 protocol. ________________________ Note ________________________ The TCP/IP Services NFS client does not yet support the NFS V3 protocol. ______________________________________________________ o Enhanced write performance With this release, the NFS server may acknowledge a write operation before the data is actually written to disk. Afterwards, the server's response to a commit message confirms that the data has been written to disk. New Features and Changes 1-27 New Features and Changes 1.1 Version 5.1 Features 1.1.13.2 Extending and Truncating Files The new version of the NFS server determines file sizes differently than in previous versions. The changes represent significant performance improvements for some users, as follows: o When writing files sequentially from an OpenVMS client, performance may improve significantly, depending on whether the file is preextended or not. Output files are normally preextended by the COPY utility. o When copying files from a UNIX client to an OpenVMS server, you can obtain some performance improvement by setting a larger default extend quantity using the DCL command SET VOLUME/EXTENSION. Enter the HELP SET VOLUME command for more information. This quantity is first set when the volume is initialized. For file copying from OpenVMS clients, this improvement may also apply for files that are not preextended. o When copying or writing files from a UNIX client, the file size is truncated to end-of-file (EOF) when the NFS server closes the file. The timing of the close operation depends on the inactivity timer. If the server shuts down, any currently open files will not be truncated to EOF. If any extra blocks are remaining, you can remove them with the DCL command SET FILE/TRUNCATE. 1.1.13.3 NFS Client Reports True Allocated Size In previous releases, the OpenVMS NFS client always reported the allocated size as equal to the EOF size. In this release, the client attempts to report the true allocated size. However, when it explicitly extends or truncates a file, the client assumes that the file size is exactly what it requested until it refreshes its cached file attributes, which may be some time later. The true allocated size may be larger because of the volume allocation cluster factor. 1-28 New Features and Changes New Features and Changes 1.1 Version 5.1 Features 1.1.13.4 MOUNT Retry Default Value The default value for the /RETRIES qualifier to the MOUNT command has been changed to 4. This is the same as the soft mount default in most UNIX operating systems. Limiting the number of retries limits the maximum allowable wait. To establish a new default, define the following logical name: TCPIP$NFS_CLIENT_MOUNT_DEFAULT_RETRIES This logical name modifies the default for the number of times an I/O operation will be attempted. Set this logical to a non-negative integer. Defining this logical to be zero (0) restores the "infinite retry, unlimited wait" implemented in earlier versions of TCP/IP Services. A value of zero results in the equivalent of a UNIX hard mount. You can override the default setting by using the /RETRIES qualifier to the TCP/IP management command MOUNT. 1.1.13.5 Network Locking This release supports a partial implementation of NFS network locking, which allows users to lock files. The software coordinates locks among remote users and between remote and local users. The file locking features is applicable regardless of whether the OpenVMS Record Management System (RMS) is used or not. However, NFS does not coordinate network locking and RMS record locks. This version of NFS does not support byte-range locking. If a byte-range lock request is received, it is handled as a file lock request. File locking is implemented using the Network Lock Manager (NLM) and the Network Status Monitor (NSM). The NLM coordinates locks made by clients. The NSM recovers lock information in case the server or client crashes. The NSM uses the NLM to keep the host list when the client or the server crashes and reboots, as follows: o If the client crashes and reboots, it notifies the NSMs on its host list. In turn, the NSMs tell their local NLMs to free any locks held for that client. New Features and Changes 1-29 New Features and Changes 1.1 Version 5.1 Features o If the server crashes, when it reboots it notifies the NSMs on each client host in its host list. In turn, the client NSMs tell their local NLMs to rerequest all the locks that were granted on their behalf by the server before it crashed. The NSM and the NLM are enabled if you select "LOCKD/STATD" from the Server Configuration menu in the TCPIP$CONFIG.COM configuration procedure. As a result, two processes are started when you start TCP/IP Services: TCPIP$LOCKD and TCPIP$STATD. For more information about managing the file locking feature, refer to the Compaq TCP/IP Services for OpenVMS Management guide). Also, see Section 3.7 in these release notes. 1.1.13.6 Managing the MOUNT Service The MOUNT service responds to Version 1 of the MOUNT protocol, which is used with Version 2 of the NFS protocol. It also supports Version 3 of the MOUNT protocol, which is used with Version 3 of the NFS protocol. The MOUNT service now runs as a separate process; in previous versions of TCP/IP Services, MOUNT ran as part of the NFS service. The MOUNT service is started automatically when you start the NFS server (for example, using TCPIP$NFS_STARTUP.COM). For information about managing the MOUNT service, refer to the Compaq TCP/IP Services for OpenVMS Management guide. 1.1.14 DHCP Client Configuration This version of TCP/IP Services allows you to designate the system as a DHCP client, to be automatically configured by a DHCP server. The same system cannot be both a DHCP client and a DHCP server. The DHCP client software conforms to the following RFCs: o RFC 2131, Dynamic Host Configuration Protocol o RFC 2132, DHCP Options and BOOTP Vendor Extensions The DHCP client service is described in the Compaq TCP/IP Services for OpenVMS Management guide. 1-30 New Features and Changes New Features and Changes 1.1 Version 5.1 Features To enable DHCP client functionality, you can either manually configure the DHCP client, or you can allow the software to configure the DHCP client. o To manually configure the DHCP client and its interface: 1. Install the TCP/IP Services V5.1 software. 2. Run the TCPIP$CONFIG configuration command procedure. 3. Configure a network interface for control by the DHCP Client. The DHCP client requires control of least one network interface. The designated interface will get its IP address, subnet mask and broadcast address automatically from the DHCP server when TCPIP$STARTUP.COM is invoked. From the "Core Environment" menu, select "Interfaces." For each interface, the procedure asks you to select one of the following: 1 - Configure interface manually 2 - Let DHCP configure interface Select "2" to designate the interface as a DHCP client interface. 4. The procedure then asks whether the interface should be designated as the "primary interface." Refer to the Compaq TCP/IP Services for OpenVMS Management for more information about primary interfaces. 5. If you configure an interface to be under DHCP control, the procedure checks to see if you have enabled DHCP client. (To enable DHCP client, from the main menu select "Clients". From the Clients menu, select "DHCP Client." If the DHCP client had not been enabled, the TCPIP$CONFIG procedure automatically invokes the Client menu. Select "Enable service on this node." The procedure sets up the environment for DHCP client, including: - Creates the the DHCP account. - Creates the DHCP directory. New Features and Changes 1-31 New Features and Changes 1.1 Version 5.1 Features - Loads the CLIENT.PCY file into the DHCP directory. - Loads the HOSTNAME. file, which specifies the host name to request from the DHCP server, into the DHCP directory. This file is populated by the TCPIP$CONFIG configuration procedure and contains the SCSNODE name. o To allow the software to automatically configure DHCP client, follow the steps listed below. The procedure is only valid on a system where TCP/IP Services has not been previously configured. 1. Install the TCP/IP Services V5.1 software. 2. Execute the TCP/IP Services startup procedure, TCPIP$STARTUP.COM. 3. The startup procedure detects the fact that TCP/IP Services have not been configured. It asks whether you want the DHCP Client to configure the host for you. Answer "Yes". 4. The startup procedure invokes TCPIP$CONFIG, which sets up the environment for the DHCP client and designates any unconfigured interfaces to be under DHCP client control. The procedure enables the following set of services automatically: - FTP client - TELNET client - TELNET server If there is more than one interface, the procedure determines whether any interface is configured with a permanent IP address. In this case, none of the interfaces are designated as the primary interface. If there are no interfaces configured with permanent IP addresses, the procedure designates the first interface it discovers as the primary interface. You can run the TCPIP$CONFIG procedure later to change the interface and service configurations. 1-32 New Features and Changes New Features and Changes 1.1 Version 5.1 Features 1.1.15 TCP Performance Options This release of TCP/IP Services supports the following socket programming options, which may improve the performance of network applications: o TCP_TSOPTENA When the TCP_TSOPTENA option is enabled, the sender places a timestamp in each data segment. The receiver, if configured to accept them, sends these times back in the acknowledgement (ACK) segments. This allows the sender to measure the round-trip communication time. o TCP_PAWS When the TCP_PAWS (Protect Against Wrapped Sequence numbers) option is enabled, the receiver rejects any old duplicate segments it receives. This option is used on synchronized TCP connections only, and requires that the TSOPTENA option be enabled also. o TCP_SACKENA When the TCP_SACKENA (Selective Acknowledgment) option is enabled, the receiver can inform the sender about all segments that arrive successfully. This allows the sender to retransmit only those segments that have actually been lost. This option is useful in cases where multiple segments are dropped. 1.2 Version 5.1 Changes The following sections describe additional changes made from TCP/IP Services Version 5.0A to Version 5.1. 1.2.1 Unsupported Management Commands The following commands are not intended for use by customers. Use of these commands may cause unpredictable results: o COPY CONFIGURATION o GENERATE MAP o START COMMUNICATION o STOP COMMUNICATION o STOP MAIL New Features and Changes 1-33 New Features and Changes 1.2 Version 5.1 Changes o STOP NAME_SERVICE o ZERO INTERFACE In addition, the following options and qualifiers are no longer supported: 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. These commands, qualifiers, and options are no longer documented in the Compaq TCP/IP Services for OpenVMS Management Command Reference manual. 1.2.2 Changes to Management Commands The following changes have been made to TCP/IP management commands: o The product name as reflected by the SHOW VERSION command has been changed. For example: TCPIP> SHOW VERSION Compaq TCP/IP Services for OpenVMS . . . o The behavior of the START COMMUNICATION/INITIALIZE command was changed. Specifically: - This command no longer enables services or loads communication proxies. These operations are performed by the service-specific startup files. - If DHCP client has been selected in the TCPIP$CONFIG.COM procedure, this command runs the dhcpconf utility, which invokes DHCP client on the specified interface. ________________________ Note ________________________ The START COMMUNICATION command is reserved for use by Compaq only. ______________________________________________________ o The SET INTERFACE command accepts two new qualifiers: /PRIMARY and /DHCP. 1-34 New Features and Changes New Features and Changes 1.2 Version 5.1 Changes o The SET CONFIGURATION INTERFACE command accepts two new qualifiers: /[NO]PRIMARY and /[NO]DHCP. For more information, see the Compaq TCP/IP Services for OpenVMS Management manual. 1.2.3 Changes to NFS Server Configuration Under previous versions of TCP/IP Services, you can 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: - /CONTINUOUS=n - /HOST=host - /IDENTIFICATION - /PARAMETERS - /SERVICES - /USER_NAME=user-name o TCPIP$NFS000000000* logical names: - TCPIP$NFS000000000_ERROR - TCPIP$NFS000000000_OPCOM - TCPIP$NFS000000000_HOSTS - TCPIP$NFS000000000_UID - TCPIP$NFS000000000_GID - TCPIP$NFS000000000_INACTIVITY New Features and Changes 1-35 New Features and Changes 1.2 Version 5.1 Changes - TCPIP$NFS000000000_SECURITY - TCPIP$NFS000000000_THREADS - TCPIP$NFS000000000_XID 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=n o SHOW NFS_SERVER command. Qualifiers include: - /CLIENT=user-name - /CONTINUOUS=n - /SERVER=host-name - /VERSION=[V2|V3] o SYSCONFIG command For more information about using SYSCONFIG to modify NFS server attributes, see Section 1.2.3.2. The following qualifiers, which were used under previous versions of TCP/IP Services, are no longer supported: o /IDENTIFICATION o /PARAMETERS o /SERVICES The NFS server logical names are no longer supported. In some cases, you can use SYSCONFIG to change an equivalent attribute instead. See Section 1.2.3.2 for more information about using SYSCONFIG. The following table lists the NFS server logical names, and, where appropriate, the equivalent attribute: 1-36 New Features and Changes New Features and Changes 1.2 Version 5.1 Changes ___________________________________________________________ Logical_Name___________________Attribute___________________ TCPIP$NFS000000000_ERROR No equivalent TCPIP$NFS000000000_OPCOM No equivalent TCPIP$NFS000000000_HOSTS No equivalent TCPIP$NFS000000000_UID noproxy_uid TCPIP$NFS000000000_GID noproxy_gid TCPIP$NFS000000000_INACTIVITY vnode TCPIP$NFS000000000_SECURITY noproxy_enabled TCPIP$NFS000000000_THREADS tcp_threads TCPIP$NFS000000000_XID No equivalent TCPIP$CFS_KEEP_ALLOC___________No_equivalent_______________ 1.2.3.1 Using NFSSTAT to Display Statistical Information You can display NFS and RPC statistical information using either the SHOW NFS_SERVER command or the UNIX utility NFSSTAT. In order to use the NFSSTAT foriegn command, be sure to run the SYS$MANAGER:TCPIP$DEFINE_COMMANDS.COM procedure. For information about using NFSSTAT, enter the following TCP/IP management command: TCPIP>HELP NFSSTAT The following table lists the SHOW NFS_SERVER qualifiers and equivalent NFSSTAT flags you can use to display statistical information about NFS and RPC connections: Table_1-1_Displaying_Statistical_Information_with_NFSSTAT________ SHOW NFS_SERVER Qualifier________Meaning______________NFSSTAT_Flag_______________ /CONTINUOUS=n Specifies the nfsstat -i interval interval (in seconds) for updating the statistics on display. (continued on next page) New Features and Changes 1-37 New Features and Changes 1.2 Version 5.1 Changes Table_1-1_(Cont.)_Displaying_Statistical_Information_with_NFSSTAT SHOW NFS_SERVER Qualifier________Meaning______________NFSSTAT_Flag_______________ /RPC Displays nfsstat -r information about RPC only. /SERVER Displays nfsstat -s information about NFS and RPC. /VERSION=(V2|V3) Displays version- For Version 2 only: nfsstat specific NFS -2 statistics. You For Version 3 only: nfsstat can include either -3 or both arguments. For example: /VERSION=(V2,V3) The default is to show statistics for _________________both_versions.__________________________________ To reset the statistics to zero, use the ZERO NFS_SERVER command, or the following NFSSTAT command: $ NFSSTAT -z 1.2.3.2 Using SYSCONFIG to Modify NFS Server Attributes You can modify NFS server attributes using either the TCP/IP management command SET NFS_SERVER, or the UNIX utility SYSCONFIG. In order to use the SYSCONFIG foreign command, be sure to run the TCPIP$DEFINE_COMMANDS.COM procedure. For information about using SYSCONFIG, enter the following TCP/IP management command: TCPIP>HELP SYSCONFIG The following table lists the NFS server attributes that you can modify using the SYSCONFIG command. This table explains the purpose of the attribute and shows the qualifier to the SET NFS_SERVER command that performs the equivalent function. 1-38 New Features and Changes New Features and Changes 1.2 Version 5.1 Changes Table_1-2_Modifying_NFS_Server_Attributes_with_SYSCONFIG_________ Attribute________Description__________SET_NFS_SERVER_Qualifier___ noproxy_enabled Enables the use No equivalent. of the noproxy_uid and noproxy_gid attributes. If this attribute is not set to 1, proxies are required for server access. If the value is 0, files owned by a user that 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 database are reported to be owned by the values of the noproxy_uid and noproxy_gid attributes. noproxy_uid Specifies the SET NFS_SERVER/UID_DEFAULT default UID when a user cannot be translated by the proxy. noproxy_gid Specifies the SET NFS_SERVER/GID_DEFAULT default GID when a user cannot be translated by the proxy. (continued on next page) New Features and Changes 1-39 New Features and Changes 1.2 Version 5.1 Changes Table_1-2_(Cont.)_Modifying_NFS_Server_Attributes_with_SYSCONFIG_ Attribute________Description__________SET_NFS_SERVER_Qualifier___ tcp_threads Specifies the No equivalent. number of concurrent TCP threads within the server. udp_threads Specifies the SET NFS_SERVER/THREADS number of concurrent UDP threads within the server. Do not set this attribute to zero. A value of zero will disable the UDP protocol. vnode_age Specifies the SET NFS_SERVER/INACTIVITY_ 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 reduce _________________performance.____________________________________ 1-40 New Features and Changes New Features and Changes 1.2 Version 5.1 Changes 1.2.3.3 Using SYSCONFIG to Display Parameter Settings To display NFS parameter settings, use the following SYSCONFIG command: $ SYSCONFIG -q nfs To display VFS parameter settings, such as vnode_age, enter the following command: $ SYSCONFIG -q vfs ________________________ Note ________________________ UNIX network commands have been ported to OpenVMS and do not return the same status codes as they do on UNIX. Therefore, you should not write functions or procedures that rely on the UNIX status codes as the result of UNIX network commands entered on the OpenVMS system. ______________________________________________________ For more information about using SYSCONFIG to modify NFS server attributes, refer to the Compaq TCP/IP Services for OpenVMS Management guide. 1.2.4 TCP/IP Process Names The process names created when services are started have been enhanced to include a reference number. Therefore, when you list the system processes using the SHOW SYSTEM command, the TCP/IP Services processes will have names that include a number that indicates the number of processes that have been started for each process. For example: New Features and Changes 1-41 New Features and Changes 1.2 Version 5.1 Changes $ SHOW SYSTEM OpenVMS V7.2-1 on node OVMS 31-AUG-2000 17:33:19.75 Uptime 0 00:22:13 Pid Process Name State Pri I/O CPU Page flts Pages 53200081 SWAPPER HIB 16 0 0 00:00:03.12 0 0 . . . 5FA0021C TCPIP$BIND_1 LEF 9 362953 0 00:01:02.84 504 381 N 5FA0021D TCPIP$PORTM_1 LEF 10 878 0 00:00:00.30 300 284 N 5FA0021E TCPIP$FTP_1 LEF 10 1317 0 00:00:00.31 700 270 N . . . 5FA00223 TCPIP$LPD_QUEUE HIB 4 49 0 00:00:00.10 263 130 5FA00224 TCPIP$METRIC_1 LEF 10 144 0 00:00:18.23 285 208 N 5FA00225 TCPIP$NFS_1 HIB 10 147 0 00:00:00.11 397 247 N 5FA00226 TCPIP$MOUNTD_1 LEF 10 1113 0 00:00:00.80 531 381 N 5FA00227 TCPIP$NTP_1 LEF 9 254946 0 00:00:41.21 355 270 N 5FA00228 TCPIP$PCNFSD_1 LEF 10 162 0 00:00:00.16 343 208 N 5FA00229 TCPIP$POP_1 HIB 10 41260 0 00:00:15.32 719 519 N . . . If you have commmand procedures that reference process names, be sure to modify them appropriately. 1.2.5 FTP Changes The following sections describe changes to the FTP utility since the last release of TCP/IP Services. 1.2.5.1 FTP Passive Mode This release provides the new FTP client commands SET PASSIVE, SHOW PASSIVE, and the UNIX command passive. Passive mode is useful in cases where a firewall prevents the FTP server from establishing an outbound data connection. The value of the new passive parameter has been added to the output from the SHOW STATUS and status commands. See FTP> HELP SET PASSIVE for details. 1.2.5.2 FTP Message Enhancement The information returned by the FTP STATUS command has been improved. When you use the STATUS command, the message reporting the handling of uppercase and lowercase characters in the file name provides more information. For example, see the line starting with "Case:" below: 1-42 New Features and Changes New Features and Changes 1.2 Version 5.1 Changes $ FTP Error level is WARNING FTP> STATUS Local client's status: No connected VMS Plus mode disabled Mode = stream, Type = ascii, Form = non_print, Structure = file Error level is WARNING Reply display is on Parsing is on Prompting is off Port command is on Case: MPUT will preserve typographical case in destination filenames, if possible FTP> 1.2.6 POP Server Threads Configuration The maximum number of threads that a single POP server can process is now configurable. To configure it, define the system logical TCPIP$POP_MAXIMUM_THREADS and specify the value as the maximum number of threads you want the POP server to handle. The minimum value is 1, which turns the POP server into a single-threaded server with each new POP connection creating a new server process. The maximum value is 15. If the logical is not defined, the default is 15. This logical may be used to solve resource problems. 1.2.7 LPD Changes The following changes affect the way the LPD works: o LPD startup and shutdown The DCL commands to start and stop LPD remote queue definitions entered in the TCPIP$LPRSETUP.EXE program are no longer appended to the TCPIP$LPD_STARTUP.COM and TCPIP$LPD_SHUTDOWN.COM command procedures. With this release, the DCL commands are included in the TCPIP$LPD_ SYSTARTUP.COM and TCPIP$LPD_SYSHUTDOWN.COM command procedures. This resolves the problem with retaining the DCL commands for queue startup and shutdown when you upgrade TCP/IP Services. The TCPIP$LPD_SYSTARTUP.COM New Features and Changes 1-43 New Features and Changes 1.2 Version 5.1 Changes and TCPIP$LPD_SYSHUTDOWN.COM procedures are not replaced when you install TCP/IP Services. Note that you must manually save and edit the procedures one more time to save the queue startup and shutdown commands. Save the DCL commands from the TCPIP$LPD_ STARTUP.COM procedure to the TCPIP$LPD_SYSTARTUP.COM procedure, and save the DCL commands from the TCPIP$LPD_ SHUTDOWN.COM procedure to the TCPIP$LPD_SYSHUTDOWN.COM procedure. After this, the DCL commands to start up and shut down the queues will be preserved. o User name appears on the flag page With this release, when an inbound print job is printed under the LPD account (TCPIP$LPD), the user name that appears on the flag page and in the display from the SHOW ENTRY command is the remote user name under which the print job was submitted. 1.2.8 NTP Changes The following lists some of the changes in NTP for this version of TCP/IP Services: o NTP has been updated to support automatic Daylight Savings Time (DST) adjustments when this feature is provided by the OpenVMS operating system. o NTP logging can be controlled with a logical name. To set the logging level, define the following logical name with a value from 1 to 6, where 6 indicates the most amount of debugging information available: TCPIP$NTP_LOG_LEVEL o NTP now has dynamic auto-detection for the existence of the DTSS time service on your system. If DTSS is enabled at NTP startup time, or if DTSS is enabled while NTP is already running, NTP will not make adjustments to the system clock. Clock adjustements will resume if DTSS is disabled. NTP will continue to be able to service client requests and hand out timestamps even when disabled from making clock adjustments. You no longer need to disable NTP from setting the clock in the TCPIP$NTP.CONF configuration file. 1-44 New Features and Changes New Features and Changes 1.2 Version 5.1 Changes o The implementation of NTP included with this release has enhanced messages, as follows: o A new message has been added. The new message is output to the log file every hour. It contains basic information about the operation of NTP, including the time offset, the intrinsic clock frequency error (the drift), and the polling interval. An example of the new message is as follows: 28 Jan 14:00:48 offset: 0.012843 sec freq: -3.186 ppm poll: 64 sec o Additional information is displayed if you try to run the TCPIP$NTPDATE utility when NTP is already running. For example: $ NTPDATE:==$TCIPIP$NTPDATE $ NTPDATE FRED Socket bind error. Verify that the NTP server (TCPIP$NTP) is not running on this host. %SYSTEM-F-DUPLNAM, duplicate name In addition to these messages, the NTP log file name has been changed. The NTP messages are now logged to the following file: TCPIP$NTP_RUN.LOG 1.2.9 DHCP Changes If you use DHCP under previous versions of TCP/IP Services, please be aware of the following changes in the current release: o Change to handling of the DHCP log file When the DHCP server starts, it creates the log file TCPIP$DHCP_RUN.LOG file. This log file is used during the beginning of the DHCP server initialization process. By default, the same file name is also used for new log files created as the DHCP server runs. You can specify a different file name for log files created while DHCP is running. To specify the log file name, define the following logical: $ DEFINE /SYSTEM TCPIP$DHCP_LOG "file name" New Features and Changes 1-45 New Features and Changes 1.2 Version 5.1 Changes When you define the TCPIP$DHCP_LOG logical, DHCP will always generate two log files: TCPIP$DHCP_RUN.LOG, which includes messages from initialization, and the file you specified, which includes messages from DHCP operation. If the DHCP server is running on multiple nodes in an OpenVMS cluster where the nodes share the same system disk (SYS$SYSDEVICE), and the TCPIP$DHCP_LOG logical is not defined, it can be difficult to determine which version of the TCPIP$DHCP_RUN.LOG file is associated with each node. To find out which node generated it, you must open the file itself. You can use the TCPIP$DHCP_LOG logical to resolve this problem. For example: $ DEFINE /SYSTEM TCPIP$DHCP_LOG - $_"TCPIP$DHCP_SERVER_''F$GETSYI("NODENAME")'.LOG" If you define the logical this way, the resulting log file names reflect the node names from which they were generated. For example, node MOE generates the log file TCPIP$DHCP_SERVER_MOE.LOG. o Changes in DHCP binary databases require rollover There have been changes in the internal format of the DHCP binary database files, which are the files that look like DB%.HSH and DB%.BTR. A database rollover must be performed in order for these files to be used by the TCP/IP Services V5.1 DHCP server. The rollover is run for you automatically when you run TCPIP$CONFIG if you have DHCP configured as an enabled service. The rollover creates a "flag file" to indicate that the rollover has been done and that the files in the directory are in V5.1 format. The file is named TCPIP$DHCP_V50_V51_DBROLL.FLG and resides in the TCPIP$DHCP_CONFIG directory, if you use that logical, or in the DHCP account's default directory (SYS$SYSDEVICE:[TCPIP$DHCP]) otherwise. Do not delete it. The DHCP server startup procedure will not allow DHCP server to start if the file is not there. 1-46 New Features and Changes New Features and Changes 1.2 Version 5.1 Changes You may have formerly used the DHCP server but have it turned off. If you run TCPIP$CONFIG to turn the DHCP server back on, the rollover procedure will ask you if you want to rollover the existing database files or 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 Since the servers use different database formats you may not run the V5.0 DHCP server against the same set of files as the V5.1 DHCP server. If you are using multiple nodes in your cluster as DHCP servers they must all run the same version of TCP/IP Services. o SERVER.PCY supports new fields The V5.1 DHCP server supports some new fields in the SERVER.PCY file. A new SERVER.PCY template file in SYS$LIBRARY:TCPIP$TEMPLATES.TLB contains comments to describe the new fields. It also contains advice on which fields to set for dynamic DNS updates. You can extract the new SERVER.PCY template file and merge your existing SERVER.PCY file into it. To extract it, enter the following command: $ LIBRARY/EXTRACT=SERVER_PCY SYS$LIBRARY:TCPIP$TEMPLATES.TLB- _$/OUT=SERVER.PCY If you do not extract the new SERVER.PCY file, the DHCP server will continue to function as it always has, with backwards compatability. Some of the comments in the file will be obsolete. 1.2.10 BIND Changes If you are using the BIND server and BIND resolver, be aware of the following changes under TCP/IP Services V5.1. 1.2.10.1 Editable Network Services Database This version of TCP/IP Services provides an editable text version of the network services database, TCPIP$ETC:SERVICES.DAT. This database has the same format as the UNIX /etc/services file. When you configure the BIND resolver using TCPIP$CONFIG.COM, the template file TCPIP$ETC:SERVICES.DAT is created. New Features and Changes 1-47 New Features and Changes 1.2 Version 5.1 Changes To support use of the TCPIP$ETC:SERVICES.DAT file, the following routines are defined in the DECC RTL: o struct servent *getservbyname( char *name, char *proto ); o struct servent *getservbyport( int port, char*proto ); o struct servent *getservent( void ); o void setservent( int stay_open ); o void endservent( void ); The getservbyname() and getservbyport() functions search the traditional (RMS indexed) service database first. If the requested service is not found there, TCPIP$ETC:SERVICES.DAT is searched before returning an error to the calling application program. ________________________ Note ________________________ The TCPIP management commands SET SERVICE and SHOW SERVICE do not operate on this file and will only affect the traditional (RMS indexed) service database. ______________________________________________________ If you are using WKS records in your BIND domain database and also have dynamic updates enabled, the WKS record may get truncated when the database file is automatically written to disk by the BIND server. In order to avoid this, you should define the specified service(s) in TCPIP$ETC:SERVICES.DAT. For example, if your WKS record appears like this: wkstest IN WKS 1.2.3.4 tcp ( telnet smtp ) It would get truncated to the following when the database is written to disk: wkstest IN WKS 1.2.3.4 tcp In this case, add the following entries to TCPIP$ETC:TCPIP$SERVICES.DAT: 1-48 New Features and Changes New Features and Changes 1.2 Version 5.1 Changes telnet 23/tcp [telnet_alias] smtp 25/tcp [mail_alias] ________________________ Note ________________________ TELNET aliases are optional. ______________________________________________________ 1.2.10.2 BIND Server Merges Dynamic Updates Automatically The default behaviour of not merging (writing to disk) dynamic updates has been changed. Before this release, a user would have to define the logical TCPIP$BIND_SERVER_ MERGE_DYNAMIC_UPDATES to have dynamic updates merged into the domain.DB file on an hourly basis. Now this action will be performed by default. To disable this behaviour, define the following logical: TCPIP$BIND_DONT_MERGE_DYNAMIC_UPDATES 1.2.11 SMTP Changes This release includes the following changes to the SMTP: o Specifying IP address for alternate gateway The SMTP alternate gateway now accepts an IP address for the configured alternate gateway. This command is specified as follows: TCPIP> SET CONFIG SMTP/GATE=ALT=IP-address Where IP-address is the IP address of the configured alternate gateway. This syntax is handled differently than if you specify a host name. If you specify a host name, SMTP performs a MX record lookup to resolve it. If you specify an IP address, however, no MX record lookup is performed. The address is used literally and SMTP connects to the specified address each time mail needs to be routed through the alternate gateway. o Comment text in To: header This release supports preserving comment text in the To: header. By default, when SMTP composes a mail message, it strips off any comments you may enter into the recipient address. This is a problem for users that depend on commands in the To: line. New Features and Changes 1-49 New Features and Changes 1.2 Version 5.1 Changes This release allows the user to tell SMTP to use the text of the recipient address in the To: header rather than stripping off the comments, which is the default behavior. To turn on the feature, the user defines the TCPIP$SMTP_ USE_VERBATIM_TO logical. Set the logical to either 1 (on) or 0 (off). Compaq recommends that this logical be defined for the specific process, not system-wide. For example: $ DEFINE TCPIP$SMTP_USE_VERBATIM_TO 1 After the logical is defined, you can send an OpenVMS mail message as follows: $ MAIL Z.Z/SUB=TEST - $_SMTP%"""/name=karen/fax=95924121/""" Because the logical is defined, the following To: header is applied to the mail message: To: /name=karen/fax=95924121/ If the logical is not defined, the SMTP server applies the following To: header: To: default@warpig.cxo.dec.com ________________________ Note ________________________ Be aware of the following limitations and restrictions in using this feature: o The address you enter must comply with RFC 822 specifications for a To: recipient address. o This change does not affect the address used in the SMTP dialog RCPT TO command. It affects the RFC 822 To: header in the message itself. The RCPT TO address will be the address, fully qualified and stripped of comments. o This feature should be used with caution, because the To: header becomes what you enter. If you enter an unqualified address the To: header will be unqualified, which may not be what you expect and might cause unexpected results. 1-50 New Features and Changes New Features and Changes 1.2 Version 5.1 Changes o Use three double quotes after the SMTP% jacket as in the example above to preserve case if there is a need to. ______________________________________________________ o Quotation marks in the OpenVMS Mail personal name This release supports the use of double quotes ("name") in the OpenVMS personal name. If the SMTP mailer encounters double quotes in the personal name, it changes them to single quotes ('name'). 1.2.12 Message Improvements The following changes reflect improvements in the messages you receive from TCP/IP Services: o Applications started before TCP/IP Services display "Network is down" message. In previous versions of TCP/IP Services, if the software had not been started when users attempt to start applications like TELNET, FTP, and RLOGIN, the Host not available message was displayed. This message was misleading and did not provide sufficient information for understanding the problem that prevented the application from starting. With the current version of TCP/IP Services, when applications are started before the TCP/IP Services software has been started, the following message is displayed: TCPIP$_NOINET, Network is down The following socket routines have been changed: o accept() o gethostbyaddr() o gethostbyname() o select() o socket() These routines now set ERRNO to ENETDOWN, indicating that the TCP/IP Services software has not been started. New Features and Changes 1-51 New Features and Changes 1.2 Version 5.1 Changes For compatability with existing code, the socket routines must set ERRNO to a value less than __ERRNO_ MAX. Setting VAXC$ERRNO to the TCPIP$_NOINET value used by applications would cause ERRNO to be set to EVMSERR, which falls outside the required range and breaks code ported from UNIX. o The TELNET client returns a secondary error code for INVHOST. If the TELNET client fails because of an invalid host (INVHOST) error, a second message is displayed that provides more information. The additional information can help you determine the actual problem that caused the error. For example: $ TELNET JUNK %TELNET-E-IVHOST, Invalid or unknown host junk -TCPIP-E-HOST_NOT_FOUND, no such host is known $ This example shows the secondary message ("no such host is known"), which indicates that the problem is in the host name entered on the command line, rather than a temporary failure in network service. o The TCPIP$STARTUP.COM procedure now issues the following timing messages: %TCPIP-I-INFO, TCP/IP Services startup beginning at 18-MAY-1999 18:39:10.40 %TCPIP-S-STARTDONE, TCP/IP Services startup completed at 18-MAY-1999 18:39:10:48 In addition, the following message is displayed if SYS$STARTUP:TCPIP$SYSTARTUP.COM is about to be executed: %TCPIP-I-INFO, executing site-specific startup SYS$STARTUP:TCPIP$SYSTARTUP.COM These messages help you determine whether problems in system startup are happening in TCPIP$STARTUP.COM or not. 1.2.13 Adjusting Interrupt Stack Pages on VAX Systems This version of TCP/IP Services requires you to increase the value of the SYSGEN parameter INTSTKPAGES to at least 12 before starting the network on VAX systems. 1-52 New Features and Changes New Features and Changes 1.2 Version 5.1 Changes 1.2.14 TELNET Changes The display from the TELNET command SHOW DEVICE has been changed to reflect the size of the address string for IPv6 and full host names. The default display from the SHOW DEVICE command now includes two lines of information for each device. For example: TELNET>SHOW DEVICE TNA21: BG6364: Temporary Local: hosta:23 Remote: mynode.abc.com:1024 TNA83: BG5014: Temporary Local: hosta:23 Remote: myalpha.abc.com:1079 TNA88: Temporary Local: (none) Remote: (none) 1.2.15 Programming Example Changes The example programs supplied with TCP/IP Services have been enhanced and updated. The programming example files are installed in the directory pointed to by the TCPIP$EXAMPLES logical name. For information about using the programming examples provided with TCP/IP Services, refer to the Compaq TCP/IP Services for OpenVMS Sockets API and System Services Programming guide. 1.2.16 SHOW DEVICE Command Changes In this release, the behavior of the TCP/IP management command SHOW DEVICE has changed. In previous releases of TCP/IP Services, the software always attempts to resolve internet addresses using the local hosts database. To resolve addresses not in the hosts database, you include the /NOLOCAL qualifier to the SHOW DEVICE command. With the current release, the SHOW DEVICE command does not attempt to resolve addresses using the hosts database. The /NOLOCAL qualifier can be used to control both local and remote host name resolution. New Features and Changes 1-53 New Features and Changes 1.2 Version 5.1 Changes 1.2.17 Server Inactivity Timer Is Not Enforced TCP/IP Services no longer enforces an inactivity timer for processes created by the INETACP. This means that once a process is created for a server, the server will endure until that service is shut down. Improvements in the OpenVMS operating system have altered the cost/benefit ratio of enduring servers so that they should be preferred. Enduring servers allow for more predictable and faster responses to connection requests at a very low cost in system resources. The TCP/IP management command SHOW SERVICE /FULL shows an entry for the Inactivity field. However, that value has no effect. The FTP service is a good example of the changed behavior. Some system managers have arranged for processes like the FTP server (TCPIP$FTP_SERVER) to exit after the value specified in the FTP service inactivity field. The FTP server process is created when the FTP service is enabled (typically at system boot). It endures until the FTP service is disabled (typically at system reboot). Other services handle the creation and maintenance of the server process in a similar manner. The FTP server process itself checks the logical name TCPIP$FTPD_IDLETIMEOUT and uses that value, or the default setting, to cause the processes that perform the actual FTP transfers (TCPIP$FTP_CHILD processes) to expire. 1.3 Version 5.1 Documentation The TCP/IP Services for OpenVMS documentation has been revised and expanded to support Version 5.1. The following manuals have been added to the documentation set: o Compaq TCP/IP Services for OpenVMS Tuning and Troubleshooting This new manual provides system and network managers with information they need to identify and resolve problems. Use this guide to solve general networking software problems. For problems restricted to specific TCP/IP services, refer to the appropriate chapter in the Compaq TCP/IP Services for OpenVMS Management guide. o Compaq TCP/IP Services for OpenVMS Guide to IPv6 1-54 New Features and Changes New Features and Changes 1.3 Version 5.1 Documentation This new manual describes the IPv6 environment, the roles of systems in this environment, the types and function of the different IPv6 addresses, and how to connect to the 6bone network. Several existing manuals have been revised to reflect this version of TCP/IP Services, including: o Compaq TCP/IP Services for OpenVMS Installation and Configuration o Compaq TCP/IP Services for OpenVMS Management o Compaq TCP/IP Services for OpenVMS Management Command Reference o Compaq TCP/IP Services for OpenVMS Sockets API and System Services Programming o Compaq TCP/IP Services for OpenVMS SNMP Programming and Reference These manuals are provided as part of the field test of the TCP/IP Services software. Information presented in these manuals is confidential and subject to the terms and conditions of the field test. New Features and Changes 1-55 2 _________________________________________________________________ Installation, Configuration, and Startup Notes Use this chapter in conjunction with the Compaq TCP/IP Services for OpenVMS Installation and Configuration manual. 2.1 Configuring IPv6 The following sections describe procedures specific to systems where IPv6 is to be enabled. 2.1.1 Information for Users of the IPv6 EAK The TCP/IP Services external field test (EFT) kit is intended to replace the TCP/IP Services V5.0 and V5.0A software. If you are running any version of the TCP/IP Services V5.0 IPv6 EAK (early adopter's kit), remove the EAK and then install the TCP/IP Services V5.1 software. You must then run the TCPIP$IP6_SETUP.COM command procedure. Refer to the Compaq TCP/IP Services for OpenVMS Guide to IPv6 for more information. There has been a change in the definition of a sockaddr structure, which breaks binary compatibility for IPv6 applications that were compiled using the TCP/IP Services V5.0 EAK. You must recompile and relink your applications after installing TCP/IP Services V5.1. 2.1.2 Warning Message in TCPIP$CONFIG.COM If you have run the TCPIP$IP6_SETUP.COM procedure to enable IPv6, then you run the TCPIP$CONFIG.COM command procedure, TCPIP$CONFIG.COM displays the following warning message when you select the Core environment option: Installation, Configuration, and Startup Notes 2-1 Installation, Configuration, and Startup Notes 2.1 Configuring IPv6 WARNING This node has been configured for IPv6. If you make any additional changes to the configuration of the interfaces, you must run TCPIP$IP6_SETUP again and update your host name information in BIND/DNS for the changes to take effect. 2.2 Removing Prior Versions of this Product This section provides important information you should review before installing the TCP/IP Services Version 5.1 software. 2.2.1 Saving Mail Messages When You Upgrade The new version of SMTP includes control files that are different from previous versions. Before upgrading to this version of TCP/IP Services, run the ANALYZE utility to pick up any dead letters on your system, as follows: $ ANALYZE MAIL/REPAIR 2.2.2 Upgrading OpenVMS VAX Systems The command procedure SYS$UPDATE:UCX$CLEANUP.COM is typically used to clean up a previous version of the TCP/IP Services product. However, running this procedure when TCP/IP Services Version 5.1 is installed will remove files necessary for the operation of the product. _______________________ Caution _______________________ Do not run UCX$CLEANUP after installing the TCP/IP Services Version 5.1 product on an OpenVMS VAX system. If you run this command procedure, it will corrupt your TCP/IP Services Version 5.1 installation. ______________________________________________________ Compaq strongly recommends you remove this command procedure after installing the TCP/IP Services Version 5.1 kit. 2-2 Installation, Configuration, and Startup Notes Installation, Configuration, and Startup Notes 2.3 System Page Table Entries Parameter (VAX Systems Only) 2.3 System Page Table Entries Parameter (VAX Systems Only) On VAX systems, make sure the AUTOGEN parameter SPTREQ is set to at least 6000. Run SYSMAN to check the minimum SPTREQ value as follows: $ RUN SYS$SYSTEM:SYSMAN SYSMAN> parameter show sptreq %SYSMAN, a USE ACTIVE has been defaulted on node VMSVAX Node VMSVAX: Parameters in use: ACTIVE Parameter Name Current Default Minimum Maximum Unit Dynamic -------------- ------- ------- ------- ------- ---- ------- SPTREQ 8000 3900 3000 -1 Pages SYSMAN> To modify the minimum SPTREQ, run the AUTOGEN command procedure as described in the OpenVMS System Management Utilities Reference Manual: A-L. Modify the minimum SPTREQ value as follows: MIN_SPTREQ = 6000 2.4 Some UCX Files Remain After Installation After installing and starting the TCP/IP Services Version 5.1 product, you may notice some files with a UCX$ prefix (most other files provided by this product use the prefix TCPIP$). The existence of these files (see Table 2-1) is normal and expected. They are required to maintain backward compatibility with previous versions of TCP/IP Services. Table_2-1_UCX_Files_Remaining_After_Installation_________________ File____________________________Description______________________ SYS$LIBRARY:UCX$IPC_SHR.EXE Allows the DEC C Run-Time Library (RTL) to use TCP/IP sockets. (continued on next page) Installation, Configuration, and Startup Notes 2-3 Installation, Configuration, and Startup Notes 2.4 Some UCX Files Remain After Installation Table_2-1_(Cont.)_UCX_Files_Remaining_After_Installation_________ File____________________________Description______________________ SYS$LIBRARY:UCX$INETDEF.ADA The INETDEF files are shipped for compatibility with applications developed under TCP/IP Services Version 4.2. These files are identical to the files shipped with Version 4.2 SYS$LIBRARY:UCX$INETDEF.BAS SYS$LIBRARY:UCX$INETDEF.FOR SYS$LIBRARY:UCX$INETDEF.H SYS$LIBRARY:UCX$INETDEF.MAR SYS$LIBRARY:UCX$INETDEF.PAS SYS$LIBRARY:UCX$INETDEF.PLI SYS$LIBRARY:UCX$INETDEF.R32 SYS$COMMON:[SYSEXE]UCX$UCP.EXE An empty (zero block) marker file which allows some layered products which use an unsupported test for the presence of the TCP/IP Services to continue to operate. SYS$COMMON:[SYSEXE]UCX$SERVICE.DAT An empty (zero block) marker file may be created if the file does not exist when TCPIP$STARTUP.COM executes. The file speci- fied by the logical name TCPIP$SERVICE (which defaults to SYS$COMMON:[SYSEXE]TCPIP$SERVICE.DAT) contains the actual service information. (continued on next page) 2-4 Installation, Configuration, and Startup Notes Installation, Configuration, and Startup Notes 2.4 Some UCX Files Remain After Installation Table_2-1_(Cont.)_UCX_Files_Remaining_After_Installation_________ File____________________________Description______________________ SYS$STARTUP:UCX$STARTUP.COM These files print an SYS$STARTUP:UCX$CONFIG.COM informational message to SYS$OUTPUT, then execute the corresponding TCPIP file. This allows the TCP/IP Services product to continue to operate until the system manager changes command files to use the new TCPIP prefix. SYS$SYSTEM:UCX$LPD_SMB.EXE Maintains backward compatibility for LPD print queue. SYS$SHARE:UCX$ESNMP_SHR.EXE Shareable images required for SYS$SHARE:UCX$ACCESS_SHR.EXE user-written programs written SYS$SHARE:UCX$RPCXDR_SHR.EXE under previous versions of the product. SYS$COMMON:[SYSEXE]UCX$TELNETSYM.EXE TELNET print symbiont executable. This file is identical to ________________________________TCPIP$TELNETSYM.EXE._____________ 2.5 Starting the Product After a Minimum OpenVMS Boot If you boot OpenVMS with the SYSGEN parameter STARTUP_P1 defined to something other than the default blank string, not all portions of OpenVMS may be started. A check has been added to the TCP/IP Services startup procedure SYS$STARTUP:TCPIP$STARTUP.COM to detect when OpenVMS has been booted in an alternate manner. If the startup procedure SYS$STARTUP:TCPIP$STARTUP.COM detects a MIN, INST, or UPGRADE boot, it displays a message and exits, setting $SEVERITY to ERROR. For example, the following message is displayed if a MIN boot is detected. %TCPIP-E-STARTFAIL, failed to start TCP/IP Services -TCPIP-E-UNSUPPORTED, option boot not supported Where option represents the type of installation you started (MIN, INST, or UPGRADE). Installation, Configuration, and Startup Notes 2-5 Installation, Configuration, and Startup Notes 2.5 Starting the Product After a Minimum OpenVMS Boot This check helps ensure that conditions required for proper operation of TCP/IP Services are met. For example, if OpenVMS and TCP/IP Services are installed from a CD-ROM or a server, and OpenVMS is booted from the same medium, the boot type will be INST. The TCP/IP startup procedure will fail in this case, because TCPIP$CONFIG cannot write configuration files to the SYS$SYSTEM: area on a CD-ROM or server disk. 2.6 Preserving LPD Startup and Shutdown Behavior Your LPD startup and shutdown command procedures may contain site-specific edits. You must manually preserve these edits when upgrading to TCP/IP Services Version 5.1 from a previous version. The procedure for preserving your edits differs for OpenVMS Alpha systems and OpenVMS VAX systems. Follow the instructions below to preserve your site-specific startup and shutdown command procedure files. 2.6.1 OpenVMS Alpha Users When you install TCP/IP Services Version 5.1 over an earlier version of the product, follow the instructions displayed on your screen to preserve your edits in the LPD startup and shutdown command procedures. The following shows a sample screen display. The following product will be installed to destination: DEC AXPVMS TCPIP V5.1-9 DISK$ALPHASYS:[VMS$COMMON.] UCX product already installed. *********************************************************************** 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; - SYS$COMMON:[SYSMGR]TCPIP$LPD_STARTUP.COM; $ BACKUP SYS$COMMON:[SYSMGR]UCX$LPD_SHUTDOWN.COM; - SYS$COMMON:[SYSMGR]TCPIP$LPD_SHUTDOWN.COM; $ PRODUCT REMOVE UCX *********************************************************************** 2-6 Installation, Configuration, and Startup Notes Installation, Configuration, and Startup Notes 2.6 Preserving LPD Startup and Shutdown Behavior After following these instructions, and completing the 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 Now merge your site-specific edits into: SYS$COMMON:[SYSMGR]TCPIP$LPD_SYSTARTUP.COM SYS$COMMON:[SYSMGR]TCPIP$LPD_SYSHUTDOWN.COM 2.6.2 OpenVMS VAX Users To preserve your site-specific startup and shutdown information, you must install TCP/IP Services Version 5.1, then copy the site-specific edits from: SYS$COMMON:[SYSMGR]UCX$LPD_STARTUP.COM SYS$COMMON:[SYSMGR]UCX$LPD_SHUTDOWN.COM to the following files: SYS$COMMON:[SYSMGR]TCPIP$LPD_STARTUP.COM SYS$COMMON:[SYSMGR]TCPIP$LPD_SHUTDOWN.COM 2.6.3 Troubleshooting SMTP and LPD Shutdown Problems If SMTP or LPD shutdown generates errors indicating that the queue manager is not running, check your site-specific shutdown command procedure (VMS_SYSHUTDOWN.COM). If this procedure contains the command to stop the queue manager (STOP/QUEUE/MANAGER), make sure this command comes after any invokation of the TCPIP$SHUTDOWN.COM procedure. ________________________ 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. ______________________________________________________ Installation, Configuration, and Startup Notes 2-7 Installation, Configuration, and Startup Notes 2.6 Preserving LPD Startup and Shutdown Behavior 2.6.4 Merging Edits (All Users) When merging edits, do not append the commands to start and stop the queue UCX$LPD_QUEUE. This queue has been replaced with TCPIP$LPD_QUEUE, and the commands for TCPIP$LPD_QUEUE will already be in the LPD startup and shutdown command procedure files. After merging the edits, set the value of the /PROCESSOR qualifier in the LPD client queue startup commands that you have just appended to point to TCPIP$LPD_SMB rather than UCX$LPD_SMB. LSE Command> SUBSTITUTE/ALL "ucx$lpd_smb" "tcpip$lpd_smb" 2.7 SNMP Installation and Setup The following sections describe procedures for installing and setting up SNMP. 2.7.1 Verifying the SNMP Installation A separate installation verification procedure (IVP) exists for SNMP. To verify your configuration, complete these steps: 1. Be sure that your process has SYSTEM privileges. 2. Run the command procedure: $ @SYS$MANAGER:TCPIP$CONFIG 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 the configuration procedure, use the following command: $ RUN SYS$COMMON:[SYSTEST.TCPIP]TCPIP$SNMPIVP.EXE 2.7.2 Preserving SNMP Startup and Shutdown Behavior After you upgrade to TCP/IP Services Version 5.1, you must perform one of the following actions to ensure correct SNMP startup: o If SNMP had been configured under a previous TCP/IP Services installation (UCX) and you want to retain the previous configuration, run SYS$MANAGER:TCPIP$CONFIG.COM 2-8 Installation, Configuration, and Startup Notes Installation, Configuration, and Startup Notes 2.7 SNMP Installation and Setup and select the option to automatically convert UCX configuration files. o After you upgrade to this version of TCP/IP Services, run SYS$MANAGER:TCPIP$CONFIG.COM. If SNMP is still enabled, disable SNMP then enable it again. This is necessary for the proper operation of this component. If you customized versions of the files UCX$SNMP_ STARTUP.COM and UCX$SNMP_SHUTDOWN.COM (used to start and stop extension subagents), save your customized files to a different directory before upgrading to TCP/IP Services Version 5.1. If you do not perform this step, your customized changes will be lost. Check for versions of these files in the following locations: o SYS$MANAGER o SYS$STARTUP o SYS$SYSDEVICE:[UCX$SNMP] After you install TCP/IP Services, manually merge your saved changes into the new files created after installation. See the Compaq TCP/IP Services for OpenVMS Management guide for more information. 2.8 Setting Up the TCP/IP Services Message Database At installation, the TCP/IP Services message database is installed at SYS$COMMON:[SYSHLP]TCPIP.MSGHLP$DATA. To get information about TCP/IP messages, include this database with the OpenVMS message database, as follows: 1. Define the logical name MSGHLP$LIBRARY to point to all the databases in the directory: $ DEFINE/SYSTEM MSGHLP$LIBRARY SYS$COMMON:[SYSHLP]*.MSGHLP$DATA 2. Enter the DCL command HELP/MESSAGE to make sure the TCP/IP message database is now recognized. For example: $ HELP/MESSAGE FTP SESDCN, FTPD: Session disconnection from 'host' at 'time' Facility: TCPIP, FTP Server Installation, Configuration, and Startup Notes 2-9 Installation, Configuration, and Startup Notes 2.8 Setting Up the TCP/IP Services Message Database Explanation: This message appears when a session is disconnected, stating the name of the client initiating the disconnection and the time of the disconnection. User Action: None. Press RETURN to continue ... In this example, Help Message displays all the messages that contain FTP as part of the message ID. 2.9 PROXYERROR Messages at Startup If the proxy database is empty when you start up TCP/IP Services, the following error messages are displayed: %TCPIP-E-PROXYERROR, error processing proxy request -TCPIP-W-NORECORD, information not found -RMS-E-RNF, record not found %TCPIP-E-PROXYERROR, error processing proxy request -TCPIP-W-NORECORD, information not found -RMS-E-RNF, record not found These messages, also displayed if you enter the TCP/IP management command LOAD PROXY, may be ignored. 2-10 Installation, Configuration, and Startup Notes 3 _________________________________________________________________ Problems and Restrictions This chapter provides information about problems and restrictions in this version of TCP/IP Services. 3.1 NFS Problems and Restrictions The following sections describe problems and restrictions with NFS. 3.1.1 NFS Lock Requests Fail If the NFS server and the NFS client are in different domains and unqualified host names are used in requests, the lock server (LOCKD) fails to honor the request and leaves the file unlocked. When the server attempts to look up a host using its unqualified host name (for example, johnws) instead of the fully qualified host name (for example, johnws.abc com), and the host is not in the same domain as the server, the request fails. To solve this type of problem, you can do one of the following: o When you configure the NFS client, specify the fully qualified host name, including the domain name. This ensures that translation will succeed. o Add an entry to the NFS server's hosts database for the client's unqualified host name. Only that NFS server will be able to translate this host name. This solution will not work if the client obtains its address dynamically from DHCP. Problems and Restrictions 3-1 Problems and Restrictions 3.1 NFS Problems and Restrictions 3.1.2 NFS Client Problems and Restrictions To get proper timestamps, when the system time is changed for Daylight Savings Time (DST), dismount all DNFS devices. (The TCP/IP management command SHOW MOUNT should show zero mounted devices.) Then remount the devices. 3.2 DHCP Client Problems and Restrictions The TCP/IP managent command SET [NO]INTERFACE command does not tell the DHCP client to release an IP address when writing over an IP address configured by DHCP or deleting the interface. This causes the following problems: o The system has a lease on an IP address that it does not need because the interface has either been deleted or reconfigured. The leased IP address should be returned to the pool for use by another DHCP client. o The DHCP client process is not told that the interface is no longer under DHCP control. Depending on the specific SET [NO]INTERFACE command that was entered, the following may occur: - If the interface was manually reconfigured with a different IP address using the SET INTERFACE command, when the DHCP client tries to extend the lease on the IP address it will reset the interface's address to the one from DHCP. - If the interface was deleted using the SET NOINTERFACE command, when the DHCP client tries to extend the lease on the IP address, the client will incur an error and log it because it will not be able to get to the interface. To avoid these problems, when you issue any command that would change the IP address of an interface that is under DHCP control, COMPAQ suggests you first enter the following DCL command: $ DHCPCONF ifname RELEASE For more information about using the DHCPCONF utility, refer to the Compaq TCP/IP Services for OpenVMS Management guide. 3-2 Problems and Restrictions Problems and Restrictions 3.3 IPv6 Problems and Restrictions 3.3 IPv6 Problems and Restrictions The following sections describe problems that are known to exist in the IPv6-enabled environment. 3.3.1 IPv6 Proxy Lookup Communication proxies are not supported under IPv6. The client applications included with TCP/IP Services have been programmed to resolve proxy requests to IPv4 addresses. However, clients requesting IPv6 addresses will fail. 3.3.2 IPv6 Requires the BIND Resolver If you are using IPv6 as described in Section 1.1.2, you must enable the BIND resolver. If you do not have the BIND resolver configured, you can enable it using the TCPIP$CONFIG.COM procedure. From the Core menu, select BIND Resolver. If you do not have access to a BIND server, specify the node address 127.0.0.0 as your BIND server. You must specify the BIND server to enable the BIND resolver. 3.4 RLOGIN Does Not Create Virtual Terminals For a proxy login, the RLOGIN service does not create a virtual terminal. For more information, refer to the Compaq TCP/IP Services for OpenVMS Management guide. 3.5 TELNET Devices Remain After Shutdown During shutdown the following message may appear: WARNING - The following TN devices are still active: TNA8: The TN device persists until the next startup, when the same message may appear. You can safely ignore these messages. They appear because TN devices are deleted using a timer that is deactivated during the shutdown procedure. Problems and Restrictions 3-3 Problems and Restrictions 3.6 TELNETSYM Autostart Queues in OpenVMS Clusters 3.6 TELNETSYM Autostart Queues in OpenVMS Clusters Autostartable TELNETSYM queues may be restarted automatically if a member node in the cluster goes down. The queue manager attempts to start the TELNETSYM queues on all the nodes for which the queues are defined. If one of the nodes is not running TCP/IP Services, the queue manager will report a failure trying to start TELNETSYM queues on that node. 3.7 File Locking Requires Compaq C RTL ECO3 or Higher You must have ECO3 to Compaq C RTL, or a later version, in order to use file locking (described in Section 1.1.13.5). With earlier versions, the TCPIP$STATD service will not start. This problem is specific to VAX systems and to OpenVMS Alpha Version 7.1. 3.8 PRODUCT REMOVE TCPIP Error Message When you use the following command: $ PRODUCT REMOVE TCPIP You may encounter an error similar to: %PCSI-W-OPTREF, product DEC AXPVMS TCPIP T5.1-9R is referenced by DEC AXPVMS OPENVMS V7.2-1 This occurs only on systems where the TCP/IP product was installed at the same time as the Operating System. This error may be ignored, and you can continue with the removal of TCPIP. Note that this also applies to the UCX product. For example: $ PRODUCT REMOVE TCPIP The following product has been selected: DEC AXPVMS TCPIP T5.1-9R Layered Product Do you want to continue? [YES] YES 3-4 Problems and Restrictions Problems and Restrictions 3.8 PRODUCT REMOVE TCPIP Error Message %PCSI-W-OPTREF, product DEC AXPVMS TCPIP T5.1-9R is referenced by DEC AXPVMS OPE NVMS V7.2-1 -PCSI-W-OPTRF1, this software dependency is expressed within a configuration -PCSI-W-OPTRF2, option that is currently selected for the referencing product -PCSI-W-OPTRF3, if you want to reconfigure the referencing product or review -PCSI-W-OPTRF4, its configuration requirements, answer NO to the following -PCSI-W-OPTRF5, question to terminate this operation; if you are sure you want -PCSI-W-OPTRF6, to remove the referenced product, then answer YES to proceed Do you want to continue? [YES] YES The following product will be removed from destination: DEC AXPVMS TCPIP T5.1-9R DISK$ALPHASYS:[VMS$COMMON.] Portion done: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100% The following product has been removed: DEC AXPVMS TCPIP T5.1-9R Layered Product %PCSIUI-I-COMPWERR, operation completed after explicit continuation from errors 3.9 Startup DUPLNAM Messages When you start TCP/IP Services, the following DUPLNAM messages may appear: %TCPIP-S-STARTDONE, TCPIP$TELNET startup completed %TCPIP-E-DYNPROXERR, cannot add record to proxy database (TCPIP$PROXY) in dynamic memory -SYSTEM-F-DUPLNAM, duplicate name %TCPIP-E-DYNPROXERR, cannot add record to proxy database (TCPIP$PROXY) in dynamic memory -SYSTEM-F-DUPLNAM, duplicate name %TCPIP-I-LOADSERV, loading TCPIP server proxy information %TCPIP-I-SERVLOADED, auxiliary server loaded with 0 proxy records -TCPIP-I-SERVSKIP, skipped 0 communication proxy records -TCPIP-I-SERVTOTAL, total of 8 proxy records read %TCPIP-S-STARTDONE, TCP/IP Services startup completed at 7-JUN-2000 16:03:51.48 These messages can be safely ignored. They are the result of a change in the current version of TCP/IP Services. Problems and Restrictions 3-5 Problems and Restrictions 3.9 Startup DUPLNAM Messages In previous versions of TCP/IP Services, the proxy database required that all names for a particular host be entered in the hosts database. For example, the host names johnws and johnws.abc.com needed to be in the hosts database if any NFS requests were made using either of the host names. With this release of TCP/IP Services, the proxy information that is loaded includes all of a server's addresses and alias names automatically. Therefore, the first entry for a host which is loaded succeeds, and all of the subsequent matching entries which only differ in the host's alias name will generate DUPLNAM messages. Proxy records for the host under both (or more) of the host's names will succeed as it did before, because all names (including the duplicates) are indeed loaded. Note that because there is now only one record for each host, the removal of a proxy entry under any of the hosts names will remove all of the addresses and aliases for that host. Subsequent removal attempts under any of the host's other names will also return an error. 3.10 Security Driver Support for the security driver is no longer available. 3.11 Command Restrictions The following restrictions apply to the management control program commands: o In this release of TCP/IP Services, the /HOST qualifier to the SHOW DEVICE_SOCKET command does not work. o The SHOW CFS command does not work. o The INCOMING and OUTGOING arguments to the /NFS qualifier on the REMOVE PROXY command do not work. o The ROUTE FLUSH command is not supported. o There is no support for zeroing counters. In previous releases, this was accomplished with the ZERO INTERFACE /COUNTERS command. 3-6 Problems and Restrictions Problems and Restrictions 3.11 Command Restrictions If you want to see changes over a period of time, you must take a snapshot with a timestamp, wait, take another snapshot with a timestamp and compare the difference. o SET INTERFACE /CLUSTER You must set the cluster network mask and cluster broadcast masks when you define a cluster alias using the SET INTERFACE /CLUSTER command. In earlier releases, you could add or modify the network and broadcast masks after defining the alias name. o SET INTERFACE If you fail to enter all of the required parameters and qualifiers with the SET INTERFACE command, the management control program may behave in an unexpected manner. To correct any problems, exit the management control program, restart, and reenter the SET INTERFACE command. o SET NAME_SERVICE /PATH This command requires the SYSNAM privilege. If you enter the command without the appropriate privilege at the process level, the command will not work but you will not be notified. If you enter the command at the system level, the command will not work but you will receive an error message. o SET SERVICE command When you modify parameters to a service, disable and reenable the service for the modifications to take effect. o DISABLE SERVICE command For most services, this command disables the specified service but does not stop the current process if one exists. This allows you to perform an orderly shutdown of the service, preventing new connections while allowing current connections to continue. To stop and restart the current process: 1. Wait until the process exits or stop it using the service-specific shutdown command procedure (TCPIP$service_SHUTDOWN.COM). Problems and Restrictions 3-7 Problems and Restrictions 3.11 Command Restrictions 2. Restart the service using the service-specific startup command procedure (TCPIP$service_ STARTUP.COM. Note that, for the NFS server, TELNET, and RLOGIN, the DISABLE SERVICE command stops the current process. To stop DHCP, enter the dhcpsigterm command (defined in SYS$MANAGER:TCPIP$DHCP_SETUPCOMMANDS.COM). See the Compaq TCP/IP Services for OpenVMS Management guide for more information. For information about TCP/IP management commands that are not supported, refer to Section 1.2.1. 3.12 NTP Problems and Restrictions The NTP server has a stratum limit of 15. It will not synchronize to any time server that reports a stratum of 15 or greater. This may cause problems if you try to synchronize to a server running the UCX NTP server, if that server has been designated as "free-running" (with the "local-master" command). For proper operation in such a case, the "local-master" designation must be specified with a stratum no greater than 14. 3.13 Error Messages Some error messages may contain extra blank lines. $ FTP host-name %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 This section describes FTP problems and restrictions. 3.14.1 GET/FDL Command When connected to a system that is not running OpenVMS, the following command fails: FTP> GET/FDL a/b/c.d In error, FTP attempts to return the file /FDL. 3-8 Problems and Restrictions Problems and Restrictions 3.14 FTP Problems and Restrictions The workaround to this problem is to enter the command using the following sequence: FTP> cd a/b/ FTP> GET/FDL c.d 3.14.2 Extended File Specifications in a Mixed Operating System Environment With FTP, file names must be valid on the target operating system. It may help to clarify this requirement in the context of Extended File Specification names when certain characters in a file name must be escaped. For example, the file A^;b.Dat;3 requires a caret escape before the first semicolon. The transfer and display of this file name between systems running OpenVMS Version 7.2, with parse-style for the process set to EXTENDED and referencing an ODS5 disk, exhibits expected behavior. The 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 The number to the right of the ending semicolon varies depending on the version of any previously existing files of that name in the directory. When operating between an OpenVMS system and a system that is not running OpenVMS, the FTP server displays the file as A^;b.Dat.3 (.3 rather than ;3). When entering a GET command for a file A;b.Dat from a UNIX system, for example, you must specify the caret in the output specification: FTP> GET A;b.Dat A^;b.Dat The following command results in a file specification error: FTP> GET A;b.Dat When entering a PUT command, you must manually remove the caret escapes from the output specification: FTP> PUT A^;b.Dat A;b.Dat Problems and Restrictions 3-9 Problems and Restrictions 3.15 DHCP Problems and Restrictions 3.15 DHCP Problems and Restrictions 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 the SYS$SYSDEVICE:[TCPIP$DHCP]NETMASKS. file and include an entry for each network. Each entry in the file must include two fields: the network address and the netmask address. For example: # Network Netmask 192.1.1.0 255.255.255.224 192.1.1.96 255.255.255.240 o To ensure an orderly shutdown of DHCP, invoke SYS$STARTUP:TCPIP$SHUTDOWN.COM from your SYS$STARTUP:SYSHUTDOWN.COM procedure. The DHCPSIGTERM command is issued from the TCPIP$DHCP_ SHUTDOWN.COM procedure. When you shut down the system, the system shutdown procedure runs TCPIP$SHUTDOWN.COM, which in turn runs TCPIP$DHCP_SHUTDOWN.COM. This process ensure an orderly shutdown. o A synchronization problem can occur if BIND lookups are slow. Before the DHCP server assigns a name to a host, it performs a reverse lookup call (gethostbyaddr) to see if there is already a name associated with the address in BIND. If the call is slow to respond, the client's repeated requests are ignored, causing the client to change the XID and send additional requests. You can trace this behavior to the XID field, where the XID field of the client reply is different from the XID field of the previous client request. To avoid this synchronization problem, define the host and IP address in the local hosts database. Enter: TCPIP> SET HOST host/ADDRESS=IP_address o In the Server/Security tab of the DHCP GUI, the Printing parameter is not functioning. At this time, you cannot print from the GUI. 3-10 Problems and Restrictions Problems and Restrictions 3.16 PPP/SLIP Problems and Restrictions 3.16 PPP/SLIP Problems and Restrictions The following sections describe problems in the PPP and SLIP services. 3.16.1 Running PPP on OpenVMS Version 7.1 If you are running PPP on OpenVMS Version 7.1, you must have a remedial kit for the ASNDRIVER installed. Without this kit, PPP may cause a system crash. This kit includes the ASNDRIVER and other fixes. Please see the kit's cover letter for more details. You can access the kit and cover letter from: ftp://ftp.service.digital.com/public/vms/axp/v7.1/alppppd01_071.A-DCX_AXPEXE ftp://ftp.service.digital.com/public/vms/axp/v7.1/alppppd01_071.CVRLET_TXT 3.16.2 PPPD CONNECT Causes the System to Fail When this version of TCP/IP Services is started, shut down, and then started again, then a remote user dials in and issues the PPPD CONNECT command, the system fails. The problem is fixed in remedial kits for SYS$PPPDRIVER. 3.17 Configuring Your Host as a Dialup Provider The TCP/IP Services product requires the use of a unique IP address when creating a network interface. If you mistakenly assign an IP address that has already been assigned to another interface, your PPP connection will work but upon termination, any other applications with active connections will hang. You must restart TCP/IP Services if this occurs. 3.18 RCP Problems and Restrictions RCP has the following problems: o The RCP command requires that directories, whether specified explicitly or implicitly, be specified as [directory] (with square bracket delimiters). Use of angle bracket delimiters is not supported. Problems and Restrictions 3-11 Problems and Restrictions 3.18 RCP Problems and Restrictions For example, the following commands specify the implicit directory correctly: $ SET DEFAULT DISK:[USER] $ RCP A.DAT XYZ:A.DAT The following command shows a correct (for RCP) explicit directory specification: $ RCP DISK:[DIR]A.DAT XYZ.DAT Note that the following commands specify an incorrect implicit directory and may not work reliably: $ SET DEFAULT DISK: $ RCP A.DAT XYZ:A.DAT RCP may exit with a memory access violation (ACCVIO) when an incorrect logical name and a directory specification of the angle bracket form are (implicity or explicitly) specified at the same time to RCP. For example: $ DEFINE/JOB/EXEC SYS$LOGIN_DEVICE SYS$LOGIN $ SET DEFAULT SYS$LOGIN_DEVICE: $ RCP A.DAT XYZ:A.DAT In this example, the first command (DEFINE/JOB/EXEC) does not contain the trailing colon (:) after the device name. As a result, the RCP command specifies an invalid logical and directory. o When the OpenVMS host running RCP is the source of a file, RCP converts the file into STREAM_LF format. This is the equivalent of an FTP or KERMIT ASCII transfer. If the file is actually a binary file, such as an executable file, RCP inserts extra linefeed characters. In most cases, this renders the binary file unusable. The workaround is to do the following: 3-12 Problems and Restrictions Problems and Restrictions 3.18 RCP Problems and Restrictions $ dir/full abc.bin ! note file characteristics $ copy abc.bin abc_copy.bin $ $ ! Cause $RCP to skip file conversion. $ set file/attributes=(rfm:stmlf) abc_copy.bin $ $ rcp abc_copy.bin remote_host:remote_abc.bin $ ! If the remote host is an OpenVMS host $ ! then, on the remote host, restore the file attributes $ ! Say the file abc.bin was really abc.exe $ set file remote_abc.exe/attribute=(rfm:fix, lrl:512) $ ! $backup expects LRL:32256 $ $ ! Done o OpenVMS file attributes are lost when RCP transfers files between two OpenVMS systems running TCP/IP Services for OpenVMS. All output files are created in STREAM_LF format. 3.19 REUSEADDR Behaviour change in V4.2 to V5.x Transition Using the REUSEADDR socket option produces different results on TCP/IP Services Version 4.2 and TCP/IP Services Version 5.x. Under Version 4.2, a TCP/IP server with a passive (listen) socket was able to run under multiple processes with the same IP address and port number. Under Version 5.x, the same circumstances result in the following fatal error: Failed to bind socket %SYSTEM-F-DUPLNAM, duplicate name 3.20 POP Problems The following problems with the Post Office Protocol (POP) server exist in TCP/IP Services Version 5.x: o Both the TCP/IP Services and IUPOP3 POP servers have problems parsing addresses that include personal names enclosed in quotation marks. Problems and Restrictions 3-13 Problems and Restrictions 3.20 POP Problems o Both the TCP/IP Services and IUPOP3 POP servers have problems parsing addresses that contain a space within the address. 3.21 SMTP Problems With TCP/IP Services Version 5.x, corruption might occur in SMTP control files. Intermittently, the SMTP server signals an error on a particular control file. The most common error message returned is SYSTEM-F-BADPARAM, although the problem can sometimes result in the access violation message SYSTEM- F-ACCVIO. During most of the occurrences, the symbiont process crashes, leaving a dump file. If you do not delete the queue entry for the control file that caused the crash, the entry will be the first entry processed when the queue is started after the crash, which causes the queue to crash again. If the job is put on hold and the TCP/IP management command SHOW MAIL/FULL is issued, the SHOW MAIL command either signals an error or hangs. This problem is due to a periodic corruption that occurs in SMTP control files and happens more frequently with high- use systems (1000 or more control files processed per day) than with systems processing less mail. To work around the problem, run the SMTP queue watcher command file TCPIP$EXAMPLES:TCPIP$RESTART_SMTPQ.COM. The header comments of this file describe its use and operation. The following describes additional problems and workarounds: o SMTP does not recognize mail to the cluster alias (IP address or DNS name) as local. V4.x versions of the product do. Workaround: Add the name of the cluster alias to the local aliases file. o The ANALYZE MAIL command does not find control files stored in TCPIP$SMTP_COMMON when TCPIP$SMTP_COMMON is not pointing to SYS$SPECIFIC:[TCPIP$SMTP]. 3-14 Problems and Restrictions Problems and Restrictions 3.21 SMTP Problems Workaround: Manually submit the control file to the SMTP queue. 3.22 Status Returned by RSH and REXEC Command Files The RSH and REXEC command files return the status of the RSH or REXEC execution, not the status of the remote command execution. The INETACP uses this return status to determine if it should append an INETACP error message. The remote command executed returns its own error message by means of SYS$OUTPUT and or SYS$ERROR. 3.23 $QIO Programming The function IO$_WRITEVBLK will return the error SS$_ EXQUOTA under the following circumstances: o The process is set /NORESOURCE_WAIT (see SET PROCESS /RESOURCE_WAIT). o The socket does not have enough space available (within its send quota) to be able to buffer all of the data being written at that moment. If both of these conditions occur, the SS$_EXQUOTA error is returned. In addition, the data to be written will not be queued for transmission; it is rejected as a whole. This error affects the various socket routines used to transmit data: send(), sendto(), and sendmsg(). The C RTL returns an error indication on the call, and sets "errno" to EVMSERR (65535); the OpenVMS specific "vaxc$errno" contains the underlying error, SS$_EXQUOTA. 3.24 SNMP Problems This section details restrictions to the SNMP component for this release. Problems and Restrictions 3-15 Problems and Restrictions 3.24 SNMP Problems 3.24.1 Incomplete Restart When the SNMP master and subagents fail or are stopped, TCP/IP Services is often able to restart all processes automatically. However, under certain conditions subagent processes may not restart; that is, the DCL command SHOW SYSTEM display does not include TCPIP$OS_MIBS and TCPIP$HR_ MIB. If this situation occurs, restart SNMP by issuing the following commands: $ @SYS$STARTUP:TCPIP$SNMP_SHUTDOWN $ @SYS$STARTUP:TCPIP$SNMP_STARTUP 3.24.2 SNMP IVP Error On slow systems, the SNMP Installation Verification Procedure can fail because a subagent does not respond to the test query. The error messages look like this: . . . Shutting down the SNMP service... done. Creating temporary read/write community SNMPIVP_153. Enabling SET operations. Starting the SNMP service... done. SNMPIVP: unexpected text in response to SNMP request: "- no such name - returned for variable 1" 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. Press Return to continue ... These types of messages in the IVP can be safely ignored. 3.24.3 Using Existing MIB Subagent Modules If an existing subagent does not execute properly, you may need to relink it against the current version of TCP/IP Services to produce a working image. Some subagents (such as those for OpenVMS support of Compaq Insight Manager) also require a minimum version of OpenVMS and a minimum version of TCP/IP Services. 3-16 Problems and Restrictions Problems and Restrictions 3.24 SNMP Problems The following general restrictions and cautions apply: o In general, only executable images linked against the following versions of the eSNMP shareable image are upward compatible with TCPIP V5.1: - UCX$ESNMP_SHR.EXE from TCP/IP Services V4.2 ECO 4 - TCPIP$ESNMP_SHR.EXE from TCP/IP Services V5.0A ECO 1 Images built under versions other than these can be relinked with one of the shareable images, or with TCPIP$ESNMP_SHR.EXE in TCP/IP Services V5.1. o The underlying eSNMP API changed from DPI in V5.0 to AgentX in V5.1. Therefore, executable images linked against older object library versions of the API (*$ESNMP.OLB) must be relinked, either against the new object library or against the new shareable image. Linking against the shareable image insures future upward compatibility and results in smaller image size. ________________________ Note ________________________ Although images may run without a relink, such backward compatibility is not supported and may result in inaccurate data or run-time problems. ______________________________________________________ o Programs that rely on TCP/IP Services Version 4.2 kernel data structures or access functions may run but may not return valid data. Such programs should be rewritten. o Executable images linked against UCX$ACCESS_SHR.EXE, UCX$IPC_SHR.EXE, UCX$RPCXDR_SHR.EXE, or other older shareable images, may not run even when relinked. It may be necessary to recompile, or rewrite and recompile such programs. o If you have executable images linked against versions other than those listed above and cannot relink, contact Compaq support for assistance. o If you have problems running executable images linked against TCP/IP Services V4.2 ECO 4 or TCP/IP Services V5.0A ECO 1, verify that the version of the shareable image is the latest by entering the following DCL command: Problems and Restrictions 3-17 Problems and Restrictions 3.24 SNMP Problems $ DIRECTORY/DATE/PROTECTION SYS$SHARE:*$ESNMP_SHR.EXE The creation dates of the files with the prefix TCPIP$ and UCX$ should be within a few seconds of each other, and only one version of each file should exist. Make sure both images include the file protection W:RE. Also, you can use the following command to check the version: $ TCPIP SHOW VERSION/ALL The second column in the line for image TCPIP$ESNMP_SHR under the category "Network Management" displays the version. For example, for field test: TCPIP$ESNMP_SHR;1 T5.1-9Q 22-NOV-2000 SYS$COMMON:[SYSLIB] o TCP/IP Services V5.0A ECO 1 and TCP/IP Services V5.1 both provide an updated version of the UCX$ESNMP_SHR.EXE shareable image to provide compatibility with subagents linked under TCP/IP Services V4.2 ECO 4. Do not delete this file. 3.24.4 Restrictions to RFC-Defined Functionality o SNMP requests are not implemented for the following MIB-II group objects: ipRouteMetric1 - ipRouteMetric5 tcpMaxConn o SNMP requests are not implemented for the following Host Resources MIB objects: hrPartitionTable hrPrinterTable hrSWInstalled hrSWInstalledTable o SNMP set requests are not implemented for the following MIB-II group objects: 3-18 Problems and Restrictions Problems and Restrictions 3.24 SNMP Problems ipDefaultTTL ipRouteAge ipRouteDest ipRouteIfIndex ipRouteMask ipRouteNextHop ipRouteType o SNMP set requests are not implemented for the following Host Resources MIB objects: hrFSLastFullBackupDate hrFSLastPartialBackupDate hrStorageSize hrSWRunStatus hrSystemDate hrSystemInitialLoadDevice hrSystemInitialLoadParameters o In the SNMP group (1.3.6.1.2.1.11), data elements noted as obsolete in RFC 1907 are not implemented. 3.24.5 SNMP Restrictions and Characteristics The restrictions and characteristics of SNMP are described below. For more information, refer to the Compaq TCP/IP Services for OpenVMS SNMP Programming and Reference guide. o The SNMP server responds correctly to SNMP requests directed to a cluster alias. Note, however, that an unexpected host might be reached when querying from a TCP/IP Services Version 4.x system that is a member of a cluster group but is not the current impersonator. o The SNMP master agent and subagents will not start up if the value of logical name TCPIP$INET_HOST does not yield an IP address of a functional interface on the host when used in a DNS query. This problem does not occur if the server host is configured correctly with a permanent network connection (for example, Ethernet or FDDI, or both). The problem can occur when a host is connected through PPP and the IP address used for the PPP connection does not match the IP address of the TCPIP$INET_HOST logical name. Problems and Restrictions 3-19 Problems and Restrictions 3.24 SNMP Problems o Under certain conditions observed primarily on OpenVMS VAX systems, the master agent or subagent exits with an error from an internal select() socket call. Under most circumstances, looping does not occur. To control the number of iterations should looping occur, define the TCPIP$SNMP_SELECT_ERROR_LIMIT logical name. o The MIB browser provided with TCP/IP Services (TCPIP$SNMP_REQUEST.EXE) supports getnext processing of OIDs that include the 32-bit OpenVMS process ID as a component. However, other MIB browsers might not provide this support. 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. 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.1 where 1.3.6.1.4.1.36.2.15.x3.7.1 corresponds to: iso.org.dod.internet.private.enterprises.dec.ema.sysobjectids.openvms.- 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. When both the TCPIP$OS_MIBS and TCPIP$HR_MIB subagents are running, a get request on the sysORTable is as follows. Except where noted, the OIDs conform to RFC 1907: 1.3.6.1.2.1.1.9.1.2.1 = 1.3.6.1.4.1.36.15.3.3.1.1 1.3.6.1.2.1.1.9.1.2.2 = 1.3.6.1.4.1.36.15.3.3.1.2 1.3.6.1.2.1.1.9.1.3.1 = Base o/s agent (OS_MIBS) capabilities 1.3.6.1.2.1.1.9.1.3.2 = Base o/s agent (HR_MIB) capabilities 1.3.6.1.2.1.1.9.1.4.1 = 31 = 0 d 0:0:0 1.3.6.1.2.1.1.9.1.4.2 = 36 = 0 d 0:0:0 3-20 Problems and Restrictions Problems and Restrictions 3.24 SNMP Problems This example is from the MIB browser (TCPIP$SNMP_ REQUEST.EXE). o The hrDeviceTable now includes template devices (for example, DNFS0 for NFS and DAD0 for virtual devices). o For network devices, only the template devices (those with unit number 0) are displayed. o The hrDeviceTable includes all devices known to the OpenVMS host except those with the following characteristics. - Off-line - Remote - UCB marked delete-on-zero-reference-count - Mailbox device - Device with remote terminal (DEV$M_RTT characteristic) - Template terminal-class device - LAT device (begins with _LT) - Virtual terminal device (begins with _VT) - Pseudoterminal device (begins with _FT) o Data items in the hrDevTable group have the following restrictions: - hrDeviceID: Always null OID (0.0) - hrDeviceErrors coded as: _____________________________________________________ Code________Condition________________________________ warning If error logging is in progress (OpenVMS (3) UCB value UCB$M_ERLOGIP) running If status indicates software is valid and (2) no error logging in progress (OpenVMS UCB value UCB$M_VALID) unknown Any other OpenVMS status (1)__________________________________________________ Problems and Restrictions 3-21 Problems and Restrictions 3.24 SNMP Problems o On systems running versions of the operating system prior to OpenVMS 7.1-2, counters for the MIB-II ifTable do not wrap back to 9 after reaching the maximum value (232- 1), as defined in RFC 1155. Instead, they behave like the gauge type and remain at the maximum value until cleared by an external event such as a system reboot. The counters affected are as follows: ifInDiscards ifInErrors ifInNUcastPkts ifInOctets ifInUcastPkts ifInUnknownProtos ifOutErrors ifOutNUcastPkts ifOutOctets ifOutUcastPkts Note that for SNMPv2, these counters are data type Counter32. The following ifTable members are always - 1 for OpenVMS: ifOutDiscards (Counter32) and ifOutQLen (Gauge32). o Under certain conditions, a subagent makes a duplicate entry in sysORTable when it restarts. For example: 1.3.6.1.2.1.1.9.1.2.1 = 1.3.6.1.4.1.36.15.3.3.1.1 1.3.6.1.2.1.1.9.1.2.2 = 1.3.6.1.4.1.36.15.3.3.1.2 1.3.6.1.2.1.1.9.1.2.1 = Base o/s agent (OS_MIBS) capabilities 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 In this example, the TCPIP$OS_MIBS subagent made two entries with different ID numbers (OIDs with the prefix 1.3.6.1.2.1.1.9.1.2) that may show different sysORUpTime (1.3.6.1.2.1.1.9.1.4). The snmp_request program translates the value in centiseconds to day (d) plus hours:minutes:seconds notation, dropping any fractions of seconds. The HR_MIB subagent has not yet successfully started and registered its capabilities. If it starts, its entries in this example would use the next available index number. 3-22 Problems and Restrictions Problems and Restrictions 3.24 SNMP Problems o hrFSMountPoint (1.3.6.1.2.1.25.3.8.1.2) is DNFSn. The device may change between restarts, or after a dismount/mount procedure. o In the hrFSTable group, if no file systems are mounted through NFS or no information is accessible, a "no such instance" status is returned for a get request. Browsers respond differently to this message. For example, TCPIP$SNMP_REQUEST.EXE responds with no output and returns directly to the DCL prompt. After an NFS mount, the following information is returned in response to a get request. The data items implemented for OpenVMS (refer to RFC 1514) are: - hrFSIndex - hrFSMountPoint: local DNFS device name - hrFSRemoteMountPoint: In UNIX format, the remote file system name - hrFSType: OID 1.3.6.1.2.1.25.3.9.1, if remote system is running TCP/IP Services, and the file system is not a UNIX style container file system. hrFSNFS, OID 1.3.6.1.2.1.25.3.9.14, if OpenVMS TCP/IP container file system or UNIX host - hrFSAccess (as defined in RFC 1514) - hrFSBootable: always HRM_FALSE (integer 2) - hrFSStorageIndex: always 0 - hrFSLastFullBackupDate: unknown time. Encoded according to RFC 1514 as hexadecimal value 00 00 01 01 00 00 00 00 (January 1, 0000). - hrFSLastPartialBackupDate: unknown time. Not available for OpenVMS systems. Instead, hexadecimal value 00-00-01-01-00-00-00-00 (January 1, 0000) applies. o hrProcessorFrwID (OID prefix 1.3.6.1.2.1.25.3.3.1.1): - Is not implemented on OpenVMS VAX. Always returns standard null OID (0.0). 1.3.6.1.2.1.25.3.3.1.1.1 = 0.0 Problems and Restrictions 3-23 Problems and Restrictions 3.24 SNMP Problems - For OpenVMS Alpha, an example is as follows. The example corresponds to firmware version 5.56-7. 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 o Data items in the hrDiskStorage table have the following restrictions: - hrDiskStorageMedia: Always "unknown" (2) - hrDiskStorageRemoveble: Always "false" (2). 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). o You can ignore the following warnings that appear in the log files: - On subagent startup: {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 is retrieved in response to a Get, GetNext, or GetBulk request: {executable-image-name} WARNING {source-file-name} line {nnn}: Null Varbind or object, or, bad object type 3.24.6 Upgrading Requires Restart After upgrading to TCP/IP Services V5.1, you must disable and then enable SNMP using TCPIP$CONFIG. When prompted for "this node" or "all nodes", select the option that reflects the previous configuration. 3.24.7 Communication Controller Data Not Fully Updated When you upgrade TCP/IP Services and then modify an existing communication controller, programs that use the communication controller may not have access to the updated information. To ensure programs like the MIB browser (snmp_request) have access to the new data about the communication controller: 1. Delete the communication controller using the TCP/IP management command DELETE COMMUNICATION_CONTROLLER. 3-24 Problems and Restrictions Problems and Restrictions 3.24 SNMP Problems 2. Reset the communication controller by running the TCPIP$CONFIG.COM procedure and exiting. 3. Restart the program (such as SNMP). For example: $ @SYS$STARTUP:SNMP_SHUTDOWN.COM $ @SYS$STARTUP:SNMP_STARTUP.COM 4. Use the TCP/IP management command LIST COMMUNICATION_ CONTROLLER to display the information. 3.24.8 SNMP MIB Browser Usage If you use either the -l (loop mode) or -t (tree mode) flag, you cannot also specify the -m (maximum repititions) flag or the -n (nonrepeaters) flag. The latter flags are incompatible with loop mode and tree mode. 3.24.9 Duplicate Subagent Identifiers With this version of TCP/IP Services, it is possible for two subagents to have the same identifier parameter. However, be aware that this makes it more difficult to determine the cause of problems reported in the log file. 3.24.10 Invalid Response to Trap The SNMP master agent sends an invalid response packet to a subagent that sends a trap with a long protocol packet payload. For example, a long protocol packet payload might include seven octet string varbinds, each with 255 characters. The invalid response packet causes the subagent to restart. However, the master agent sends the trap to registered trap listeners. The chess program example exhibits this problem. 3.25 eSNMP Programming and Subagent Development The following notes pertain to eSNMP programming and subagent development. o In the documentation, the terms extension subagent, custom subagent, and user-written subagent refer to any subagent other than the standard subagents for MIB-II and the Host Resources MIB, which are provided as part of the TCP/IP Services product. Problems and Restrictions 3-25 Problems and Restrictions 3.25 eSNMP Programming and Subagent Development o For overall architecture information and details about the eSNMP API, refer to the Compaq Tru64 UNIX documentation at the following URL. www.tru64unix.compaq.com The eSNMP software for OpenVMS is derived from the Tru64 UNIX product. o In the [.SNMP] subdirectory of TCPIP$EXAMPLES, files with the .C, .H, .COM, .MY, and .AWK extensions contain additional comments and documentation. o The TCPIP$SNMP_REQUEST.EXE, TCPIP$SNMP_TRAPSND.EXE, and TCPIP$SNMP_TRAPSND.EXE programs are useful for testing during extension subagent development. o For information about prototypes and definitions for the routines in the eSNMP API, see the TCPIP$SNMP:ESNMP.H file. 3.26 DIGITAL TCP/IP Services for OpenVMS User's Guide Problems and Restrictions The DIGITAL TCP/IP Services for OpenVMS User's Guide guide has not been updated for the release of TCP/IP Services. The following errors and changes affect the DIGITAL TCP/IP Services for OpenVMS User's Guide: o The manual does not reflect the use of quotation marks to preserve the casing of user names, as described in Section 1.2.11 in these release notes. o The example showing the use of the RSH /ESCAPE_CHARACTER qualifier needs to be improved. The following shows a better example: $ RSH TRUNIX /USER_NAME=EVT /ESCAPE_CHARACATER="@" Password: Last successful login for evt: Wed Nov 18 15:50:22 1998 from OVMS Last unsuccessful login for evt: Tue Oct 13 14:16:51 1998 on ttyp3 Digital UNIX V3.2C (Rev. 148); Tue Apr 2 18:32:54 EST 1996 Digital UNIX V3.2D-1 Worksystem Software (Rev. 41) Digital Equipment Corporation Internal Use Only 3-26 Problems and Restrictions Problems and Restrictions TCP/IP Services for OpenVMS User's Guide Problems and Restrictions trunix.ucx.lkg.dec.com>@. (character string not echoed) %RSH-S-LCLCLOSED, Local connection closed In this example, the escape character closed the connection from the local side as opposed to the remote system closing the connection. o The manual indicates that the default setting for the RSH command is /NOTRUNCATION_USER_NAME. This is an invalid qualifier, which will be removed the manual. o The messages displayed in response to the FTP Client command MPUT have been improved as described in Section 4.1.12. Problems and Restrictions 3-27 4 _________________________________________________________________ Corrections 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. o Section 4.2 lists problem reports addressed in this release. 4.1 Software Corrections This section describes the changes and problems corrected since the product's last release. In addition, please see Section 1.2 for information about other software changes made for this release. 4.1.1 UCP Problems Fixed Since Last Release The TCP/IP management command SET ROUTE allows the /MASK qualifier to be used when specifying a CIDR mask without requiring the /NETWORK qualifier. The resulting route that is created may not be useable. If you specify the /MASK qualifier on the SET ROUTE command, you must also include the /NETWORK qualifier. 4.1.2 TELNET Server Problems Fixed Since Last Release When the TELNET server is configured for virtual terminals (VTAs), and the TELNET command UNBIND specifies an inbound TELNET connection whose VT device has been associated with the specified TN device, the system fails with an INVEXCEPTN error. Corrections 4-1 Corrections 4.1 Software Corrections The driver has been enhanced to verify the arguments to the TELNET commands BIND and UNBIND. The situation described in this section fails correctly with the status SS$_ DEVREQERR. 4.1.3 TELNETSYM Problems Fixed Since Last Release The limit of 16 queues (streams) for each TELNETSYM process has been updated to 32 to reflect the new queue manager limit. TELNETSYM now supports up to 32 queues for each symbiont process. 4.1.4 IPC Problems Fixed Since Last Release The gethostaddr routine was not working. 4.1.5 DHCP Problems Fixed Since Last Release o Sometimes the DHCP client process hangs and is unresponsive to any commands except DHCPSIGTERM. This happens only when the TCPIP$DHCP_DEBUG logical is not defined. o The lt field from a DHCPCAP entry keyed on the subnet and vendor class was being missed. 4.1.6 POP Problems Fixed Since Last Release o The POP server will no longer incorrectly set the Date: header for non-SMTP (such as DECnet) mail messages based on the current system time and date. The date used will be based on the mail message's delivery time into the user's mailbox. o The POP server now flushes the log file on each write to it. This ensures that the log is always current with the state of the POP server process. 4.1.7 SMTP Problems Fixed Since Last Release o Mail that contains 8-bit characters may be converted by some mailers to a MIME quoted-printable format that is displayed with encoded characters by OpenVMS mail. To prevent the conversion by mailers, set the following logical: TCPIP$SMTP_8BITMIME_HACK 4-2 Corrections Corrections 4.1 Software Corrections This Boolean logical tells the local mail server to accept the ESMTP 8BITMIME request from the remote SMTP client, preventing the mail client from converting the 8-bit characters and allowing OpenVMS mail to display the message properly. o A mail message with an empty Reply-To header causes a strange header to appear in the OpenVMS MAIL From: line. SMTP ignores empty sender headers (Repy-To, From, Sender) when it formats the message. 4.1.8 BIND Resolver Problems Fixed Since Last Release SMTP failed with an access violation while attempting to do an MX lookup when both of the following conditions were true in the TCPIP$GET_MX resolver routine: 1. There were no NS records returned from the query to the BIND server. 2. UCP passed an allowed but improperly handled value of 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: o The SET CONFIGURATION INTERFACE command fails to create a default broadcast mask when you create a cluster interface record. For example: $ TCPIP TCPIP> SET CONFIGURATION INTERFACE WE0 - _TCPIP> /CLUSTER=16.20.208.68 /C_NETWORK=255.255.0.0 TCPIP> SHOW CONFIGURATION INTERFACE WE0 /FULL Interface: WE0 IP_Addr: 16.20.208.68 NETWRK: 255.255.0.0 BRDCST: 16.20.255.255 C_Addr: 16.20.208.68 C_NETWRK: 255.255.0.0 C_BRDCST: Flags: Receive buffer: 0 Corrections 4-3 Corrections 4.1 Software Corrections o The SET INTERFACE command permits the creation of multiple pseudointerfaces having identical interface names. In addition, the SET INTERFACE command does not correctly create pseudointerfaces with unit numbers greater than 9 (valid unit numbers range from 0 to 255). For example, this SET INTERFACE commands fails to create WFA10: $ TCPIP SET INTERFACE WFA10 /HOST=10.10.0.10 Output from the SHOW INTERFACE command demonstrates this. (The WFA1 interface shown below should have been created as WFA10.) $ TCPIP SHOW INTERFACE Packets Interface IP_Addr Network mask Receive Send MTU LO0 127.0.0.1 255.0.0.0 18355 18355 4096 WF0 16.20.208.100 255.255.0.0 5104314 5068074 4470 WFA1 10.10.0.10 255.255.0.0 5104314 5068074 4470 This SET INTERFACE command results in creating two pseudointerfaces that have identical names: $ TCPIP SET INTERFACE WFA11 /HOST=10.10.0.11 Output from the SHOW INTERFACE command demonstrates this. (The second WFA1 interface shown below should have been created as WFA11).) $ TCPIP SHOW INTERFACE Packets Interface IP_Addr Network mask Receive Send MTU LO0 127.0.0.1 255.0.0.0 18367 18367 4096 WF0 16.20.208.100 255.255.0.0 5144574 5077124 4470 WFA1 10.10.0.10 255.255.0.0 5144574 5077124 4470 WFA1 10.10.0.11 255.255.0.0 5144574 5077124 4470 Note that: o Pseudointerfaces cannot be modified; that is, a pseudointerface must be deleted and then created to change its associated network address. o Use of the /HOST qualifier is required when creating pseudointerfaces. 4-4 Corrections Corrections 4.1 Software Corrections o The TCP/IP management command START ROUTING/SUPPLY does not supply the route. The workaround was to use GATED with RIP enabled. o Specifying a remote host by IP address on an RSH command could trigger an access violation error when no host name could be found in the local or BIND database for the IP address. 4.1.10 PPP/SLIP Problems Fixed Since Last Release The following command sequence crashes the system: $ TCPIP SET INTERFACE PP0 /SERIAL=TTA1 /NETWORK_MASK=x.x.x.x $ TCPIP SET INTERFACE PP0/SERIAL=TTB0 %TCPIP-E-INVINTER, error defining interface: PP0 -TCPIP-I-ACPQIO, failure on internet ACP QIO -SYSTEM-W-NOMSG, Message number 0000FCE0 4.1.11 FTP Server Problems Fixed Since Last Release o In previous versions of TCP/IP Services, when a client address is not known to the name server, an excessive delay after the password prompt can occur. This delay is caused by possible multiple name server timeouts, multiple retires, and multiple name servers. This problem has been corrected. Define the following logical to correct this problem: - TCPIP$FTP_SERVER_NAME_SERVICE_TIMEOUT Specify the number of seconds for the timeout interval. For more information, refer to the description of the SET NAME_SERVICE/TIMEOUT command in the Compaq TCP/IP Services for OpenVMS Management Command Reference manual. - TCPIP$FTP_SERVER_NAME_SERVICE_RETRY Specify the number of times the BIND resolver should attempt to contact a BIND server if the first attempt fails. These logical names are used only if the FTP server will be using host names (that is, the logical name TCPIP$FTP_SERVER_LOG_CLIENT_BY_ADDRESS is not defined). Corrections 4-5 Corrections 4.1 Software Corrections o TELNET, RLOGIN, RSH, and REXEC examine the log option address bit in the service database. If the bit is set, they display host names as numeric presentation addresses (for example, n.n.n.n or IPv6 address). If the bit is clear and the name is in the local host database or the BIND resolver knows the host name, they use that name. The default is to the numeric form. This bit is set by $TCPIP SET SERVICE FTP/LOG_OPTION=address. The FTP server has been modified to lookup and use this bit. In particular, SYS$REM_NODE and SYS$REM_NODE_ FULLNAME in the FTP child process will always contain a numeric presentation address when this bit is set. In situations where numeric addresses are appropriate in the FTP server and other log files, you may want to set this logical. Setting it makes the FTP session login operation slightly faster and less expensive because a name lookup is avoided. 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. This condition has been corrected. This allows access to multiple alternate, possibly language specific, component help libraries. o In previous versions of TCP/IP Services, when FTP was connected to a non-VMS_PLUS remote host or node, the following sequence would yield an uppercase file name for the first MPUT and a lowercase file name for the second (and later) and MPUTs: $ FTP host-name/USER=user-name/PASS=password FTP> MPUT A.dat ! Yields A.DAT at destination FTP> PUT A.dat ! Yields a.dat FTP> MPUT A.dat ! Yields a.dat rather than expected/previous A.DAT This problem occurs for several commands, in addition to PUT. This behaviour has been corrected so that the second MPUT command will now yield a file name with the same case as the first. This problem occurs only with the above sequence of commands and when there is no TCPIP$FTPINIT.INI file. 4-6 Corrections Corrections 4.1 Software Corrections Use the FTP CASE OFF and CASE ON commands to change the typographical case used by MPUT to lowercase and back to uppercase. o Files with no "type" in a RENAME operation could cause memory to be accessed which should not have been. o Inaccurate use of RMS_POSTED in the appe_ascii() and recv_ascii() routines causes the FTP client to lose synchronization with the server. 4.1.12 FTP Client Problems Fixed Since Last Release The following corrections have been made to the FTP client. o The FTP Client does not properly take input from command files with Fortran RMS record attributes. This problem is observed on systems running versions of OpenVMS prior to Version 7.1 and certain versions of DEC C RTL. o The text returned by the FTP command STATUS has been improved to make the following clear: - The specified variable affects only the MPUT command. - The CASE ON command really means "as is," rather than "force to uppercase." The CASE OFF command means "force to lowercase," but CASE ON does not mean the inverse. - The MPUT command may not always be able to comply with your case settings. 4.1.13 Load Balancing Problems Fixed Since Last Release The following corrections have been made to the load balancing component (LBROKER). o The LBROKER log file contains the host name that generated the file. For example: TCPIP$LBROKER_host-name.LOG o The following NOTICE-level LBROKER log file message has been changed to be a DEBUG level message: NOTICE: updated DNS RRset cluster_name This will now only be displayed if the TCPIP$LBROKER_ LOG_LEVEL logical is set to 1 or greater. Corrections 4-7 Corrections 4.1 Software Corrections o In the LBROKER configuration file you may specify "max- members," which tells the load broker how many A records to send to the BIND server. The problem occured if you specified a count of 1. Instead of sending one record, it sent all of them from the members list. With TCP/IP Services V5.1, max-members behaves as expected when specified as 1 in the LBROKER configuration file. 4.1.14 NTP Problems Fixed Since Last Release The following logical name allows you to specify debug mode for NTP: TCPIP$NTP_LOG_LEVEL This logical should be defined with /SYSTEM and can assume a value in the range 1-6 (with 6 being the most verbose). 4.2 Reported Problems Fixed Since Last Release Compaq uses the IPMT (Integrated Problem Management Tool) to track problems reported by customers. When a problem report is created, it is given a unique identification number, starting with "CFS." When the problem is logged for engineering attention, it receives a PTR number. This section describes problems which have been reported and fixed, providing the CFS and PTR identifiers for each. Table_4-1_Management_Problems_Fixed_Since_Last_Release_____ CFS_Number__PTR_Number_______Description___________________ CFS.70983 70-5-1158 The SHOW PROTOCOL UDP/PARAM command does not show receive quotas. The SET PROTOCOL UDP/QUOTA=RECEIVE=value command does not work. (continued on next page) 4-8 Corrections Corrections 4.2 Reported Problems Fixed Since Last Release Table 4-1 (Cont.) Management Problems Fixed Since Last __________________Release__________________________________ CFS_Number__PTR_Number_______Description___________________ CFS.72192 70-5-1195 The following TCPIP command doesn't work if the /ADDRESS qualifier value specifies a network address with subnet: TCPIP> SET NETWORK net /ADDRESS=x.x.x.x For example, the following SET NETWORK command (without subnet info) works: $ TCPIP SET NETWORK VMSNET /ADDRESS=18.0.0.0 However, the following SET NETWORK command (with subnet info) fails: $ TCPIP SET NETWORK VMSNET /ADDRESS=16.66.66.0 %TCPIP-E- NETWORKERROR, error processing network request -TCPIP-E- INVQUAL, invalid qualifier value for /ADDRESS -TCPIP-I- ____________ADR_HOST,_internet_address_specifies_a_host____ Table_4-2_BIND_Server_Problems_Fixed_Since_Last_Release____ CFS_Number__PTR_Number_______Description___________________ CFS.72317 70-5-1198 The restriction that you could only have one BIND server enabled among nodes sharing a system disk in a cluster no longer exists. (continued on next page) Corrections 4-9 Corrections 4.2 Reported Problems Fixed Since Last Release Table 4-2 (Cont.) BIND Server Problems Fixed Since Last __________________Release__________________________________ CFS_Number__PTR_Number_______Description___________________ CFS.75957 70-5-1382 The BIND server was not rolling over the database file when the maximum version number of 32767 was reached. This specifically applied to a slave server that was increasing the database file version number by performing a zone transfer. Master servers already had a form of this rollover functionality. CFS.73712 70-5-1274 BIND did not support the dynamic updating of SRV resource records. CFS.68483 70-5-1079 The BIND server reports syntax CFS.66892 70-5-1022 errors when CIDR notation was used in the configuration file _____________________________(TCPIP$BIND.CONF).____________ Table_4-3_NFS_Client_Problems_Fixed_Since_Last_Release_____ CFS_Number__PTR_Number_______Description___________________ CFS.68919 70-5-1094 Beginning with VMS V7.2, running BACKUP on an NFS client device results in the following error: _____________________________-SYSTEM-F-BADATTRIB,_bad_attribute control list Table_4-4_TELNET_Server_Problems_Fixed_Since_Last_Release__ CFS_Number__PTR_Number_______Description___________________ CFS.67834 70-5-1053 System crash in TN$NETWORK_ _____________________________DISCONNECT()._________________ 4-10 Corrections Corrections 4.2 Reported Problems Fixed Since Last Release Table_4-5_PPP/SLIP_Problems_Fixed_Since_Last_Release_______ CFS_Number__PTR_Number_______Description___________________ CFS.69244 70-5-1108 An accepted socket doesn't inherit the probe and drop settings (tcp_keepidle, tcp_ keepintvl, tcp_keepcnt) of the listener socket. CFS 76412 70-5-1399 TCP/IP Services limits the number of SLIP and PPP interfaces to 9. For more information, refer to the Compaq TCP/IP Services for OpenVMS Management guide for _____________________________TCP/IP_Services_Version_5.1.__ Table_4-6_NTP_Problems_Fixed_Since_Last_Release____________ CFS_Number__PTR_Number_______Description___________________ CFS.75496 70-5-1382 Problems occur when using TCPIP$NTPTRACE against a TCP/IP Services NTP server that had been designated as _____________________________"free-running."_______________ Corrections 4-11