[an error occurred while processing this directive]

HP OpenVMS Systems Documentation
Content starts here

HP TCP/IP Services for OpenVMS

Release Notes

March 2010

This document describes the new features and changes introduced with Version 5.7 of the HP TCP/IP Services for OpenVMS software product.

Revision/Update Information: This is an updated document.

Software Version: HP TCP/IP Services for OpenVMS Version 5.7

Operating Systems: OpenVMS Version 8.4 for Integrity servers

OpenVMS Alpha Version 8.4





Hewlett-Packard Company

Palo Alto, California

© Copyright 2010 Hewlett-Packard Development Company, L.P.

Confidential 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 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.

Intel and Itanium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.

UNIX is a registered trademark of The Open Group.

The HP TCP/IP Services for OpenVMS documentation is available on CD-ROM.

Contents

Preface

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 Integrity server systems. This document describes the latest release of the HP TCP/IP Services for OpenVMS 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.

Intended Audience

These release notes are intended for experienced OpenVMS and UNIX® system managers and assume a working knowledge of OpenVMS system management, TCP/IP networking, TCP/IP terminology, and some familiarity with the TCP/IP Services product.

Document Structure

These release notes are organized into the following chapters:

  • Chapter 1 describes new features and special changes to the software that enhances its observed behavior.
  • Chapter 2 describes changes to the installation, configuration, and startup procedures, and includes other related information that is not included in the HP TCP/IP Services for OpenVMS Installation and Configuration manual.
  • Chapter 3 describes information about problems and restrictions, and includes notes describing changes to particular commands or services.
  • Chapter 4 describes problems identified in previous versions of TCP/IP Services that have been fixed.
  • Chapter 5 describes updates to information in the TCP/IP Services product documentation.

Related Documents

Table 1 lists the documents available with this version of TCP/IP Services.

Table 1 TCP/IP Services Documentation
Manual Contents
HP 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 UNIX command formats.
HP 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.
HP TCP/IP Services for OpenVMS Sockets API and System Services Programming This manual describes how to use the Berkeley Sockets API and OpenVMS system services to develop network applications.
HP 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, see: 


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.

Reader's Comments

HP welcomes your comments on this manual. Please send comments to openvmsdoc@hp.com.

How to Order Additional Documentation

For information about how to order additional documentation, see: 


http://www.hp.com/go/openvms/doc/order

Conventions

In the product documentation, the name TCP/IP Services means any of the following:

  • HP TCP/IP Services for OpenVMS Alpha
  • HP TCP/IP Services for OpenVMS Integrity servers

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:
  • Additional optional arguments in a statement have been omitted.
  • The preceding item or items can be repeated one or more times.
  • 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.
| 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.

Chapter 1
New Features and Behavioral Enhancements

This chapter describes the new features of TCP/IP Services Version 5.7 as well as behavioral enhancements.

Note
TCP/IP Services Version 5.7 is supported on OpenVMS Alpha and OpenVMS for Integrity servers systems only. On VAX systems, use TCP/IP Services Version 5.3.

To use TCP/IP Services Version 5.7, you must upgrade to OpenVMS Version 8.4 or higher.

For information about installing and configuring TCP/IP Services, see the HP TCP/IP Services for OpenVMS Installation and Configuration guide.

1.1 New features

Table 1-1 lists the new features of TCP/IP Services Version 5.7 and the sections that describe them.

Table 1-1 TCP/IP Services for OpenVMS, New Features
Feature Section Description
Packet Processing Engine 1.1.1 This release includes Packet Processing Engine, a CPU for processing TCP/IP that increases the performance efficiency.
FTP Anonymous Light 1.1.2 This release includes FTP Anonymous Light, used for restricting user access for a particular set of directories.

1.1.1 Packet Processing Engine

TCP/IP Packet Processing Engine (PPE) is modeled on the OpenVMS Dedicated Lock Manager. If you are familiar with Dedicated Lock Manager, you will only need to learn the different methods used to manage TCP/IP PPE.

TCP/IP runs on a single CPU, which is normally shared with other processes. However, some system loads result in near saturation of the TCP/IP CPU and causes TCP/IP to become a system-wide bottleneck. By dedicating a CPU for processing TCP/IP, a significant performance efficiency can be achieved, but, at the cost of dedicating a CPU for TCP/IP.

Note
Since TCP/IP PPE is recommended only in environments where the TCP/IP CPU is near saturation, dedicating a CPU to TCP/IP is a mere formality; except with significant payback.

Also, note that TCP/IP PPE can be dynamically enabled and disabled. System administrator can dynamically change the state of the TCP/IP PPE to suit the required load.

1.1.1.1 Configuring PPE

This section describes the hardware and software configuration required to configure PPE.

Hardware configuration

TCP/IP PPE will run only on systems with more than one active CPU. If TCP/IP PPE was running and the configuration changes such that there is only one active CPU remaining, the TCP/IP PPE becomes dormant.

Because, TCP/IP PPE dedicates an entire CPU for processing TCP/IP, it is recommended that TCP/IP must be enabled only on systems with a large number of CPUs, and only if the current TCP/IP CPU is nearing saturation.

Software configuration

For optimum performance, a CPU must be dedicated to PPE.

