For some components, the TCP/IP Services management program
includes two kinds of configuration commands, those that
modify volatile memory, and those that modify the permanent
database files. Commands that modify volatile memory take effect
immediately, but may be overwritten when the TCP/IP Services
software is restarted. Commands that modify the permanent
database take effect after the TCP/IP Services software has been
restarted.
Those commands are listed in the following table.
Commands that modify Commands that modify the permanent
volatile memory database files
Not applicable SET CONFIGURATION [NO]BIND
SET COMMUNICATION SET CONFIGURATION COMMUNICATION
ENABLE [NO]SERVICE SET CONFIGURATION ENABLE [NO]SERVICE
SET [NO]INTERFACE SET CONFIGURATION [NO]INTERFACE
SET NAME_SERVICE SET CONFIGURATION [NO]NAME_SERVICE
UNMAP SET CONFIGURATION NOMAP
SET PROTOCOL SET CONFIGURATION PROTOCOL
Not applicable SET CONFIGURATION SMTP
Not applicable SET CONFIGURATION SNMP
START ROUTING SET CONFIGURATION START ROUTING
Whether permanent or volatile, the configuration information for
each pair of SET and SET CONFIGURATION commands is the same.
1 – BIND
Configures the BIND name server. Creates the BIND server
configuration file, which holds the following information:
o Cluster alias or aliases
o Server type (primary, secondary, or forwarding)
o Domains to be served
o Location from which the BIND server gets initial information
for lookups
You can configure the BIND server as follows:
o For one or more Internet domains
o As one kind of BIND server (primary, secondary, or forwarding)
o As multiple kinds of BIND servers
o On TCP/IP clusters for cluster load balancing
This command does not create a BIND 8.1 configuration. If you
want to take full advantage of the new features available
with the BIND 8.1 implementation, you should set up your BIND
environment by editing the TCPIP$BIND.CONF configuration file.
Refer to the HP TCP/IP Services for OpenVMS Management manual for
detailed instructions.
If you choose to configure your BIND environment with the
SET CONFIGURATION BIND command, you must enter the command
CONVERT/CONFIGURATION BIND before running BIND.
Related commands: SHOW CONFIGURATION BIND,
CONVERT /CONFIGURATION BIND
Format
SET CONFIGURATION [NO]BIND [ /CACHE=options ]
[ /[NO]CLUSTER=names ]
[ /FORWARDERS=options ]
[ /PRIMARY=options ]
[ /SECONDARY=options ]
1.1 – Restrictions
Requires SYSPRV or BYPASS privilege.
1.2 – Qualifiers
1.2.1 /CACHE
/CACHE=([NO]DOMAIN:do,[NO]FILE:file)
Optional. Default: None.
Specifies the cache server for the specified domain. Do not use
with /FORWARDERS. Use with /PRIMARY and /SECONDARY.
The cache tells the primary or secondary server how to use hints
to find the file. These hints let a server find a root name
server. With this ability, the server can answer requests even
if it does not have the information. You can use the following
options:
o DOMAIN keys to a particular record within a type.
NODOMAIN deletes the entry.
o FILE specifies the name of the hints file.
If you use /CACHE with no options:
o DOMAIN defaults to "." ("root").
o FILE defaults to NAMED.CA.
1.2.2 /CLUSTER
/CLUSTER=name
/NOCLUSTER=name
Required to configure cluster load balancing.
Identifies the name of a TCP/IP cluster as the first step to
setting up cluster load balancing.
For information about the remaining procedure, refer to the HP
TCP/IP Services for OpenVMS Management manual.
/NOCLUSTER=name deletes the specified name as a cluster load-
balancing host.
1.2.3 /FORWARDERS
/FORWARDERS=([NO]HOST:host)
Optional.
Specifies the forwarding server.
NOHOST deletes hosts.
1.2.4 /PRIMARY
/PRIMARY=([NO]DOMAIN:do,[NO]FILE:file)
Optional. Default: None.
Specifies the primary server for the specified zone. Multiple
primary servers are allowed if each is associated with a
different domain.
o DOMAIN keys to a particular domain.
NODOMAIN deletes the entry.
o FILE specifies the domain to be served.
If you do not specify a file, the default file name is created
from the value that you supply with the DOMAIN option.
NOFILE specifies that no file is created.
1.2.5 /SECONDARY
/SECONDARY=([NO]DOMAIN:do,[NO]FILE:file,[NO]HOST:host)
Optional. Default: None.
Specifies the secondary server for the specified zone. Multiple
secondary servers are allowed if each is associated with a
different domain.
o DOMAIN keys to a particular record within a type.
NODOMAIN deletes the entry.
o FILE specifies the name of the boot file.
If you do not specify a file, the default file name is created
from the value that you supply with the DOMAIN option.
NOFILE specifies that no file is created.
o HOST is a list of hosts from which the secondary server copies
the database file.
NOHOST deletes hosts from the host list.
1.3 – Examples
1.TCPIP> SET CONFIGURATION BIND -
_TCPIP> /PRIMARY=(DOMAIN:RHEA.LAB.UBIRD.EDU)
Configures the host as the primary server for domain
RHEA.LAB.UBIRD.EDU.
2.TCPIP> SET CONFIGURATION BIND -
_TCPIP> /SECONDARY=(DOMAIN:JACANA.LAB.UBIRD.EDU) -
_TCPIP> /SECONDARY=(FILE:JACANA.DB,HOST=MARSHY)
Configures the host as a secondary server for domain
JACANA.LAB.UBIRD.EDU and names the boot file JACANA.DB.
Omitting the file name would default to file JACANA_LAB_UBIRD_
EDU.DB.
3.TCPIP> SET CONFIGURATION BIND -
_TCPIP> /SECONDARY=(DOMAIN:0.192.IN-ADDR.ARPA,HOST:WEBBED)
Configures the host as a secondary server for the reverse
lookup domain for addresses that have the form 192.0.*.*.
The boot file name defaults to 0_192_IN-ADDR_ARPA.DB and the
host copies this file from the host WEBBED.
4.TCPIP> SET CONFIGURATION BIND /CACHE
Points the server to the cache file (NAMED.CA), which contains
hints about the root name servers.
2 – COMMUNICATION
Enters information into the configuration database to start the
IP, TCP, UDP, and INET_ACP software when the system starts up.
When TCP/IP Services starts up, this configuration overrides the
default settings.
Related commands: SHOW CONFIGURATION COMMUNICATION,
SET COMMUNICATION
Format
SET CONFIGURATION COMMUNICATION [ /ACCEPT=options ]
[ /DOMAIN=domain ]
[ /LOCAL_HOST=host ]
[ /PROXIES=n ]
[ /REJECT=options ]
2.1 – Restrictions
Requires OPER privilege.
2.2 – Qualifiers
2.2.1 /ACCEPT
/ACCEPT { =[NO]HOSTS=(hosts) | =[NO]NETWORKS=(networks) }
Optional. Default: All hosts and all networks.
Accepts communication from the hosts and networks specified.
Do not specify the same hosts or networks for both /ACCEPT and
/REJECT.
To delete an /ACCEPT entry, specify it again using the NOHOSTS or
NONETWORKS option.
Specify one of the following:
o [NO]HOSTS=hosts
Hosts that can access TCP/IP Services. Maximum is 32. For
example:
/ACCEPT=HOSTS=(host1_name,host2_name,host3_address)
o [NO]NETWORKS=networks
Networks that can access TCP/IP Services. Maximum is 16.
The syntax is:
NETWORKS=(net1[:net1mask],net2[:net2mask],...)
For each network, specify: network:[network_mask]. The network
mask is optional. (Default: class number of your network.
For example, the default for 11.200.0.0. is 255.0.0.0.). For
example:
/ACCEPT=NETWORKS=(net1_name,net2_addr,net3_addr:net3_mask)
2.2.2 /DOMAIN
/DOMAIN=domain
Optional.
Specifies your system's local domain. This qualifier requires
either SYSPRV or BYPASS privilege.
2.2.3 /LOCAL_HOST
/LOCAL_HOST=host
Optional.
Defines the following logical names for the local host:
o TCPIP$INET_HOST=host-name
This logical is always set with the primary host name, even if
the alias name was specified as host.
o TCPIP$INET_HOSTADDR=host-IP-address
If the local host has multiple IP addresses, this logical
name is set with a name for each address, called TCPIP$INET_
HOSTADDRn, where n is a number starting at 2.
This qualifier requires either SYSPRV or BYPASS privilege.
2.2.4 /PROXIES
/PROXIES=n
Optional. Default: Number of communication proxies plus 10, with
a minimum of 20.
Specifies the maximum size of the proxy cache. If you plan to add
entries to the proxy database after you start the TCP/IP Services
software, set /PROXIES to a value higher than the default.
You cannot change this value if the TCP/IP Services software is
running.
2.2.5 /REJECT
/REJECT { =[NO]HOSTS=(hosts) | =[NO]NETWORKS=(networks) |
Optional. Default: No rejections.
Specifies the hosts or networks that cannot access the TCP/IP
Services software, including the rejection message that TCP/IP
might return.
(For remote login, remote shell, and remote executive, the
rejection message is preceded by a byte with a value of 1 and
terminated by a byte with a value of 0.)
Do not specify the same hosts or networks for both /ACCEPT and
/REJECT.
To delete a /REJECT entry, specify it again using the NOHOSTS or
NONETWORKS option.
Specify one of the following:
o [NO]HOSTS=hosts to list hosts that cannot access TCP/IP
Services. Maximum is 32. The syntax is:
/REJECT=HOSTS=(host1_name,host2_name, host3_address)
o [NO]NETWORKS=networks to list networks that cannot access
TCP/IP Services Maximum is 16. The syntax is:
NETWORKS=(net1[:net1mask],net2[:net2mask],... )
For each network, specify network:network_mask. The network
mask is optional. Default: Class number of your network. For
example, the default for 11.200.0.0. is 255.0.0.0. The syntax
is:
/REJECT=NETWORKS=(net1_name,net2_address,net3_addr:net3_mask)
2.3 – Examples
1.TCPIP> SET CONFIGURATION COMMUNICATION -
_TCPIP> /REJECT=NETWORK=(16.30.0.0:255.255.0.0,16.40.0.0:255.255.0.0)
In the configuration database, sets all the services to be
inaccessible to the two specified networks.
3 – ENABLE_SERVICE
Note: Specify SET CONFIGURATION ENABLE SERVICE without an
underscore when entering this command. Modifies service-related
information in the permanent configuration database that enables
(or disables) services for startup. Allows you to specify that
the service be enabled or disabled for startup on the current
node only or on all nodes in the cluster. To specify clusterwide
enabling or disabling of services, use the /COMMON qualifier.
SET CONFIGURATION ENABLE SERVICE adds an entry for a service to
the list of enabled services in the configuration database.
SET CONFIGURATION ENABLE NOSERVICE removes an entry for a service
from the list of enabled services in the configuration database.
Related commands: SHOW CONFIGURATION ENABLE SERVICE, ENABLE
SERVICE
Format
SET CONFIGURATION ENABLE [NO]SERVICE service
[ /COMMON ]
[ /[NO]CONFIRM ]
3.1 – Parameters
service
Required.
Specifies the service to add or delete from the configuration
database. 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:
o Uppercase and lowercase alphabetic characters
o Numerals
o Dollar sign ($)
o 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, or FTP). In addition, the
service name CUSTOMER_SERVICE is reserved by HP.
3.2 – Qualifiers
3.2.1 /COMMON
Optional. Default (when /COMMON is not specified): node-specific
enabling or disabling of services.
Modifies service-related information in the configuration
database for the clusterwide enabling or disabling of services.
3.2.2 /CONFIRM
/CONFIRM
/NOCONFIRM
Optional. Default: /CONFIRM if you use wildcards; otherwise,
/NOCONFIRM.
Use only with SET CONFIGURATION ENABLE NOSERVICE. Controls
whether the software requests you to confirm before it deletes an
entry. With /CONFIRM enabled, the software requests confirmation.
At the CONFIRM: prompt, enter one of the following:
o Y to delete the entry
o N to retain the entry
The /NOCONFIRM qualifier eliminates all user confirmation when
deleting service entries.
3.3 – Examples
1.TCPIP> SET CONFIGURATION ENABLE SERVICE TELNET
In the configuration database, enables the TELNET service for
startup on this node.
2.TCPIP> SET CONFIGURATION ENABLE SERVICE FTP /COMMON
In the configuration database, enables the FTP service for
startup on every node in the cluster.
3.TCPIP> SET CONFIGURATION ENABLE NOSERVICE *
Enable service TELNET
Remove? [N]: Y
In the configuration database, disables any service enabled for
startup on this node, if confirmed by the user.
4 – INTERFACE
Enters information into the configuration database, which defines
one of the following when TCP/IP Services starts up:
o An Internet interface (hardware connection to the network)
o A serial line Internet interface (a form of hardware
connection to the network)
o A pseudointerface (a data structure that extends subnet
routing so that, on the same physical network, an interface
acts as a gateway between multiple subnets)
Related commands: SHOW INTERFACE, SET INTERFACE
Applies to: Routing
Format
SET CONFIGURATION [NO]INTERFACE interface
[/[NO]ARP ]
[/[NO]AUTO_START ]
[/BROADCAST_MASK=IP_address ]
[/C_BROADCAST_MASK=IP_address]
[/C_NETWORK=IP_address ]
[/[NO]CLUSTER=host ]
[/COMPRESS=options ]
[/DESTINATION=IP_address ]
[/[NO]DHCP ]
[/FLOWCONTROL ]
[/HOST=host ]
[/[NO]LOOPBACK ]
[/NETWORK_MASK=IP_address ]
[/[NO]PRIMARY ]
[/SERIAL_DEVICE=device ]
4.1 – Restrictions
This command requires:
o OPER privilege
o Read access to the hosts database
o Read access to the networks database
o Read, write, and delete access to the routes database
Every host on the same network must have the same network mask.
4.2 – Parameters
interface
Required.
Specifies an interface name for the communication controller,
such as RF1, RT1, ZE0, XE0, SL0, SL1, SL2, PP0, PP1, PP2. Refer
to the chapter on configuring network interfaces in the HP TCP/IP
Services for OpenVMS Management manual for more information.
4.3 – Qualifiers
4.3.1 /ARP
/ARP
/NOARP
Optional. Default: /ARP.
Enables IP address-to-hardware address (Ethernet or FDDI)
mapping.
/ARP is valid when you create an interface but not when you
modify an existing interface.
4.3.2 /AUTO_START
/AUTO_START
/NOAUTO_START
Optional. Default: /AUTO_START.
Valid for a SLIP or PPP interface. Automatically creates the
interface when TCP/IP Services starts.
4.3.3 /BROADCAST_MASK
/BROADCAST_MASK=IP_address
Optional.
Sets the Internet interface to receive all broadcast messages.
TCP/IP Services calculates the default by the following methods:
o Using the network number
o Setting all bits in the host number field to 1
4.3.4 /C_BROADCAST_MASK
/C_BROADCAST_MASK=IP_address
Optional.
Sets the cluster broadcast mask to receive all broadcast
messages.
The software calculates the default by the following methods:
o Using the network number
o Setting all bits in the host number field to 1
4.3.5 /C_NETWORK
/C_NETWORK=IP_address
Optional.
Sets the network mask of the cluster network. This mask is
specific to the cluster host network.
The software calculates the default by using the following
methods:
o Setting the bits representing the network fields to 1
o Setting the bits representing the host field to 0
4.3.6 /CLUSTER
/CLUSTER=host
/NOCLUSTER
Optional. Default: None.
Specifies the cluster host name (alias host identifier).
Before using this qualifier, first define the same name in the
hosts database.
/CLUSTER=host associates the alias host identifier with each
interface in a cluster.
/NOCLUSTER disables Internet cluster processing on the specified
interface.
CAUTION
When you specify /NOCLUSTER, active communication is aborted
for applications bound to the cluster alias name.
4.3.7 /COMPRESS
/COMPRESS= {ON | OFF | AUTOMATIC}
Optional. Defaults: For PPP interface, /COMPRESS=ON; for SLIP
interface, /COMPRESS=OFF.
Valid for SLIP and PPP interfaces.
Enables or disables TCP header compression.
/COMPRESS=AUTOMATIC turns off compression unless the remote end
begins to use it.
4.3.8 /DESTINATION
/DESTINATION=IP_address
Optional.
Valid for a PPP interface.
Used on the local host to provide dialup access to remote
systems. The value specified is the IP address to be given to
remote clients for use while the PPP connection is active. If
using /DESTINATION, you must provide the address of the local
host by using the /HOST qualifier.
4.3.9 /DHCP
/DHCP
/NODHCP
Optional.
Designates the interface as a DHCP-controlled interface in the
permanent database.
4.3.10 /FLOWCONTROL
Optional. Default: No flow control.
Valid for a SLIP interface. Enables the handling of XON and
XOFF characters to interoperate properly with modems that are
configured to interpret these characters locally.
Specify /FLOWCONTROL only if the host at the other end of the
line is running TCP/IP Services.
4.3.11 /HOST
/HOST=host
Required when first setting the interface; optional if the
interface is already defined. Always required for a SLIP
interface. Optional for a PPP interface unless you are setting
up the local host as a dialup provider by using the /DESTINATION
qualifier.
Local host name or IP address using the interface. If not
specified for a PPP interface, PPP obtains the correct address
from the remote host.
If your host is multihomed, specify an address.
4.3.12 /LOOPBACK
/LOOPBACK
/NOLOOPBACK
Optional. Default: /NOLOOPBACK.
Sets loopback mode.
4.3.13 /NETWORK_MASK
/NETWORK_MASK=IP_address
Required if you use subnets.
The part of the host field of the IP address identified as the
subnet.
The software calculates the default by the following methods:
o Setting the bits representing the network fields to 1
o Setting the bits representing the host field to 0
An IP address consists of a network number and a host number. You
can also divide the host field into a site-specific subnetwork
and host field.
4.3.14 /PRIMARY
/PRIMARY
/NOPRIMARY
Optional.
For DHCP-controlled interfaces, designates the interface from
which system-wide configuration options (such as the IP address
of the BIND server) are used.
4.3.15 /SERIAL_DEVICE
/SERIAL_DEVICE=device
Required for SLIP and PPP interfaces; otherwise, not used.
Identifies the OpenVMS terminal device used as a serial device.
Specify an arbitrary terminal device name. (Unlike Ethernet,
FDDI, and Token Ring interface names, a serial interface name is
not related to the OpenVMS device name.)
4.4 – Examples
1.TCPIP> SET CONFIGURATION INTERFACE SL5 /HOST=LARK -
_TCPIP> /NETWORK_MASK=255.255.255.0 /SERIAL_DEVICE=TTA3: -
_TCPIP> /COMPRESS=ON /FLOWCONTROL
Configures SLIP interface SL5, using the local IP address
assigned to host LARK, with a subnet mask of 255.255.255.0.
The interface uses the terminal device TTA3:.
The /COMPRESS qualifier enables TCP header compression (CSLIP).
The /FLOWCONTROL qualifier enables special handling of XON and
XOFF characters for proper interoperation with modems that are
configured to interpret these characters locally.
2.TCPIP> SET CONFIGURATION INTERFACE FF0 /HOST=KESTREL -
_TCPIP> /NETWORK_MASK=255.255.0.0 -
_TCPIP> /BROADCAST_MASK=128.30.0.0 /ARP
For new interface FF0 on host KESTREL, sets the network mask
to 255.255.0.0, sets the broadcast mask to 128.30.0.0, enables
ARP, and activates the interface.
3.TCPIP> SET CONFIGURATION INTERFACE PP0 /SERIAL_DEVICE=TTA0: -
_TCPIP> /HOST=10.10.1.2 /DESTINATION=10.10.1.3
Configures the interface as a PPP serial device. This command
specifies that the local host is a dialup provider. The address
specified with the /DESTINATION qualifier (10.10.1.3) is the
address assigned to the client system requesting an address.
Refer to the HP TCP/IP Services for OpenVMS Management manual
for more information about setting up interfaces for SLIP and
PPP communication.
5 – MAP
Adds information to the configuration database that maps
(logically links) one of the following to the NFS server:
o OpenVMS disk - Requires one execution of SET CONFIGURATION MAP
to map the disk to a UNIX path name (logical file system).
o Container file system - Requires two executions of SET
CONFIGURATION MAP. The first maps the disk, and the second
maps the file system.
Mapping creates a logical file system, also called an NFS file
system.
When the NFS server starts up, it issues a GENERATE MAP command,
which creates the mappings for disks and container file systems;
these mappings are viewable with the SHOW MAP command.
Related commands: ADD EXPORT, SHOW EXPORT, REMOVE EXPORT, MAP,
UNMAP, SET CONFIGURATION NOMAP, SHOW MAP, SHOW CONFIGURATION MAP
Format
SET CONFIGURATION MAP "file system name" logical_file_system
5.1 – Restrictions
Requires SYSPRV and BYPASS privileges.
5.2 – Parameters
"file system name"
Required.
Specifies the name for the file system or disk. When mapping
a disk, the "/path" can be only one level from the root. This
parameter specifies the name by which users access the file
system.
logical_file_system
Required.
Specifies the file system to make known to the NFS server.
To map an OpenVMS file system, specify its disk as follows:
$ SET CONFIGURATION MAP "/disk" disk:
To map a container file system, specify the disk and the
directory name as follows:
TCPIP> SET CONFIGURATION MAP "/container_name" -
_TCPIP> disk:[vms.directory.name]
5.3 – Examples
1.TCPIP> SET CONFIGURATION MAP "/usr" CANARY$DUA2:
Maps local disk CANARY$DUA2: to /usr. This disk can be exported
to users on remote NFS clients as /usr.
2.TCPIP> SET CONFIGURATION MAP "/remote" VERDIN$DUA3: -
_TCPIP> SET CONFIGURATION MAP "/flyers" VERDIN$DUA3:[UNIX_BIRD_FILES]
Maps [UNIX_BIRD_FILES], a container file system on disk
VERDIN$DUA3:, to /flyers. This file system can be exported
to NFS server users as /flyers. (The first MAP command maps the
underlying OpenVMS file system.)
6 – NAME_SERVICE
When TCP/IP Services starts up, configures the BIND resolver and
designates a BIND server. All settings are systemwide.
Related commands: SET NAME_SERVICE,
SHOW CONFIGURATION NAME_SERVICE
Format
SET CONFIG [NO]NAME_SERVICE [ /[NO]SERVER=host]
[ /[NO]DOMAIN=domain ]
[ /[NO]PATH=domain ]
[ /RETRY=number of retries ]
[ /TIMEOUT=seconds ]
[ /TRANSPORT=protocol ]
6.1 – Qualifiers
6.1.1 /CLUSTER
/CLUSTER=dev:[directory]
Optional.
Specifies the common BIND directory. By default, the clusterwide
common database common-disk:[TCPIP$BIND_common] is used. This
qualifier reloads the BIND database on every master BIND server
running the OpenVMS cluster.
6.1.2 /DOMAIN
/DOMAIN=domain
/NODOMAIN
Optional. Default: The local domain.
Defines the default domain.
/NODOMAIN deletes the definition of the domain.
6.1.3 /PATH
/PATH=domain
/NOPATH=domain
Optional. SYSNAM privilege is required for this command.
Defines the BIND resolver domain search list. The /NOPATH
qualifier removes domains from the list.
To specify multiple domains, list them by search preference. The
resolver starts with the first domain on the list, and continues
to search each domain until the name is found (or until all
domains have been exhausted and the lookup fails).
If you define a domain list and then issue another SET
CONFIGURATION NAME_SERVICE /PATH command, TCP/IP Services appends
the new domains to the end of the list.
If a search list is not defined, the default behavior of the BIND
resolver is to do a lookup on the name as you typed it. If that
lookup fails, then the default domain is appended and the lookup
is attempted again.
6.1.4 /RETRY
/RETRY=number of retries
Optional. Default: Four retries.
Number of times that the BIND resolver attempts to contact a BIND
server if previous tries failed.
6.1.5 /SERVER
/SERVER=host
/NOSERVER=host
Optional.
Host name or address of the BIND server or servers that the BIND
resolver will query.
To specify multiple hosts, list them by request preference. The
resolver sends the first lookup request to the first host on the
list.
/NOSERVER removes hosts from the list.
If you define a server list and then issue another
SET CONFIGURATION NAME_SERVICE /SERVER command, TCP/IP Services
appends the new servers to the end of the list.
6.1.6 /TIMEOUT
/TIMEOUT=seconds
Optional. Default: 4 seconds.
Timeout interval for the BIND resolver's requests to a BIND
server. Represents the length of time to wait for a reply after
each retry attempt.
The total timeout period will be:
timeout_value * retry_value * number_servers
6.1.7 /TRANSPORT
/TRANSPORT=protocol
Optional. Default: UDP.
Protocol used for communicating with a BIND server. Specify one:
o UDP
o TCP
o SCTP
6.2 – Examples
1.TCPIP> SET CONFIGURATION NAME_SERVICE /SERVER=(PARROT,SORA,JACANA)
When TCP/IP Services starts, defines hosts PARROT, SORA, and
JACANA as BIND servers.
2.TCPIP> SET CONFIGURATION NAME_SERVICE /SERVER=OSPREY -
_TCPIP> /PATH=(abc.dec.com,xyz.dec.com)
When TCP/IP Services starts, defines host OSPREY as the BIND
server. The BIND resolver searches the abc.dec.com domain
first, and then searches the xyz.dec.com domain.
7 – NOMAP
Removes map records from the configuration database that were
previously added with SET CONFIGURATION MAP. When the NFS server
starts up, it issues a GENERATE MAP command that creates the
mappings for disks and container file systems.
Related commands: SET CONFIGURATION MAP,
SHOW CONFIGURATION MAP, ADD EXPORT, SHOW EXPORT, REMOVE EXPORT,
MAP, UNMAP, SHOW MAP
Format
SET CONFIGURATION NOMAP "/path/name" [ /[NO]CONFIRM ]
7.1 – Restrictions
Requires SYSPRV and BYPASS privilege.
7.2 – Parameters
"/path/name"
Required.
UNIX name of the file system to unmap.
You can use wildcards.
7.3 – Qualifiers
7.3.1 /CONFIRM
/CONFIRM
/NOCONFIRM
Optional. Default: /CONFIRM if you use a wildcard.
With /CONFIRM enabled, requests confirmation before unmapping
each file system. If you specify the /NOCONFIRM qualifier, the
operation is performed without asking you to confirm the request.
7.4 – Examples
1.TCPIP> SET CONFIGURATION NOMAP "/disk_host"
Unmaps the NFS file system /remote, making it unavailable to
client users when TCP/IP Services starts.
8 – PROTOCOL
Enters information into the configuration database that sets the
parameters for ICMP, IP, TCP, and UDP when TCP/IP Services starts
up.
Related commands: SET PROTOCOL, SHOW CONFIGURATION PROTOCOL
Format
SET CONFIGURATION PROTOCOL ICMP [ /[NO]REDIRECT ]
SET CONFIGURATION PROTOCOL IP [ /[NO]FORWARD ]
[ /REASSEMBLY_TIMER=seconds ]
SET CONFIGURATION PROTOCOL TCP [ /[NO]MTU_SEGMENT_SIZE ]
[ /[NO]DELAY_ACK ]
[ /DROP_COUNT=n ]
[ /PROBE_TIMER=seconds ]
[ /QUOTA=[
SEND=bytes,RECEIVE=bytes
] ]
[ /[NO]WINDOW_SCALE ]
SET CONFIGURATION PROTOCOL UDP [ /[NO]BROADCAST ]
[ /[NO]FORWARD ]
[ /QUOTA=options ]
8.1 – Restrictions
Requires OPER privilege.
8.2 – Parameters
{ICMP | IP | TCP | UDP}
Required.
Specifies the protocol software to configure.
8.3 – ICMP Qualifiers
8.3.1 /REDIRECT
/REDIRECT
/NOREDIRECT
Optional. Default: /NOREDIRECT.
Sends ICMP_REDIRECT messages.
8.4 – IP Qualifiers
8.4.1 /FORWARD
/FORWARD
/NOFORWARD
Optional. Default: /NOFORWARD.
Forwards IP messages to other hosts.
8.4.2 /REASSEMBLY_TIMER
/REASSEMBLY_TIMER=n
Optional. Default: 7 seconds. Valid range: 1 to 126.
Sets the maximum time for trying to reassemble a received
datagram.
8.5 – TCP Qualifiers
8.5.1 /MTU_SEGMENT_SIZE
/MTU_SEGMENT_SIZE
/NOMTU_SEGMENT_SIZE
Optional. Default: /NOMTU_SEGMENT_SIZE.
If a connection is more than one hop away, sets the segment size.
Specify one of the following:
/MTU_SEGMENT_SIZE Sets the segment size as close as possible to
the maximum transfer unit (MTU) size.
/NOMTU_SEGMENT_ Sets the segment size as close as possible to
SIZE the standard 512 bytes.
8.5.2 /DELAY_ACK
/DELAY_ACK
/NODELAY_ACK
Optional. Default: /DELAY_ACK.
Enables or disables a delay before sending acknowledgments:
/DELAY_ACK ACKs are generated with a delay.
/NODELAY_ACK ACKs are generated without any delay.
8.5.3 /DROP_COUNT
/DROP_COUNT=n
Optional.
Number of idle probes that can go unsatisfied before the software
declares a TCP connection dead and closes it.
8.5.4 /PROBE_TIMER
/PROBE_TIMER=n
Optional. Default: 75 seconds.
Number of seconds between probes for idle TCP connections (when
the SO_KEEPALIVE option is set). If the remote system fails to
respond, the connection is removed. Also, when initiating a TCP
connection request, indicates the maximum number of seconds that
the software waits for a response from the remote system before
the request times out.
8.5.5 /QUOTA
/QUOTA=[SEND=bytes,RECEIVE=bytes]
Optional.
Specifies the queue size (in bytes) for messages.
The options for setting TCP message queue size are:
o RECEIVE:n - Receive queue size. Default: 4096 bytes.
o SEND:n - Send queue size. Default: 4096 bytes.
8.5.6 /WINDOW_SCALE
/WINDOW_SCALE
/NOWINDOW_SCALE
Optional.
Turns TCP window scaling on and off. Default is on.
Scaling allows windows larger than 64 KB to be represented in the
normal 16-bit TCP window field. Large windows allow improved
throughput. Turning this option off may help troubleshoot
communication problems with another TCP/IP implementation.
8.6 – UDP Qualifiers
8.6.1 /BROADCAST
/BROADCAST
/NOBROADCAST
Optional. Default: /NOBROADCAST.
Enables privilege checking for broadcast messages.
o /BROADCAST - Nonprivileged users can send broadcast messages.
o /NOBROADCAST - To send broadcast messages, users need a
privileged UIC or SYSPRV, BYPASS, or OPER privilege.
Sun RPC applications use broadcast messages and need privilege
checking disabled.
8.6.2 /FORWARD
/FORWARD
/NOFORWARD
Optional. Default: /NOFORWARD.
Forwards IP messages.
8.6.3 /QUOTA
/QUOTA=options
Optional.
Specifies the queue size (in bytes) for messages.
The options for setting UDP message queue size are:
o RECEIVE:n - Receive queue size. Default: 9000 bytes.
o SEND:n - Send queue size. Default: 9000 bytes.
8.7 – Examples
1.TCPIP> SET CONFIGURATION PROTOCOL IP /FORWARD
Sets IP to forward messages to other hosts, including other
Internet cluster nodes.
2.TCPIP> SET CONFIGURATION PROTOCOL TCP /PROBE_TIMER=50
Sets the TCP protocol probe timer parameter to 50 seconds.
9 – SMTP
Modifies the SMTP configuration in the configuration database.
SET CONFIGURATION NOSMTP with no qualifiers deletes all SMTP
records.
Related commands: SHOW CONFIGURATION SMTP
Format
SET CONFIGURATION [NO]SMTP [ /ADDRESS_RETRIES=n ]
[ /GATEWAY=option=host ]
[ /HOP_COUNT_MAXIMUM=n ]
[ /INTERVAL=options ]
[ /[NO]LOG=[file] ]
[ /OPTIONS=options ]
[ /QUEUES=n ]
[ /RECEIVE_TIMEOUT=minutes ]
[ /SEND_TIMEOUT=minutes ]
[ /SUBSTITUTE_DOMAIN=[NO]NAME=fully-qualified-name
]
[ /[NO]ZONE[=domain] ]
9.1 – Restrictions
For clusters, issue this command only on the nodes where the SMTP
queues reside - that is, on nodes that are not using clusterwide
queues and are not managing clusterwide queues for other nodes.
Requires SYSPRV or BYPASS privilege.
9.2 – Qualifiers
9.2.1 /ADDRESS_RETRIES
/ADDRESS_RETRIES=n
Optional. Default: 16.
Maximum number of different addresses to which SMTP will send
as it tries to deliver mail. Beyond this number of attempts, the
message is undeliverable.
A message is also undeliverable if SMTP fails to deliver after it
attempts all the possible addresses from an MX lookup.
9.2.2 /GATEWAY
/GATEWAY=option=host
Optional. Default: None.
An alternate route through which SMTP sends mail if delivery
fails.
o [NO]ALTERNATE=host
- Alternate host or domain to which delivery is attempted.
- Used by ZONE, if a zone is defined, as the last chance for
delivery (see the /ZONE qualifier).
- NOALTERNATE deletes an existing alternate destination.
o [NO]GENERAL_PURPOSE=host
- Gateway to handle non-SMTP mail, for example, UUCP
addresses.
- NOGENERAL_PURPOSE deletes the specified destination for
protocols other than SMTP.
9.2.3 /HOP_COUNT_MAXIMUM
/HOP_COUNT_MAXIMUM=n
Optional. Default: 16.
Maximum number of relays (hops) between routers until SMTP
considers the mail undeliverable.
9.2.4 /INTERVAL
/INTERVAL={ INITIAL="OpenVMS_delta_time" | RETRY="OpenVMS_
delta_time" | MAXIMUM="OpenVMS_delta_time" }
Optional. Defaults: INITIAL=30 minutes, RETRY=60 minutes,
MAXIMUM=3 days.
Time intervals related to repeated attempts before delivery
fails. Specify the value within quotation marks as follows: "dddd
hh:mm:ss:cc." For example:
dddd = days (0-9999)
h = hours (0-24)
m = minutes
s = seconds
cc = milliseconds
You can modify the following options:
o INITIAL="OpenVMS_delta_time" is the amount of time that SMTP
waits before making a second attempt to deliver.
o RETRY="OpenVMS_delta_time" is the time SMTP waits between
retries, starting with the second attempt. (Recommended time:
twice the initial interval.)
o MAXIMUM="OpenVMS_delta_time" is the maximum elapsed time that
SMTP retries delivery.
9.2.5 /LOG
/LOG=[file]
/NOLOG=[file]
Optional. Default: SYS$SPECIFIC:[TCPIP_SMTP]TCPIP$SMTP_
LOGFILE.LOG.
File to which SMTP queue activity is logged.
9.2.6 /OPTIONS
/OPTIONS=options
Optional. Defaults: NOEIGHT_BIT, HEADERS, NORELAY.
The following SMTP options are available:
o [NO]EIGHT_BIT
All characters must have the eighth bit clear. Allows the
transmission of 8-bit characters.
o Header control. Specify one of the following:
HEADERS Headers are printed at bottom of messages.
NOHEADERS Headers are omitted.
TOP_HEADERS Headers are printed at top of messages.
NOTOP_ Resets TOP_HEADERS to the default.
HEADERS
o [NO]RELAY
Relays mail to other hosts by functioning as an end node.
9.2.7 /QUEUES
/QUEUES=n
Optional. Default: 1.
Number of execution queues for the specified nodes.
Use this qualifier only on nodes that own the SMTP queues - that
is, nodes not using clusterwide SMTP queues or managing SMTP
clusterwide queues for other nodes.
9.2.8 /RECEIVE_TIMEOUT
/RECEIVE_TIMEOUT=minutes
Optional. Default: 5 minutes.
Maximum time between socket receipts of a message for a
particular dialog.
If a message is not received within this interval, the connection
is broken and the mail control file is deleted.
9.2.9 /SEND_TIMEOUT
/SEND_TIMEOUT=minutes
Optional. Defaults:
DATA - 3 minutes
INITIAL - 5 minutes
MAIL - 5 minutes
RECEIPT - 5 minutes
TERMINATION - 10 minutes
Maximum time between remote host acknowledgments of a particular
SMTP command.
If an acknowledgment is not received within the specified time,
it is assumed that there are communication problems with the
remote host. If the next delivery attempt takes place before the
mail's delivery date, the mail is rescheduled for later delivery.
9.2.10 /SUBSTITUTE_DOMAIN
/SUBSTITUTE_DOMAIN=[NO]NAME=fully-qualified-domain
Optional.
By default, the From: and Return-Path fields display the
sender's name and fully qualified domain. NONAME causes the
sender's domain name to be omitted from the Return-Path field.
If you specify a fully qualified domain name (/SUBSTITUTE_
DOMAIN=NAME=fully-qualified-domain), that specified domain name
is displayed as the sender's domain name.
For example, suppose you specify the fully qualified
domain name eagle for the sender's return path
(/SUBSTITUTE_DOMAIN=NAME=eagle). When user magpie on host
condor.hawk.eagle.org sends mail to daw on another host,
user daw sees the return path as magpie@eagle rather than
magpie@condor.hawk.eagle.org.
This is what daw sees:
#707 18-NOV-2002 14:02:02.71 MAIL
From: SMTP%"magpie@eagle"
To: SMTP%"daw@crow.ravin.rook.org"
CC:
Subj: Big sale today!
NOTE
For changes made with the /SUBSTITUTE_DOMAIN qualifier
to take effect, you must stop and restart SMTP. For more
information about stopping and starting SMTP, refer to the
HP TCP/IP Services for OpenVMS Management manual.
9.2.11 /ZONE
/ZONE[=domain]
/NOZONE[=domain]
Optional. Default: /NOZONE (no gateway searching).
Domain for your environment (probably a superset of your local
domain).
Mail sent to another network must be sent to this gateway.
With no value, /ZONE defaults to one level higher than your local
domain.
For example, if your local domain is a.b.com, the default value
of /ZONE is b.com because TCP/IP Services has been started; this
assumes that the domain is known.
Mail for delivery outside of your zone is sent to its destination
by the alternate gateway (see the /GATEWAY qualifier).
9.3 – Examples
1.TCPIP> SET CONFIGURATION SMTP /INTERVAL=(INIT="0 00:10:00.00")
The system waits 10 minutes before making its first attempt to
deliver the message.
2.TCPIP> SET CONFIGURATION SMTP /INTERVAL=(RETRY="0 00:20:00.00")
Specifies the wait time between retries.
3.TCPIP> SET CONFIGURATION SMTP /INTERVAL=(MAX="3 00:20:00.00")
Specifies the maximum amount of time to retry before an error
message is issued.
4.TCPIP> SET CONFIGURATION SMTP /GATEWAY=(ALTERNATE:route_gateway)
Specifies the alternate host or domain to which delivery
is attempted if mail cannot be delivered to the primary
destination.
5.TCPIP> SET CONFIGURATION SMTP /GATEWAY=(GENERAL:uucp_gateway)
Specifies a general-purpose gateway to handle non-SMTP mail.
6.TCPIP> SET CONFIGURATION SMTP /ZONE=rsch.opt.com
Specifies that rsch is a domain that can be used to divert
messages to nodes outside the local domain.
10 – SNMP
Configures SNMP on an individual host.
SET CONFIGURATION NOSNMP does not require any qualifiers.
After making changes to the SNMP configuration, shut down and
restart the master agent and any subagents. Issue the following
commands:
$ @SYS$STARTUP:TCPIP$SNMP_SHUTDOWN
$ @SYS$STARTUP:TCPIP$SNMP_STARTUP
Related command: SHOW CONFIGURATION SNMP
Format
SET CONFIGURATION [NO]SNMP [ /[NO]ADDRESS=host ]
[ /[NO]COMMUNITY="name" ]
[ /[NO]CONFIRM ]
[ /CONTACT=name ]
[ /FLAGS=options]
[ /LOCATION=options ]
[ /TYPE=options ]
10.1 – Restrictions
Requires SYSPRV or BYPASS privilege.
If you add a new community and do not specify the /TYPE
qualifier, the value of /TYPE defaults to read only.
If you add a new community and do not specify the /ADDRESS
qualifier, the default address is 0.0.0.0.
10.2 – Qualifiers
10.2.1 /ADDRESS
/ADDRESS=(IP_address)
/NOADDRESS=(IP_address)
Optional. Default: 0.0.0.0
Specifies hosts that belong to a particular community. You can
specify multiple addresses.
This qualifier is meaningful only if you include the /COMMUNITY
qualifier. A remote host cannot access information from this
host unless its address appears in one or more communities
of type READ or WRITE. For communities of type TRAP, the
addresses specify the hosts that receive trap messages. For more
information, see the /TYPE qualifier.
If you add a new community and do not specify this qualifier, the
new entry's address is 0.0.0.0.
If you use the /ADDRESS qualifier with a community that already
exists, these addresses are added to the existing address list.
/NOADDRESS deletes addresses from an existing list. If the
deleted address is the only address listed for the community
name, this qualifier also deletes the community.
10.2.2 /COMMUNITY
/COMMUNITY="name"
/NOCOMMUNITY="name"
Optional. Default: To enable the standard "public" community, you
can run the TCPIP$CONFIG procedure.
Used with the /ADDRESS qualifier. Name of the community that the
SNMP agent recognizes. Optionally, specify a type of access and
a list of host addresses. Enclose the name in quotation marks
to preserve lowercase characters. See the /TYPE and /ADDRESS
qualifiers for more information.
[NO]COMMUNITY="name" removes a community name.
10.2.3 /CONFIRM
/CONFIRM
/NOCONFIRM
Optional. Default: /CONFIRM with if you use a wildcard;
otherwise, /NOCONFIRM
When you delete communities (with the /NOCOMMUNITY qualifier),
first asks for your confirmation.
If you specify the /NOCONFIRM qualifier, the operation is
performed without asking you to confirm the request.
10.2.4 /CONTACT
/CONTACT=name
Optional. Default: None.
Name of the system administrator (or other contact person) of the
host on which the SNMP agent runs. The name field has a maximum
length of 235.
10.2.5 /FLAGS
/FLAGS=options
Optional.
The options include:
o SETS
Lets the master agent process SET commands from SNMP clients.
o AUTHEN_TRAPS
Lets the master agent send trap messages in response to
unauthorized community strings from SNMP clients.
10.2.6 /LOCATION
/LOCATION=options
Optional. Default: None.
Location of the system on which the SNMP agent runs. Maximum
total length is 215 characters.
The options include:
o [NO]FIRST=text
Specifies the first part of the location. Maximum length of
text is 200 characters.
o [NO]SECOND=text
Specifies the last part of the location. Maximum length of
text is 200 characters.
If you specify two options, they are appended when sent to a
client in response to an SNMP request for syslocation. For
example, if FIRST is abc and SECOND is def, the value of the
location is abcdef with no spaces. The total number of characters
must not exceed 215.
10.2.7 /TYPE
/TYPE= {[NO]READ | [NO]TRAP | [NO]WRITE}
Optional. Default: READ.
Sets the type of access (to your local MIB data) to allow for a
specified community.
o Type READ allows the master agent to accept GET, GETNEXT, and
GETBULK commands from clients (management stations).
o Type TRAP allows the local master agent to issue traps
to members of a specified community. Members of a trap
community receive SNMP Trap-PDUs for significant events,
including coldStart traps when the agent is initialized, and
authenticationFailure traps when the agent receives an SNMP
request that specifies an unauthorized community string.
o Type WRITE allows the master agent to accept SET commands from
clients (management stations).
READ access is present by default when specifying TRAP or WRITE.
Also, you can remove the read access without affecting the way
the agent responds to a read request. For example:
$ SET CONFIGURATION SNMP /COMMUNITY="name" /TYPE=NOREAD
10.3 – Examples
1.TCPIP> SET CONFIGURATION SNMP /COMMUNITY="public" -
_TCPIP> /CONTACT="Sam Spade" -
_TCPIP> /LOCATION=(FIRST="Falcon Building",SECOND="Los Angeles,
California")
Configures SNMP with the standard public community, taking the
default type (READ) and address (0.0.0.0) for that community.
Both contact and location are specified.
The first and second parts of the location text are
concatenated when displayed by an SNMP client. For example:
Falcon BuildingLos Angeles, California
If no update to the location text is done by an SNMP client,
the display produced by SHOW CONFIGURATION SNMP is as follows:
Location
First: Falcon Building
Second: Los Angeles, California
If the text is updated by an SNMP client (for example, to
change "Falcon" to "Falconi"), the original formatting is not
preserved and the display produced by SHOW CONFIGURATION SNMP
is as follows:
Location
First: Falconi BuildingLos Angeles, California
2.TCPIP> SET CONFIGURATION SNMP /COMMUNITY="rw" /TYPE=WRITE -
_TCPIP> /ADDRESS=136.20.100.10 /FLAGS=SETS
Configures a community with only read/write access to the host
with the address specified. Other hosts still have read access
through the public community. Also sets the SETS flag to enable
the SNMP agents to process write requests from SNMP clients on
host 136.20.100.10.
3.TCPIP> SET CONFIGURATION SNMP /NOCOMMUNITY="rw"
Removes the rw (read/write) community (set in example 2.)
4.TCPIP> SET CONFIGURATION SNMP /COMMUNITY="trapit" /TYPE=TRAP -
_TCPIP> /ADDRESS=136.20.0.10
Configures SNMP so that agents can send trap messages to the
well-known UDP port 162 on the host identified with the address
136.20.0.10.
5.TCPIP> SET CONFIGURATION SNMP /FLAGS=AUTHEN_TRAPS -
_TCPIP> /COMMUNITY="trapit2" /TYPE=TRAP -
_TCPIP> /ADDRESS=(136.20.0.12,136.20.0.15)
Configures SNMP with the AUTHEN_TRAPS flag so that the
master agent sends trap messages when it detects a client
request containing an invalid community name. Also configures
an additional trap community. Trap messages, including
authentication traps, go to all three addresses specified in
the trap communities configured in this example and in example
4.
6.TCPIP> SET CONFIGURATION SNMP /COMMUNITY="rw2" /TYPE=WRITE -
_TCPIP> /ADDRESS=(136.20.0.15,136.20.0.100)
Configures community rw2, which gives read/write access to
two hosts. Note that one address can appear for more than one
community, although a given address cannot be specified more
than once for a single community.
11 – START_ROUTING
Note: Specify START ROUTING without an underscore when entering
this command. Enters information into the configuration database
to start dynamic routing when TCP/IP Services starts.
Related commands: SHOW CONFIGURATION START ROUTING, START ROUTING
Format
SET CONFIGURATION START [NO]ROUTING [ /GATED ]
[ /LOG ]
[ /SUPPLY[=DEFAULT] ]
11.1 – Qualifiers
11.1.1 /GATED
Optional.
Enables the gateway routing daemon (GATED).
If you enable dynamic GATED routing, you will be able to
configure this host to use any combination of the following
routing protocols to exchange dynamic routing information with
other hosts on the network:
o RIP (Routing Information Protocol), Versions 1 and 2
o RDISC (Router Discovery Protocol)
o OSPF (Open Shortest Path First)
o EGP (Exterior Gateway Protocol)
o BGP (Border Gateway Protocol), BGP-4
o Static routes
11.1.2 /LOG
Optional. Default: No logging.
Applies to ROUTED. Do not use with /GATED.
Logs routing activity to
SYS$SYSDEVICE:[TCPIP$ROUTED]TCPIP$ROUTED.LOG.
11.1.3 /SUPPLY
/SUPPLY[=DEFAULT]
Optional. Applies only to ROUTED. Do not use with /GATED.
Broadcasts routing information to other hosts in 30-second
intervals.
If you specify /SUPPLY=DEFAULT, the local host supplies the
default network route.
11.2 – Examples
1.TCPIP> SET CONFIGURATION START ROUTING /SUPPLY
Starts ROUTED dynamic routing when TCP/IP Services is started.
The local host both broadcasts and receives network routing
information.