DIGITAL TCP/IP Services for OpenVMSManagement Command ReferenceOrder Number: AA-PQQGG-TE
January 1999
This manual describes the commands used for configuring and managing the DIGITAL TCP/IP Services for OpenVMS product. Revision Information: This is a revised manual. Operating Systems: OpenVMS Alpha Versions 7.1, 7.2 OpenVMS VAX Versions 7.1,7.2 Software Version: DIGITAL TCP/IP Services for OpenVMS Version 5.0
January 1999 Compaq Computer Corporation makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description. Possession, use, or copying of the software described in this publication is authorized only pursuant to a valid written license from Compaq or an authorized sublicensor. Compaq conducts its business in a manner that conserves the environment and protects the safety and health of its employees, customers, and the community. © Compaq Computer Corporation 1999. All rights reserved. The following are trademarks of Compaq Computer Corporation: Alpha, Compaq, DIGITAL, DIGITAL UNIX, LAT, OpenVMS, OpenVMS, OpenVMS Cluster, PATHWORKS, POLYCENTER, VAX, VAX DOCUMENT, VAXcluster, VMS, and the DIGITAL logo. The following are third-party trademarks: JOIN is a trademark of Competitive Automation, Inc. MS-DOS is a registered trademark of Microsoft Corporation. OSF/1 is a registered trademark of Open Software Foundation, Inc. PostScript is a registered trademark of Adobe Systems, Inc. Sun, NFS, and PC-NFS are registered trademarks of Sun Microsystems, Inc. UNIX is a registered trademark of UNIX System Laboratories, Inc., a wholly-owned subsidiary of Novell, Inc. All other trademarks and registered trademarks are the property of their respective holders.
ZK6527
PrefaceThe DIGITAL TCP/IP Services for OpenVMS product is Compaq's implementation of the TCP/IP networking protocol suite and internet services for OpenVMS Alpha and OpenVMS VAX systems. A layered software product, DIGITAL TCP/IP Services for OpenVMS provides a comprehensive suite of functions and applications that support industry-standard protocols for heterogeneous network communications and resource sharing. This manual describes the DIGITAL TCP/IP Services for OpenVMS management commands. Use it in conjunction with the DIGITAL TCP/IP Services for OpenVMS Management manual, which describes the management tasks. Intended AudienceThis manual is for experienced OpenVMS and/or UNIX system managers and assumes a working knowledge of TCP/IP networking, TCP/IP terminology, and some familiarity with the DIGITAL TCP/IP Services for OpenVMS product. If you are not familiar with the DIGITAL TCP/IP Services for OpenVMS product, please review the DIGITAL TCP/IP Services for OpenVMS Concepts and Planning before using this manual to configure and manage TCP/IP components. New and Changed FeaturesDIGITAL TCP/IP Services for OpenVMS Version 5.0 provides a new kernel based on the IPv4 kernel ported from DIGITAL UNIX Version 4.0D. 1 Other new features include:
Changes to this document include:
Document StructureThis manual contains two chapters.
Related DocumentationTable 1 lists the documents available with this version of DIGITAL TCP/IP Services for OpenVMS.
For additional information about the DIGITAL TCP/IP Services for OpenVMS products and services, access the DIGITAL OpenVMS World Wide Web site at the following URL:
You might find the Internetworking with TCP/IP: Principles, Protocols, and Architecture, by Douglas Comer useful if you are looking for a comprehensive overview of the TCP/IP protocol suite. TerminologyDIGITAL TCP/IP Services for OpenVMS Version 5.0 completes the change initiated several releases ago when the product name changed from "ULTRIX Connection (UCX)" to "DIGITAL TCP/IP Services for OpenVMS." To complete this change, the identifier "UCX" is replaced with "TCPIP" in the following:
DIGITAL TCP/IP Services for OpenVMS is used to describe both:
The auxiliary server is the DIGITAL TCP/IP Services for OpenVMS implementation of the UNIX internet daemon (inetd). NFS is the DIGITAL TCP/IP Services for OpenVMS implementation of the NFS protocols, including the NFS server, the NFS client, and PC-NFS. TN3270 means the TELNET client software that emulates IBM 3270 model terminals. The term UNIX refers to the DIGITAL UNIX operating system. DIGITAL UNIX is fully compatible with Version 4.3 and Version 4.4 of the Berkeley Software Distribution (BSD). Host and node both mean a system connected to an internet. The term Internet refers to the global interconnection of networks, as defined by RFC 1208, which consists of large networks using TCP/IP to provide universal connectivity, reaching the Defense Advanced Projects Research Internet, MILNET, NSFnet, CERN, and many worldwide universities, government research labs, military installations, and business enterprises. The term internet refers to private interconnected networks that use TCP/IP to connect together and function as one, virtual network. AcronymsFor a complete list of acronyms used throughout this and other manuals in the DIGITAL TCP/IP Services for OpenVMS documentation set, see DIGITAL TCP/IP Services for OpenVMS Management guide. ConventionsAll IP addresses in this book represent fictitious addresses. The following conventions apply to this book.
Reader's CommentsCompaq welcomes your comments on this manual. Print or edit the online form SYS$HELP:OPENVMSDOC_COMMENTS.TXT and send us your comments by:
How to Order Additional DocumentationVisit the OpenVMS Documentation World Wide Web site at the following URL to learn how to order additional documentation:
If you need help deciding which documentation best meets your needs, call 800-DIGITAL (800-344-4825). <RECTO_HEAD>(CANCEL_H) <VERSO_HEAD>(CANCEL_H)
Chapter 1
|
$ TCPIP |
At the TCPIP> prompt, enter the commands described in this manual or display online help. Type EXIT to exit the management control program or Ctrl/C to abort a command.
Help is also available at the OpenVMS prompt by entering HELP TCPIP_SERVICES.
The word command refers to commands for the DIGITAL TCP/IP Services for OpenVMS product. DCL commands and UNIX commands are so identified when needed. |
Table 1-1 describes the guidelines you should follow when entering management control program commands.
| Guideline | Description |
|---|---|
| Abbreviating Keywords | Abbreviate command keywords to the fewest number of characters, usually four, that identify the command. |
| Using Quotation Marks |
On command lines, enclose the following in quotation
marks ( " " ):
Consider these examples:
|
| Entering Host Names and IP Addresses | To specify a host or network on a command line, you can enter either the host's name or the host's IP address. |
| File and Directory Names | When you specify OpenVMS files, follow all OpenVMS file specification rules. Likewise, when you specify UNIX files, follow all UNIX file specification rules. |
| Multiple Values |
To specify multiple host names, addresses, or options for parameters
and qualifiers, be sure to separate elements with commas and enclose
the entire list in parentheses.
Wildcards are valid unless otherwise stated. A space between
multiple elements is optional unless otherwise stated. For example,
is the same as
|
| Number Values | Unless otherwise stated, all shown values are decimal. |
| Address Formats |
Some commands require that you specify one of the following kinds of
addresses:
Be sure to use the appropriate format. The examples below
illustrate an IP address, a hardware address, and an Ethernet address.
|
| UNIX commands |
Follow UNIX syntax and case rules when entering UNIX commands at the
TCPIP> prompt. For example, enter:
TCPIP> ifconfig options not
|
| Using Wildcards |
If you specify a wildcard on a command line, you will be asked for
confirmation before the command executes.
Change this default behavior with the /NOCONFIRM qualifier. For
example:
Most SHOW commands default values to *. DELETE commands require that you supply a parameter. |
| Valid Values | Most management commands accept any number value you might enter. Specify values appropriate to your environment. |
For some components, you can enter information only in a permanent database and, for others, only in dynamic memory. In addition, DIGITAL TCP/IP Services for OpenVMS can store parameter settings and other configuration information for some of the software in both locations. Table 1-2 shows the SET commands that affect only one or the other.
| Modify Permanent Database Files | Modify Dynamic Memory |
|---|---|
| SET BOOTP | SET ARP |
| SET CONFIGURATION | SET COMMUNICATION |
| SET HOST | SET INTERFACE |
| SET MX_RECORDS | SET NAME_SERVICE |
| SET NETWORK | SET NFS_SERVER |
| SET CONTAINER | SET PROTOCOL |
| SET SERVICE |
The SET ROUTE command works on both the permanent and dynamic routing
databases.
1.1.2 Modifying Parameters
Unlike the other databases, which have similar objects, the configuration database holds diverse initialization information for various DIGITAL TCP/IP Services for OpenVMS components.
All the initialization information is node-specific except for TIME and SNMP. This information is identified by the SYSGEN parameter SCSNODE. If you change your node's name after you configure DIGITAL TCP/IP Services for OpenVMS, the startup information, by default, will not be seen by the startup procedure or by the management software.
To see the configuration that is paired to the original node name, use the /ON qualifier, which is available with all the configuration commands. To copy node-specific startup information from one node to another, use the COPY CONFIGURATION command.
The following commands modify the configuration database:
The CREATE commands create the following kinds of files:
| Next | Contents | Index |
|
|
|
|
Copyright © Compaq Computer Corporation 1998. All rights reserved. Legal |
6527PROFILE.HTML
|
|