Normally, the TCP/IP BG0: driver shares the CPU with other fastpath drivers and processes. However, to achieve the best results with TCP/IP PPE, it is necessary to configure BG0: to be the only driver using the nominated CPU; all other fastpath drivers must be moved to other CPUs.

If TCP/IP PPE is running and other drivers are associated with the same CPU as BG0:, it results in suboptimal performance for both drivers.

Sample configuration

  1. Configure the BG driver to be dedicated to CPU 3. For optimum results, ensure that no other fastpath devices share CPU 3.
    To examine the fastpath devices that are using CPU 3, execute the following: 


            $ SHOW FASTPATH
  2. If other fastpath drivers are assigned to that CPU, move them to a different CPU. For example, if the PEA0: device is assigned to CPU 3, move it to another CPU by executing the following: 


            $ SET DEVICE PEA0 /PREF=5  ! move PEA0 to CPU 5.
  3. Assign TCP/IP BG0: device to CPU 3 by executing the following: 


            $ SET DEVICE BG0/PREF=3
  4. Verify that BG0: is the only fastpath driver assigned to CPU 3 by executing the following: 


            $ SHOW FASTPATH/CPU=3

1.1.1.2 Managing TCP/IP PPE

TCP/IP PPE is managed using the SYSCONFIG subsystem. To manage the TCP/IP PPE, complete the following steps:

Dynamically enable or disable PPE

  1. To use sysconfig, at the DCL command line, execute the following: 


            $ @SYS$MANAGER:TCPIP$DEFINE_COMMANDS
  2. To examine the current state of PPE, execute the following: 


            $ SYSCONFIG -q INET PPE_ENABLE
  3. If the ppe_enable attribute is 0, TCP/IP PPE is disabled. To enable TCP/IP PPE, execute the following: 


            $ SYSCONFIG -r INET PPE_ENABLE=1

    Note
    Although, the "ppe_enable" attribute may indicate that TCP/IP PPE is enabled, you must also verify that PPE is running. As described in Section 1.1.1, PPE does not run if the number of active CPUs drops to 1. To verify that TCP/IP PPE is running, execute the following: 


            $ SHOW SYSTEM/PROC=TCPIP$INETPPE


    An output similar to the following is displayed: 


    OpenVMS V8.4 on node GRYFFI  30-AUG-2009 13:32:03.22  Uptime  0 13:00:21 
 
  Pid     Process Name   State  Pri   I/O       CPU         Page flts  Pages 
22000438  TCPIP$INETPPE  CUR 3  63    10   0 12:49:32.25        91      108


    The priority of this process is set to 63. This ensures that TCP/IP PPE is not rescheduled and no other process will use CPU 3.

    You can also use the following command to verify that TCP/IP PPE is running: 


            $ MONITOR MODES/CPU=3 ! it will be 100% in Kernel Mode

    To dynamically disable TCP/IP PPE, execute the following: 


            $ SYSCONFIG -r INET PPE_ENABLE=0

    After a brief moment, the monitor display changes to show the CPU load distribution amongst the various modes.

Enabling TCP/IP PPE at system startup

To enable TCP/IP PPE after TCP/IP has started, use one of the following methods:

  • Add the following to the TCPIP$ETC:SYSCONFIGTAB.DAT file: 


            inet: 
                ppe_enable=1   # Enable TCP/IP PPE

    When TCP/IP is loaded, the ppe_enable flag will also be set.
    OR
  • Add the SYSCONFIG command to the startup procedure. It is recommended that SYS$STARTUP:TCPIP$SYSTARTUP.COM must be modified with the following: 


            $ @SYS$MANAGER:TCPIP$DEFINE_COMMANDS 
        $ SYSCONFIG -r INET PPE_ENABLE=1  ! Enable TCP/IP PPE

1.1.1.3 Monitoring PPE

This section describes how to monitor PPE.

When PPE is disabled, the performance of the TCP/IP CPU can be monitored with following command: 


 $ MONITOR MODES/CPU=xx  ! where xx is the TCP/IP CPU Id

When PPE is enabled, the TCP/IP CPU runs 100% in the kernel mode, because the CPU is dedicated entirely to TCP/IP. Hence, the monitor command is not useful when PPE is running.

This section describes how to collect statistics when PPE is running. Also note that this method provides a much finer granularity and can also be used when PPE is disabled. This approach also helps you compare performance when PPE is enabled or disabled.

To gather statistics, enable profiling by executing the following: 


        $SYSCONFIG -r INET PROFILING=1

Note that with profiling enabled, there is a small processing overhead to collect the statistics. It is recommended to enable profiling only while gathering statistics. With profiling enabled, the statistics can be gathered using the TCPMON command as follows: 


 $ SET COMMAND TCPIP$EXAMPLES:TCPIP$TCP_MON 
 $ TCPMON/SHOW=INET

For more information on how to use the TCPMON command, see the help by executing the following: 


 $ HELP/LIBRARY=TCPIP$EXAMPLES:TCPIP$TCP_MON TCPMON

You can also use the Performance Data Collector (TDC) to monitor PPE. TDC can automatically gather the PPE statistics. For more information about TDC, visit the Web site at: 


http://h71000.www7.hp.com/openvms/products/tdc/index.html

Next Contents