| Previous | Contents | Index |
After you install Compaq 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 procedure.
This chapter explains the TCPIP$CONFIG menus, provides sample
installation output, and summarizes additional configuration and setup
tasks.
3.1 Recommended Order for Configuring TCP/IP Services
Table 3-1 lists the tasks involved in configuring the TCP/IP Services components and functionality, and the sections that describe these tasks.
| Step | Task | Described in... |
|---|---|---|
| 1 | Assemble system information to prepare for running TCPIP$CONFIG. | Section 1.3 |
| 2 | Run TCPIP$CONFIG. If you have a TCP/IP Services V4. x configuration on your system, answer prompts to convert existing databases or create new ones. | Section 3.3 |
| 3 | If preferred, have TCP/IP Services software configured automatically by a DHCP server. | Section 3.2 |
| 4 | Manually configure the major components and functionality using TCPIP$CONFIG. | Section 3.3.4 |
| 5 | Configure the optional components using TCPIP$CONFIG, as applicable. | Section 3.3.7 |
| 6 | Start TCP/IP Services. | Section 3.5 |
| 7 | Verify the configuration. | Section 3.6 |
| 8 | Complete additional configuration tasks, as appropriate. | Section 3.7 |
TCP/IP Services Version 5.1 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:
Configuration options:
1 - Configure interface manually (Current default)
2 - Let DHCP configure interface
|
The TCPIP$CONFIG 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 from a V4.x version of the product, and you have never configured a V5.x product on the system, the procedure begins by prompting you whether to convert the old 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 Compaq 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, Compaq TCP/IP Services for OpenVMS configures
LPD such that nonprivileged users cannot modify queue entries.
Creating TCPIP$AUX identifier with a value of 3655
Compaq 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:
TCP/IP Network Configuration Procedure This procedure helps you define the parameters required to run Compaq TCP/IP Services for OpenVMS on this system. Checking TCP/IP Services for OpenVMS configuration database files. Creating SYS$COMMON:[SYSEXE]TCPIP$SERVICE.DAT Creating SYS$COMMON:[SYSEXE]TCPIP$HOST.DAT Creating SYS$COMMON:[SYSEXE]TCPIP$NETWORK.DAT Creating SYS$COMMON:[SYSEXE]TCPIP$ROUTE.DAT Creating SYS$COMMON:[SYSEXE]TCPIP$PROXY.DAT Creating SYS$COMMON:[SYSEXE]TCPIP$CONFIGURATION.DAT Compaq TCP/IP Services for OpenVMS requires a definition for at least one interface. There are no interfaces defined on this system. Please select the Interface option from the Core Environment Menu. |
After the configuration files are converted or created, the Main Configuration menu is displayed:
Compaq TCP/IP Services for OpenVMS Configuration Menu
Configuration options:
1 - Core environment
2 - Client components
3 - Server components
4 - Optional components
5 - Shutdown Compaq TCP/IP Services for OpenVMS
6 - Startup Compaq 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:
If you do not have experience with the TCP/IP Services product, you
should use the configuration menus. However, if you have experience
configuring the software and want to bypass the menus, you can add one
or more command parameters when you run TCPIP$CONFIG. For information
about the command parameters, see Section 3.4.
3.3.4 Configuring the Core Environment
From the Core Environment Configuration menu, enter option A to configure all the core environment components. Alternatively, you can configure one option at a time. The sample output in the following sections show the progression of the procedure when you choose to configure all components.
If you select option A from the Main Configuration menu, the Core Environment Configuration menu is displayed first. You can enter option A to configure all the core environment components. You are required to configure the Domain, Interfaces, and Routing options; the 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. |
Compaq 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]
|
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).
3.3.4.1 Domain Configuration
The following is a sample output for configuring the domain:
DOMAIN Configuration Enter Internet domain [budget.acme.com]: widgets.com [Return] |
The following is a sample output for configuring the Internet interface:
INTERFACE Configuration
The Ethernet device(s) on your system are: EWA0:
Start of configuration questions for Internet interface WE0.
WE0 is the Ethernet device EWA0:
Interface: WE0
IP_Addr: 10.10.2.2 NETWRK: 255.255.255.0 BRDCST: 10.10.2.255
C_Addr: C_NETWRK: C_BRDCST:
Flags:
Receive buffer: 0
Compaq TCP/IP Services for OpenVMS Interface WE0 Reconfiguration
Menu
Reconfiguration options:
1 - Configure interface manually (Current default)
2 - Let DHCP configure interface
[E] - Exit menu (Do not reconfigure interface WE0)
Enter configuration option: [Return]
|
In this example, no changes are made to the interface.
3.3.4.3 Dynamic Routing Configuration
The following is a sample output for configuring dynamic routing:
DYNAMIC ROUTING Configuration
Dynamic routing has not been configured.
You may configure dynamic ROUTED or GATED routing.
You cannot enable both at the same time. If you want
to change from one to the other, you must disable the
current routing first, then enable the desired routing.
If you enable dynamic ROUTED routing, this host will use the
Routing Information Protocol (RIP) - Version 1 to listen
for all dynamic routing information coming from other
hosts to update its internal routing tables.
It will also supply its own Internet addresses to
routing requests made from remote hosts.
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:
Routing Information Protocol (RIP) - Version 1 & 2
Router Discovery Protocol (RDISC)
Open Shortest Path First (OSPF)
Exterior Gateway Protocol (EGP)
Border Gateway Protocol (BGP-4)
Static routes
* Do you want to configure dynamic ROUTED or GATED routing [NO]: YES [Return]
* Do you want to enable GATED routing configuration [NO]: [Return]
ROUTED option
If you enable the 'supply' option of dynamic routing,
this host will supply dynamic routing information to
other hosts on the network whether it is acting as an
internetwork gateway or not.
* Do you want this host to supply its dynamic routing information [NO]: [Return]
|
The following is a sample output for configuring the BIND resolver:
A BIND resolver has already been configured. BIND Resolver Configuration Transport: UDP Domain: budget.acme.com Retry: 4 Timeout: 4 Servers: island.budget.acme.com Path: No values defined * Do you want to reconfigure BIND [NO]: [Return] |
In this example, no changes are made to the BIND resolver.
3.3.4.5 Time Zone Configuration
The following is a sample output for configuring the time zone:
TIME ZONE Configuration TCPIP uses timezone information provided by the OpenVMS Operating System. No additional timezone configuration is needed for TCPIP when the operating system is configured correctly. This section verifies the current OpenVMS timezone configuration. A warning message (TCPIP-W-) indicates that corrective action should be taken. TCPIP will appear to operate but components may display either the wrong time or a time inconsistent with other applications. %TCPIP-I-INFO, Logical name SYS$TIMEZONE_RULE found. -TCPIP-I-INFO, Software for automatic Summer/Winter time (TDF) change -TCPIP-I-INFO, is present. -TCPIP-I-INFO, Further action to ensure TDF change is not necessary. %TCPIP-I-NORMAL, timezone information verified Press Return to continue ... |
After the core environment is configured, the procedure returns to the Core Environment menu. Enter option E to exit. If you selected option A in the Main Configuration menu, the Client Components Configuration menu is displayed next.
Compaq TCP/IP Services for OpenVMS Client Components Configuration Menu
Configuration options:
1 - FTP Enabled Stopped
2 - NFS Client Enabled Stopped
3 - REXEC and RSH Enabled Stopped
4 - RLOGIN Enabled Stopped
5 - SMTP Enabled Stopped
6 - TELNET Enabled Stopped
7 - DHCP Disabled Stopped
8 - Telnetsym Disabled Stopped
A - Configure options 1 - 8
[E] - Exit menu
|
Note that the sample Client Components Configuration menu shows most components enabled and all of them stopped. Components are enabled if they have been enabled in the TCP/IP Services configuration database (TCPIP$CONFIGURATION.DAT). The enabled services are started the next time TCP/IP Services is started. You can also start (or stop) a specific component, without having to restart TCP/IP Services, by selecting the "Start service" option from that component's configuration menu. In addition, you can use command procedures to start or stop a specific component, as explained in Section 3.9.
The initial status of the components depends on whether you have other TCP/IP Services installations in place on the system, and whether the software or individual components have been started. On a new system, all the components would be disabled (the default). The status of components is also affected by the selections you made from the Core Environment menu.
To minimize resource consumption, enable and start only those components that you are sure to use. Disable those you do not plan to use.
You can enter option A to configure all the client components.
The following is an example of the output for configuring an FTP client. The configuration output for other clients might vary. Note that after you configure a client (such as FTP) that has an associated server, the configuration prompts you about whether to configure the corresponding server.
Enter configuration option: 1 [Return]
FTP CLIENT Configuration
Service is enabled on specific node.
Service is stopped.
FTP CLIENT configuration options:
1 - Disable service on this node
2 - Start service on this node
[E] - Exit FTP_CLIENT configuration
Enter configuration option: 1 [Return]
The FTP SERVER is enabled.
* Do you want to configure the FTP SERVER [NO] ? [Return]
|
In the preceding example, the FTP client was originally enabled, and you selected option 1 to disable it. The following example shows the configuration output that might be seen if you want to enable an FTP client that had been disabled.
FTP CLIENT Configuration
Service is not enabled.
Service is stopped.
FTP CLIENT configuration options:
1 - Enable service on this node
2 - Enable & Start service on this node
[E] - Exit FTP_CLIENT configuration
Enter configuration option: 2 [Return]
|
In this example, as with the previous one, the TCP/IP Services software has already been started, so you have the choice of starting the client as well as enabling it. If you select option 1, the FTP service will be enabled and FTP will start the next time the TCP/IP Services is started. If you select option 2, the FTP service will be started immediately and then every time the TCP/IP kernel is started.
If the TCP/IP Services software had not already been started, then the FTP Client Components Configuration menu would only give you the option of enabling the component, as in the following example:
1 - Enable service on this node
[E] - Exit FTP_CLIENT configuration
|
If you selected option A from the Main Configuration menu, the Server Components menu is displayed after you exit the Client Components Configuration menu.
Compaq TCP/IP Services for OpenVMS Server Components Configuration Menu
Configuration options:
1 - BIND Disabled Stopped 11 - NTP Enabled Stopped
2 - BOOTP Disabled Stopped 12 - PC-NFS Enabled Stopped
3 - DHCP Disabled Stopped 13 - POP Enabled Stopped
4 - FINGER Enabled Stopped 14 - PORTMAPPER Enabled Stopped
5 - FTP Enabled Stopped 15 - RLOGIN Enabled Stopped
6 - LBROKER Enabled Stopped 16 - RMT Enabled Stopped
7 - LPR/LPD Enabled Stopped 17 - SNMP Enabled Stopped
8 - METRIC Enabled Stopped 18 - TELNET Enabled Stopped
9 - NFS Enabled Stopped 19 - TFTP Enabled Stopped
10 - LOCKD/STATD Disabled Stopped 20 - XDM Disabled Stopped
A - Configure options 1 - 20
[E] - Exit menu
Enter configuration option:
|
Components are enabled if they have been added to the TCP/IP Services configuration database (TCPIP$CONFIGURATION.DAT), and they are started the next time TCP/IP Services is started. You can also start (or stop) a specific component, without having to restart TCP/IP Services, by selecting the "Start service" option from that component's configuration menu. In addition, you can use command procedures to start or stop a specific component, as explained in Section 3.9.
The initial status of the components depends on whether you have other TCP/IP Services installations in place on the system, and whether the software or individual components have been started. To minimize resource consumption, enable and start the specific server components you plan to use, and disable those you do not plan to use. You can enter option A to configure all the server components.
For server components that have associated client components (such as the FTP server and client), when you configure the server component, you will be prompted about whether you want to configure the corresponding client component.
The following is an example of an XDM server configuration output. The configuration displays for other server components might vary.
Enter configuration option: 20 [Return] XDM Configuration Service is defined in the SYSUAF. Service is not defined in the TCPIP$SERVICE database. Service is not enabled. Service is stopped. XDM configuration options: 1 - Enable service on this node [E] - Exit XDM configuration Enter configuration option: |
After you configure the server components, press Return to go to the Main Configuration menu. If you entered option A in the Main Configuration menu, the Optional Components Configuration menu is displayed next.
| Previous | Next | Contents | Index |