| Previous | Contents | Index |
After you install HP TCP/IP Services for OpenVMS, you need to enable the components and characteristics you require for your particular system using the menu-driven TCPIP$CONFIG configuration procedure.
This chapter explains the TCPIP$CONFIG menus, provides sample installation output, and summarizes additional configuration and setup tasks.
Table 3-1 lists the tasks involved in configuring TCP/IP Services, and the sections that describe these tasks.
| Step | Task to perform... | Described in... |
|---|---|---|
| 1 | Assemble system information to prepare for running TCPIP$CONFIG. | Section 1.3 |
| 2 | If applicable, add your system to the OpenVMS Cluster to perform as a TCP/IP host | Section 3.2 |
| 3 | Run TCPIP$CONFIG. (Alternatively, have TCP/IP Services configured automatically, as explained in step 4.) If you have a TCP/IP Services V4. x configuration on your system, answer prompts to convert existing databases or to create new ones. | Section 3.4 |
| 4 | If you prefer, have TCP/IP Services software configured automatically by a DHCP server. | Section 3.3 |
| 5 | Manually configure the TCP/IP Services core environment, clients, and servers using TCPIP$CONFIG. | Sections 3.4.4 through 3.4.6 |
| 6 | Configure the optional components using TCPIP$CONFIG, as applicable. | Section 3.4.7 |
| 7 | Start TCP/IP Services. | Section 3.6 |
| 8 | Verify the configuration. | Section 3.9 |
| 9 | Complete additional configuration tasks, as appropriate. | Section 3.10 |
Configuration changes made to the TCP/IP Services software do not take effect until you start or restart the software. See Section 3.6. |
Beginning with Version 5.5, the TCPIP$CONFIG.COM configuration procedure for TCP/IP Services can create OpenVMS accounts using larger system parameter values than in previous versions. Only new accounts get these larger values. These values are useful on OpenVMS Alpha systems but essential on OpenVMS I64 systems.
To have your OpenVMS I64 system join an OpenVMS Cluster as a TCP/IP host, HP recommends adding the system to the cluster before you configure TCP/IP Services. The guidelines in Section 3.2.1 assume you have followed this recommendation.
If you configure TCP/IP Services before you add the system to a cluster,
see Section 3.2.2.
3.2.1 Running a Newly Configured Host in the Cluster
The following recommendations assume you are configuring TCP/IP Services on the system after having added the system to the OpenVMS Cluster.
If TCP/IP Services has previously been installed on a node in the cluster and you encounter problems running a TCP/IP component on the system, modify the cluster SYSUAF to increase the parameter values for the account used by the affected component. The minimum recommended values are listed in Table 3-2.
| Parameter | Minimum Value |
|---|---|
| ASTLM | 100 |
| BIOLM | 400 |
| BYTLM | 108000 |
| DIOLM | 50 |
| ENQLM | 100 |
| FILLM | 100 |
| PGFLQUOTA 1 | 50000 |
| TQELM | 50 |
| WSEXTENT | 4000 |
| WSQUOTA | 1024 |
The IMAP, DHCP, and XDM components can exhibit account parameter
problems if the value assigned to PGFLQUOTA or to any of the other
listed parameters is too low. Use the OpenVMS AUTHORIZE utility to
modify SYSUAF parameters. For more information, refer to the
HP OpenVMS System Management Utilities Reference Manual: A-L.
3.2.2 Configuring TCP/IP Services Before Adding the System to the Cluster
If you configure TCP/IP Services before you add the system to a cluster,
when you add the system to the cluster the owning UIC for each of the
TCP/IP service SYS$LOGIN directories (TCPIP$service-name,
where service-name is the name of the service) may be
incorrect. Use the OpenVMS AUTHORIZE utility to correct these UICs.
3.3 Automatic Configuration of TCP/IP Services Using DHCP Client
Beginning with Version 5.5, TCP/IP Services supports the DHCP client, which allows you to have your system configured automatically by a DHCP server. You can achieve this in one of two ways:
WORF_system> @sys$startup:tcpip$startup %TCPIP-I-NOCONFIG, TCP/IP Services is not configured Autoconfigure TCP/IP Services using DHCP client [YES]: |
HP TCP/IP Services for OpenVMS Interface & Address Configuration Menu
Hostname Details: Configured=Not Configured, Active=Not Configured
Configuration options:
1 - WE0 Menu (EWA0: TwistedPair 1000mbps)
2 - IE0 Menu (EIA0: TwistedPair 100mbps)
[E] - Exit menu
Enter configuration option:
|
HP TCP/IP Services for OpenVMS Interface WE0 Configuration Menu
Configuration options:
1 - Add a primary address on WE0
2 - Add an alias address on WE0
3 - Enable DHCP client to manage address on WE0
[E] - Exit menu
Enter configuration option:
|
Configure WE0 as the DHCP PRIMARY? (Y,N,HELP) [Y]: |
HP TCP/IP Services for OpenVMS Interface & Address Configuration Menu
Hostname Details: Configured=Not Configured, Active=Not Configured
Configuration options:
1 - WE0 Menu (EWA0: TwistedPair 1000mbps) (Managed by DHCP client - PRIMARY)
2 - IE0 Menu (EIA0: TwistedPair 100mbps)
[E] - Exit menu
Enter configuration option:
|
Verify that a DHCP Server is already setup and running on another system first; otherwise, you could receive errors when the DHCP Client tries to start, similar to the following:
The DHCP server needs the following files to be setup for success:
|
The TCPIP$CONFIG configuration procedure displays menus from which you do the following:
To get started, enter:
$ @SYS$MANAGER:TCPIP$CONFIG |
If you have a TCP/IP Services for OpenVMS (UCX) configuration in place (Version 4.x), and you have never configured a Version 5.x product on the system, the procedure begins by asking you whether to convert the Version 4.x (UCX) TCP/IP Services configuration files:
Convert the old configuration files [Y] |
Unless you respond NO to the prompt, the procedure converts existing configuration files to new configuration files.
If you have already configured this product, the procedure indicates that no new configuration files are being created:
Checking TCP/IP Services for OpenVMS configuration database files. No new database files were created. |
The following sample output shows the start of the TCPIP$CONFIG procedure and a portion of the conversion of a previous configuration:
TCP/IP Network Configuration Procedure
This procedure helps you define the parameters required
to run HP TCP/IP Services for OpenVMS on this system.
NOTE:
TCP/IP has been previously configured from an earlier version
of this product. You can avoid a complete reconfiguration of
TCP/IP by allowing this procedure to automatically convert the
old configuration files. If you choose not to do this now, you
will not be asked again. At the end of the conversion you will
be able to further modify your configuration.
Convert the old configuration files [Y]: [Return]
Preparing files for conversion...
UCX$SERVICE.DAT --> TCPIP$SERVICE.DAT
UCX$HOST.DAT --> TCPIP$HOST.DAT
UCX$NETWORK.DAT --> TCPIP$NETWORK.DAT
UCX$ROUTE.DAT --> TCPIP$ROUTE.DAT
UCX$PROXY.DAT --> TCPIP$PROXY.DAT
UCX$CONFIGURATION.DAT --> TCPIP$CONFIGURATION.DAT
UCX$EXPORT.DAT --> TCPIP$EXPORT.DAT
UCX$PRINTCAP.DAT --> TCPIP$PRINTCAP.DAT
No new database files were created.
FTP SERVER Configuration
LPD SERVER Configuration
Service is not defined in the SYSUAF.
Nonprivileged user access is not enabled.
By default, HP TCP/IP Services for OpenVMS configures
LPD such that nonprivileged users cannot modify queue entries.
Creating TCPIP$AUX identifier with a value of 3655
HP TCP/IP Services for OpenVMS supports Line Printer Daemon
Protocol (see RFC 1179).
LPD requires the following:
- Name of the local queue
- Name of the remote queue
- Name of the remote host
- Spooling directory for the local queue
To add or delete printers in the TCPIP PRINTCAP database, use the
$RUN SYS$SYSTEM:TCPIP$LPRSETUP command.
.
.
.
|
If you do not have an existing TCP/IP Services configuration in place from a previous version of the product, the procedure begins by creating configuration database files, as shown in the following sample output:
Checking TCP/IP Services for OpenVMS configuration database files. Creating SYS$COMMON:[SYSEXE]TCPIP$SERVICE.DAT;1 Creating SYS$COMMON:[SYSEXE]TCPIP$HOST.DAT;1 Creating SYS$COMMON:[SYSEXE]TCPIP$NETWORK.DAT;1 Creating SYS$COMMON:[SYSEXE]TCPIP$ROUTE.DAT;1 Creating SYS$COMMON:[SYSEXE]TCPIP$PROXY.DAT;1 Creating SYS$COMMON:[SYSEXE]TCPIP$CONFIGURATION.DAT;1 Interface - NONE configured. DHCP will be the default. |
After the configuration files are converted or created, the Main Configuration menu is displayed:
HP TCP/IP Services for OpenVMS Configuration Menu
Configuration options:
1 - Core environment
2 - Client components
3 - Server components
4 - Optional components
5 - Shutdown HP TCP/IP Services for OpenVMS
6 - Startup HP TCP/IP Services for OpenVMS
7 - Run tests
A - Configure options 1 - 4
[E] - Exit configuration procedure
Enter configuration option:
|
The options are as follows:
| Option | Description | |
|---|---|---|
| 1 | Core environment | Configure software associated with the Network, Internet, and Transport layers of the TCP/IP architecture (Section 3.4.4). |
| 2 | Client components | Configure application software and related services (Section 3.4.5). |
| 3 | Server components | Configure server software and related services (Section 3.4.6). |
| 4 | Optional components | Configure software necessary if you plan to allow Anonymous FTP access, enable Kerberos authentication for the TELNET server, enable failSAFE IP support, or run such products as PATHWORKS for OpenVMS (Advanced Server), Advanced Server for OpenVMS, DECnet over TCP/IP, or any applications that use the Stanford Research Institute (SRI) QIO application programming interface (Section 3.4.7) |
| 5 | Shutdown TCP/IP Services for OpenVMS | Stop TCP/IP Services (Section 3.7). |
| 6 | Startup TCP/IP Services for OpenVMS | Start TCP/IP Services (Section 3.8). |
| 7 | Run tests | Run the installation verification procedure (Section 3.9). |
| A | Configure options 1 - 4 | Configure all the TCP/IP Services components (the core, client, server, and optional services). The procedure takes you through each of the configuration options. |
| E | Exit the configuration procedure | Return to the system prompt. |
If you do not have experience with the TCP/IP Services product, you should use the configuration menus provided by the TCPIP$CONFIG configuration procedure to configure the product (use options 1 through 4, or option A). If you have experience configuring the software and want to bypass the configuration menus, you can add one or more command parameters when you run TCPIP$CONFIG. For information about the command parameters, see Section 3.5. |
To display the Core Environment Configuration menu, choose option 1 (Core environment) from the Main Configuration menu. If you chose option A from the Main Configuration menu to configure all the TCP/IP Services components, the Core Environment Configuration menu is displayed first. The sample output in the following sections show the progression of the procedure when you choose option A.
You are required to configure the Domain, Interfaces, and Routing services; BIND Resolver and Time Zone are optional.
Use the Interfaces menu (option 2) to set up an interface under control of the DHCP client. If you mark a DHCP client interface as primary, you might not need to set up the other Core Environment components. Ask your network manager whether these components are configured by DHCP. For more information, see the DHCP client documentation. |
HP TCP/IP Services for OpenVMS Core Environment Configuration
Menu
Configuration options:
1 - Domain
2 - Interfaces
3 - Routing
4 - BIND Resolver
5 - Time Zone
A - Configure options 1 - 5
[E] - Exit menu
Enter configuration option: A [Return]
|
If you have run the TCPIP$IP6_SETUP.COM procedure to enable IPv6, and then you run the TCPIP$CONFIG.COM command procedure, TCPIP$CONFIG.COM displays the following warning message prior to displaying the Core Environment configuration options. For more information, see Chapter 4.
|
The following sections include sample output for the core environment components. The samples reflect a TCP/IP Services product configuration for a system on which other TCP/IP Services configurations are in place. The output varies for a new TCP/IP Services installation (see Appendix A).
Enter your responses to the menu questions using the information from your configuration planning worksheet ( Section 1.3).
| Previous | Next | Contents | Index |