Order Number: BA548-90006
This manual describes how to configure and manage the TCP/IP Services product.
Revision/Update Information: This manual supersedes Compaq TCP/IP Services for OpenVMS Management, Version 5.4.
Software Version: HP TCP/IP Services for OpenVMS Version 5.6
Operating System:
HP OpenVMS Alpha Version 8.3
HP OpenVMS I64 Version 8.3
Hewlett-Packard Company Palo Alto, California
© 2006 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.
UNIX is a registered trademark of The Open Group.
Microsoft, Windows and Windows NT are US registered trademarks of Microsoft Corporation.
ZK6526
The HP TCP/IP Services for OpenVMS documentation is available on CD-ROM.
| Contents | Index |
The HP TCP/IP Services for OpenVMS product is the HP implementation of the TCP/IP networking 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.
This manual provides system and network managers with information needed for the day-to-day management of the TCP/IP Services software product. This manual is best used in conjunction with the HP TCP/IP Services for OpenVMS Management Command Reference manual.
See the HP TCP/IP Services for OpenVMS Installation and Configuration manual for information about installing, configuring, and starting this product.
This manual is for experienced OpenVMS and UNIX system managers and assumes a working knowledge of OpenVMS system management, TCP/IP networking, and TCP/IP terminology.
This manual contains seven parts, as follows:
| Part 1 | Describes how to configure network interfaces, how to set up serial lines, and how to configure and manage routing. |
| Part 2 | Describes how to set up and manage the BIND server, resolver, and load broker components. |
| Part 3 |
Describes how to set up the following network services:
DHCP server |
| Part 4 |
Describes how to configure network applications that let users send and
receive electronic mail from the internet, establish login sessions
with a remote host, and transfer files. These network applications
include:
TELNET |
| Part 5 | Describes how to configure, use, and manage the components that enable transparent network file sharing, including the NFS server and NFS client. |
| Part 6 | Describes how to configure and manage network printing services, including LPD/LPR, TELNETSYM, and PC-NFS. |
| Part 7 |
Provides appendixes that:
|
Table 1 lists the documents available with this version of TCP/IP Services.
| 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 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, 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. |
| HP TCP/IP Services for OpenVMS Management |
This manual describes how to configure and manage the TCP/IP Services
product.
Use this manual with the HP TCP/IP Services for OpenVMS Management Command Reference manual. |
| HP TCP/IP Services for OpenVMS Management Command Reference |
This manual describes the TCP/IP Services management commands.
Use this manual with the HP TCP/IP Services for OpenVMS Management manual. |
| 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 Sockets API and System Services Programming | This manual describes how to use the 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. |
| 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 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 6bone 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, you might find the book Internetworking with TCP/IP: Principles, Protocols, and Architecture, by Douglas Comer, useful.
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 |
The name TCP/IP Services means:
The name UNIX refers to the HP 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. |
| 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. |
Part 1 provides the information on how to get started after installing and configuring the TCP/IP Services software.
Part 1 includes the following chapters:
This chapter reviews information you need to get started with the TCP/IP Services software. Topics include:
This manual assumes you installed and configured TCP/IP Services software with the configuration procedure SYS$MANAGER:TCPIP$CONFIG.COM, as described in the HP TCP/IP Services for OpenVMS Installation and Configuration manual. This menu-driven procedure configures the software components you select or all of the TCP/IP Services software components. The "out-of-the-box" defaults are designed to get your system up and running as an internet host with minimal effort.
TCPIP$CONFIG creates the database files listed in Table 1-1.
| Database | File Name |
|---|---|
| BOOTP database | SYS$COMMON:[SYSEXE]TCPIP$BOOTP.DAT 1 |
| Configuration database | SYS$COMMON:[SYSEXE]TCPIP$CONFIGURATION.DAT |
| Export database | SYS$COMMON:[SYSEXE]TCPIP$EXPORT.DAT |
| Hosts database | SYS$COMMON:[SYSEXE]TCPIP$HOST.DAT |
| Networks database | SYS$COMMON:[SYSEXE]TCPIP$NETWORK.DAT |
| Proxy database | SYS$COMMON:[SYSEXE]TCPIP$PROXY.DAT |
| Routes database | SYS$COMMON:[SYSEXE]TCPIP$ROUTE.DAT |
| Services database | SYS$COMMON:[SYSEXE]TCPIP$SERVICE.DAT |
Logical names allow you to customize or modify component behavior. Logical names also point to directories, database files, and log files.
TCPIP$CONFIG defines the following logical names for the databases listed in Table 1-1:
Service-specific logical names should be defined while the service is not running. Always stop the service before defining logical names.
Most logical names require SYSTEM privileges in order to affect the service. You should use the /EXECUTIVE and /SYSTEM qualifiers on the DEFINE command line.
It is important to always use the standard, documented shutdown procedures to stop the services and to stop TCP/IP Services; otherwise, logical names may revert to their default definitions.
Many services reference service-specific configuration files. To specify different configuration options for the nodes in an OpenVMS cluster, you can modify service-specific logical name so that the configuration files are specific to each node. In clusters with a shared system disk, the default device (SYS$SYSDEVICE) is a cluster-common directory.
To specify node-specific configuration files, you can define the service-specific logical to reference a node-specific file. For example, on each node that requires node-specific customizations:
$ @SYS$STARTUP:TCPIP$service_SHUTDOWN.COM |
$ DEFINE/SYS/EXEC logical-name SYS$SPECIFIC:[directory]logical-name |
$ @SYS$STARTUP:TCPIP$service_STARTUP |
See individual component chapters in this manual for information on how
specific components use logical names.
1.1.2 Modifying Your Configuration
After the initial configuration, you may want to reconfigure existing components or configure new ones, disable and re-enable components, add hosts, reconfigure routing, and so forth.
When making any configuration modifications, HP recommends that you run the configuration procedure TCPIP$CONFIG again.
You cannot use TCPIP$CONFIG to set up SLIP or PPP lines. See Chapter 3 for more information. |
In some instances, TCPIP$CONFIG only partially configures a component (for example, when configuring a BIND name server). You may need to run additional setup programs or enter management commands to complete the configuration and fine-tune your environment.
Component-specific chapters in this manual describe additional configuration tasks and explain how to configure and manage specific components. These tasks may include:
The configuration procedure TCPIP$CONFIG saves configuration and initialization information in the file TCPIP$CONFIGURATION.DAT. You can modify the configuration dynamically or permanently, as follows:
To make changes take effect immediately and modify permanent settings, enter both the interactive SET and permanent SET CONFIGURATION commands.
The following commands permanently modify the configuration database:
Throughout this manual, all commands are assumed to be TCP/IP management commands. Any DCL commands that are mentioned are identified as such. For a full description of the TCP/IP management commands and a discussion of how to use them, see the HP TCP/IP Services for OpenVMS Management Command Reference manual. |
| Next | Contents | Index |