This document describes the new features and changes to the HP TCP/IP Services for OpenVMS Version 5.4 software product.
Revision/Update Information: This is a new document.
Software Version: HP TCP/IP Services for OpenVMS Version 5.4
Operating Systems: HP OpenVMS Alpha Versions 7.3-1 and 7.3-2
Hewlett-Packard Company Palo Alto, California
© 2003 Hewlett-Packard Development Company, L.P.
UNIX® is a registered trademark of The Open Group.
Microsoft® is a US registered trademark of Microsoft Corporation.
The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.
Proprietary computer software. Valid license from HP 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.
The HP TCP/IP Services for OpenVMS documentation is available on CD-ROM.
| Contents |
The HP TCP/IP Services for OpenVMS product is the HP implementation of the TCP/IP protocol suite and internet services for OpenVMS Alpha and OpenVMS VAX systems. This document describes the HP TCP/IP Services for OpenVMS Version 5.4 product.
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 HP TCP/IP Services for OpenVMS Installation and Configuration manual.
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.
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.
Table 1 lists the documents available with this version of TCP/IP Services.
| Manual | Contents |
|---|---|
| Compaq TCP/IP Services for OpenVMS Concepts and Planning |
This manual provides conceptual information about TCP/IP networking on
OpenVMS systems, including general planning issues to consider before
configuring your system to use the TCP/IP Services software.
This manual also describes the other manuals in the TCP/IP Services documentation set and provides a glossary of terms and acronyms for the TCP/IP Services software product. |
| HP TCP/IP Services for OpenVMS Release Notes | 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. |
| HP TCP/IP Services for OpenVMS Installation and Configuration | This manual explains how to install and configure the TCP/IP Services product. |
| HP TCP/IP Services for OpenVMS User's Guide | This manual describes how to use the applications available with TCP/IP Services such as remote file operations, e-mail, TELNET, TN3270, and network printing. |
| HP TCP/IP Services for OpenVMS Management | This manual describes how to configure and manage the TCP/IP Services product. |
| HP TCP/IP Services for OpenVMS Management Command Reference | This manual describes the TCP/IP Services management commands. |
| HP TCP/IP Services for OpenVMS Management Command Quick Reference Card | This reference card lists the TCP/IP management commands by component and describes the purpose of each command. |
| HP TCP/IP Services for OpenVMS UNIX Command Equivalents Reference Card | This reference card contains information about commonly performed network management tasks and their corresponding TCP/IP management and Tru64 UNIX command formats. |
| Compaq TCP/IP Services for OpenVMS ONC RPC Programming | This manual presents an overview of high-level programming using open 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. |
| HP TCP/IP Services for OpenVMS Guide to SSH | This manual describes how to configure, set up, use, and manage the SSH for OpenVMS software. |
| Compaq TCP/IP Services for OpenVMS Sockets API and System Services Programming | This manual describes how to use the Sockets API and OpenVMS system services to develop network applications. |
| Compaq TCP/IP Services for OpenVMS SNMP Programming and Reference | This manual describes the Simple Network Management Protocol (SNMP) and the SNMP application programming interface (eSNMP). It describes the subagents provided with TCP/IP Services, utilities provided for managing subagents, and how to build your own subagents. |
| HP TCP/IP Services for OpenVMS Tuning and Troubleshooting | This manual provides information about how to isolate the causes of network problems and how to tune the TCP/IP Services software for the best performance. It also provides information about using UNIX network management utilities on OpenVMS. |
| HP TCP/IP Services for OpenVMS Guide to IPv6 | This manual describes the IPv6 environment, the roles of systems in this environment, the types and function of the different IPv6 addresses, and how to configure TCP/IP Services to access the IPv6 network. |
For additional information about HP OpenVMS products and services, visit the following World Wide Web address:
http://www.hp.com/go/openvms |
For a comprehensive overview of the TCP/IP protocol suite, refer to the book Internetworking with TCP/IP: Principles, Protocols, and Architecture, by Douglas Comer.
HP welcomes your comments on this manual. Please send comments to either of the following addresses:
| Internet | openvmsdoc@hp.com |
| Postal Mail |
Hewlett-Packard Company
OSSG Documentation Group, ZKO3-4/U08 110 Spit Brook Rd. Nashua, NH 03062-2698 |
For information about how to order additional documentation, visit the following World Wide Web address:
http://www.hp.com/go/openvms/doc/order |
In the product documentation, the name TCP/IP Services means both:
In addition, please note that all IP addresses are fictitious.
The following conventions are used in the documentation.
| 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. |
| 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. |
| [Return] |
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:
|
|
.
. . |
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. |
| | | 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 type | Bold type represents the introduction of a new term. It also represents the name of an argument, an attribute, or a reason. |
| italic type | Italic type 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 TYPE | Uppercase type indicates a command, the name of a routine, the name of a file, or the abbreviation for a system privilege. |
| Example | This typeface indicates code examples, command examples, and interactive screen displays. In text, this type also identifies URLs, UNIX commands and pathnames, PC-based commands and folders, and certain elements of the C programming language. |
| - | 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. |
This chapter describes the new features of HP TCP/IP Services for OpenVMS Version 5.4.
TCP/IP Services V5.4 is supported on OpenVMS Alpha systems only. |
For more information about configuring and managing these services, see the HP TCP/IP Services for OpenVMS Management guide provided with the TCP/IP Services software.
Table 1-1 lists the new features of TCP/IP Services Version 5.4 and the sections that describe them.
| Section | Description |
|---|---|
| Section 1.1 | A new TCP/IP kernel provides performance scalability for symmetric multiprocessing (SMP) systems. |
| Section 1.2 | Secure shell (SSH) client and server. |
| Section 1.3 | Secure Socket Layer (SSL) for POP. |
| Section 1.4 | IP address failover. |
| Section 1.5 | Software update and new programming examples using IPv6 APIs. |
| Section 1.6 | BIND server Version 9.2.1. |
| Section 1.7 | INET driver performance enhancements. |
| Section 1.8 | NFS server performance enhancements. |
| Section 1.9 | TELNET server performance enhancements. |
| Section 1.10 | BG device creation enhancement. |
| Section 1.11 | Fast BG device creation and deletion. |
| Section 1.12 | Updated standard kernel. |
| Section 1.13 | Support for TCPDUMP utility. |
The TCP/IP kernel has been modified to provide increased performance on symmetric multiprocessing (SMP) systems.
This complete redesign of the TCP/IP kernel provides enhanced performance on SMP systems by removing CPU contention among users. The new kernel uses a dynamic spinlock to lock the main internal database. All processing that requires locking is directed to a designated TCP/IP CPU, thus eliminating CPU contention with other CPU users. Essentially, network I/O becomes a series of asynchronous, transaction-based operations.
Be aware that implementations of the scalable kernel in future versions of TCP/IP Services may differ from the way it is described here. Always consult the current documentation. |
To enable the scalable kernel, add the following lines to the SYS$MANAGER:SYLOGICALS.COM command procedure:
$ ! ONLY the argument "PERF=ALL" is supported. $ ! Other values may cause unpredictable results $ ! to disable scalable kernel support, comment out next line and reboot. $ DEFINE/SYSTEM/EXECUTIVE TCPIP$STARTUP_CPU_IMAGES "PERF=ALL" |
If TCP/IP Services has already been started, you must reboot the system after you make this change to the SYLOGICALS.COM file.
Although the scalable kernel runs on single processor systems, its greatest benefits are derived from its use on symmetric multiprocessor (SMP) systems.
When the scalable kernel is enabled, the following messages are displayed when TCPIP$STARTUP.COM is executed:
%TCPIP-I-INFO, PERF cpu-specific image SYS$LOADABLE_IMAGES:TCPIP$BGDRIVER_PERF.EXE selected %TCPIP-I-INFO, PERF cpu-specific image SYS$LOADABLE_IMAGES:TCPIP$INTERNET_SERVICES_PERF.EXE selected %TCPIP-I-INFO, PERF cpu-specific image SYS$SYSTEM:TCPIP$INETACP_PERF.EXE selected %TCPIP-I-INFO, PERF cpu-specific image SYS$LOADABLE_IMAGES:TCPIP$TNDRIVER_PERF.EXE selected |
To verify that the scalable kernel is enabled, use the TCP/IP
management command SHOW VERSION/ALL. The value of the
TCPIP$STARTUP_CPU_IMAGES logical name is displayed. Images pertinent to
the scalable kernel will have a _PERF suffix. Also, the image
identification will have a PF suffix.
1.1.2 Restrictions on Using the Scalable Kernel
When you enable the scalable kernel, be aware of the following:
This release includes the Secure Shell (SSH) client and server, providing secure login, remote command execution, and file transfer. This implementation is based on SSH2 software from SSH Communications Security Corp., Version 2.4.1.
If the TCP/IP Services V5.3 Early Adopter's Kit (EAK) for SSH for OpenVMS is installed on the system, you must use the PCSI command PRODUCT REMOVE to remove the EAK before you install TCP/IP Services V5.4. |
The SSH server allows:
For information about configuring, managing, and using SSH for OpenVMS, refer to the HP TCP/IP Services for OpenVMS Guide to SSH.
For restrictions on the use of this version of SSH for OpenVMS, see
Section 3.5.
1.3 Secure POP
SSL (Secure Socket Layer) is supported for POP (Post Office protocol), providing secure retrieval of mail.
The secure POP server accepts connections on port 995. Secure POP encrypts passwords, data, and POP commands and is compatible with clients that use SSL, such as Microsoft Outlook.
To use this feature, you must download the HP SSL kit for OpenVMS Alpha from:
http://www.openvms.compaq.com/openvms |
Select "Security Products."
If the HP SSL software is not installed, the POP server will communicate in non-SSL mode.
For information about configuring and managing Secure POP, see the HP TCP/IP Services for OpenVMS Management guide.
The SSL logical names are defined by the SSL startup procedure.
Therefore, if you have POP configured to use SSL logical names to
locate the certificate and key files, you must ensure that the SSL
startup procedure is run before the TCP/IP Services startup procedure.
1.4 failsafe IP
The failSAFE IP feature provides IP address failover capability for multiple interfaces on a host or a cluster.
If you have installed the TCP/IP Services V5.3 Early Adopter's Kit (EAK) for failSAFE IP, you must use the PCSI command PRODUCT REMOVE to remove the EAK before you install TCP/IP Services V5.4. |
For more information about configuring and managing failSAFE IP, see the HP TCP/IP Services for OpenVMS Management guide.
For information about restrictions on using this version of failSAFE
IP, see Section 3.2.
1.5 IPv6 Enhancements
The following sections describe updates and enhancements to IPv6
functionality.
1.5.1 IPv6 DNS Domain Name and Address Registration
New with this release, the TCPIP$ND6HOST process is capable of registering the host's domain name and address in the DNS.
The TCPIP$ND6HOST process receives and processes IPv6 Router Advertisement (RA) packets of the Neighbor Discovery Protocol. This enables a system to autoconfigure itself without manual intervention. With this version of TCP/IP Services, you can also enable DNS registration.
To enable host name and address registration, enter the following command:
$ DEFINE /SYSTEM TCPIP$ND6D_ENABLE_DDNS 1 |
The domain name to be registered is obtained using the gethostname() call.
To update the zone, TCPIP$ND6HOST sends dynamic updates to the primary master name server. The name of the primary master name server is stored in the MNAME field of the SOA record for a zone. To determine the master name server, TCPIP$ND6HOST sends a query for the zone's SOA record to the name server specified in the DNS resolver configuration. To display the DNS resolver configuration information, use the TCP/IP management command SHOW NAME.
To make use of this feature, you must enable dynamic updates. By default, dynamic updates are rejected by DNS servers. For information about allowing dynamic updates, see the BIND Chapter of the HP TCP/IP Services for OpenVMS Management guide.
| Next | Contents |