 |
HP TCP/IP Services for OpenVMS
HP TCP/IP Services for OpenVMS
Management Command Reference
Order Number:
AA--PQQGJ--TE
September 2003
This manual describes the commands used for configuring and managing
the HP TCP/IP Services for OpenVMS product.
Revision/Update Information:
This manual supersedes the Compaq TCP/IP Services for OpenVMS Management Command Reference, Version 5.1.
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
© Copyright 2003 Hewlett-Packard Development Company, L.P.
UNIX® is a registered trademark of The Open Group.
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.
ZK6527
The HP TCP/IP Services for OpenVMS documentation is available on CD-ROM.
This document was prepared using DECdocument, Version V3.3-1e.
Preface
The HP TCP/IP Services for OpenVMS product is the HP implementation of the TCP/IP
networking protocol suite and internet services for HP OpenVMS Alpha
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 describes the TCP/IP Services management commands. Use it in
conjunction with the HP TCP/IP Services for OpenVMS Management manual, which describes the
management tasks.
Refer to the HP TCP/IP Services for OpenVMS Installation and Configuration manual for information about installing,
configuring, and starting this product.
Intended Audience
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.
If you are not familiar with the TCP/IP Services product, please review
the Compaq TCP/IP Services for OpenVMS Concepts and Planning manual before using this manual to configure and
manage TCP/IP components.
Document Structure
This manual contains the following chapters:
- Chapter 1 introduces the management control program.
- Chapter 2 provides command descriptions for each management
command.
Related Documents
Table 1 lists the documents available with this version of
TCP/IP Services.
Table 1 TCP/IP Services Documentation
| 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 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.
|
|
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 RPCs). This manual also
describes the RPC programming interface and how to use the RPCGEN
protocol compiler to create applications.
|
|
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.
|
|
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.
|
|
HP TCP/IP Services for OpenVMS Guide to SSH
|
This manual describes the way Secure Shell (SSH) is implemented on
TCP/IP Services. It describes how to configure, manage, and use the
optional services that are protected by secure shell security.
|
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.
Reader's Comments
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
|
How to Order Additional Documentation
For information about how to order additional documentation, visit the
following World Wide Web address:
http://www.hp.com/go/openvms/doc/order
|
Conventions
IP addresses in this manual are fictitious. The following conventions
may be used in this manual.
|
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).
|
|
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.
|
|
UPPERCASE TYPE
|
Uppercase type indicates a command, the name of a routine, the name of
a file, or the abbreviation for a system privilege.
|
|
-
|
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
Using TCP/IP Services Management Commands
The TCP/IP Services product provides a management command interface you
use to configure and manage the software. These commands let you
perform the following tasks:
- Configure and reconfigure components
- Modify parameters of components
- Configure customer-developed services
- Enable and disable running components
- Monitor the running software
1.1 Entering Commands
To start the management control program, type TCPIP at the DCL prompt.
For example:
At the TCPIP> prompt, you can enter commands described in this
manual or display online help. Type EXIT to exit the management control
program, or press Ctrl/C to abort a command.
Help is also available at the DCL prompt by typing HELP TCPIP_SERVICES.
Note
The word command refers to commands for the
TCP/IP Services software. DCL commands and UNIX commands are explicitly
identified.
|
Table 1-1 provides guidelines for using management control program
commands.
Table 1-1 Management Command Guidelines
| Element |
Guideline |
|
Address formats
|
Some commands require that you specify one of the following kinds of
addresses:
- IP
- Ethernet
- FDDI
- Token Ring
- Hardware
Be sure to use the appropriate format. The following examples
illustrate an IP address, an Ethernet address, and a hardware address,
respectively.
TCPIP> SET HOST CROW /ADDRESS=1.2.3.4
TCPIP> SET ARP AA-BB-04-05-06-07 CONDOR
TCPIP> SET BOOTP MACAW /HARDWARE=ADDRESS=08-dd-ff-2a-23-21
|
|
Default
|
Refers to the command's behavior if optional qualifiers are omitted.
|
|
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.
|
|
Service names
|
To specify a lowercase or mixed-case service name, enclose it in
quotation marks. Service names are limited to 16 characters. Use only
the following characters in a service name:
- Uppercase and lowercase alphabetic characters
- Numerals
- Dollar sign ($)
- Underscore (_)
Do not define a service name equivalent to one of the TCP/IP
Services for OpenVMS components (for example, do not define a service
name BIND or TCPIP$BIND). In addition, the service name
CUSTOMER_SERVICE is reserved by HP.
|
|
Host names and IP addresses
|
To specify a host or network name on a command line, you can enter
either the host's name or the host's IP address.
|
|
Keywords
|
You can abbreviate commands to the fewest number of characters, usually
four, that identify the command. The following command lines, for
example, have identical meanings:
TCPIP> SH SE NFS/FU/PER
TCPIP> SHOW SERVICE NFS /FULL /PERMANENT
Command examples shown in this manual are expressed using full
command and qualifier names for clarity.
|
|
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, the following qualifiers are the same:
/qualifier=(option_a:value1,option_b:value2,value3)
/qualifier=(option_a=value1),(option_b=value2,value3)
Wildcards are valid unless otherwise stated. A space between
multiple elements is optional unless otherwise stated.
|
|
Numeric values
|
Unless otherwise stated, all numeric values are decimal. Values are
indicated by either a preceding equals sign (=) or a colon (:). For
example:
TCPIP> SET NAME_SERVICE /SERVER:(SORA,JACANA,PARROT) -
_TCPIP> /ACCEPT:(HOSTS:JACANA,JAY,JUNCO,999.20.40.3)
|
|
Quotation marks
|
In command lines, enclose the following in quotation marks:
- Lowercase and mixed-case names to be stored in a database with the
exact case preserved
- Directory and file specifications containing a slash (/)
- Uppercase options specified with UNIX commands
Consider these examples:
- To specify a path, enclose it in quotation marks:
TCPIP> MAP "/usr/songbirds/canary" CANARY$DUA2:
- To specify host names using lowercase letters when you create a
proxy entry in the database:
TCPIP> ADD PROXY COUSINS /GID=10 /UID=40 -
_TCPIP> /HOST=("raven","crow","rook","daw")
Note the use of the DCL command-line continuation character ( - )
that allows you to continue a long command on the next line.
- To specify a lowercase host name when adding the host to the hosts
database, use these commands:
TCPIP> SET HOST "eaglet" /ADDRESS = 128.33.22.1
TCPIP> SHOW HOST EAGLET
Note that DCL interprets all input as uppercase unless you enclose
it in quotation marks. Therefore, you must use quotation marks to enter
the host name in lowercase in the hosts database. To display
information about a host, you can enter either uppercase or lowercase
characters.
- When entering a lowercase or mixed-case service name in a command,
enclose it in quotations marks. For example:
TCPIP> SET SERVICE "hello" ...
- When entering an option in uppercase in a UNIX command, enclose the
option in quotation marks. For example:
TCPIP> sysconfig "-Q" inet
|
|
UNIX commands
|
Follow UNIX syntax and case rules when entering UNIX commands at the
DCL and TCPIP> prompts. For example, enter the
ifconfig
command in lowercase letters:
TCPIP> ifconfig
options
When entering UNIX commands at the DCL or TCPIP> prompt, enclose
uppercase options in quotation marks. For example:
$ TCPIP> sysconfig "-Q" inet
You can abbreviate commands, as shown in the following example. The
abbreviation must be unique through the first four characters.
TCPIP> ifco
options
If the abbreviation entered is not unique, an error message will
advise you to supply more characters. In the following example, the
SYSCONFIG command cannot be abbreviated because of the SYSCONFIGDB
command.
TCPIP> sysc -q
%CLI-W-ABVERB, ambiguous command verb - supply more characters
|
|
Wildcards
|
If you specify a wildcard (an asterisk [*]) on a command line, you are
asked for confirmation before the command executes. For example:
TCPIP> REMOVE PROXY *
VMS User_name Type User_ID Group_ID Host_name
GRACKLE N 269 48 MAPLE
Remove? [N]:
To change this default behavior (so that you are not asked to
confirm), use the /NOCONFIRM qualifier with the command.
|
1.1.1 Setting Configuration Parameters
Some commands allow you to enter information in the database; others
modify only the run-time parameters. Table 1-2 shows the SET
commands that affect one or the other.
Table 1-2 SET Commands
| 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 ROUTE
|
SET ROUTE
|
|
SET SERVICE
|
|
Note that the SET ROUTE command affects both the permanent and dynamic
routing databases.
|
