| Previous | Contents | Index |
You may need to configure optional product components if you plan to do one or more of the following:
To configure the optional components, enter option 4 from the Main Configuration menu. The Optional Components Configuration menu displays the following menu options:
Compaq TCP/IP Services for OpenVMS Optional Components Configuration
Menu
Configuration options:
1 - Configure PWIP Driver (for DECnet-Plus and PATHWORKS)
2 - Configure SRI QIO Interface (INET Driver)
3 - Set up Anonymous FTP Account and Directories
A - Configure options 1 - 3
[E] - Exit menu
Enter configuration option:
|
Enter the options that are appropriate for your system: the PWIP Driver, the SRI QIO Interface, or Anonymous FTP Accounts and Directories.
The following shows the output when configuring the PWIP driver:
Enter configuration option: 1 [Return]
TCPIP Transport for DECnet and Pathworks Service Configuration
Service is enabled on specific node.
Service is stopped.
TCPIP Transport for DECnet and Pathworks Service configuration options:
1 - Disable service on this node
[E] - Exit PWIP_DRIVER configuration
Enter configuration option:
|
If you are an experienced TCP/IP Services user, you may want to bypass the configuration menus to enable or disable functionality, as follows:
@SYS$MANAGER:TCPIP$CONFIG [option] {DISABLE | ENABLE} [CLUSTER]
|
| Option | Description |
|---|---|
| ALL | Configures the core environment and all client and server components. |
| CLIENT | Configures all client components and related software. |
| MINIMUM | Configures the domain, Internet interfaces, remote login, FTP client, FTP server, TELNET client, and TELNET server. Prompts you for optional components. |
| SERVER | Configures all server components and related software. |
| WORKSTATION | Configures the BIND resolver, the domain, dynamic routing, Internet interfaces, time zone, remote login, remote shell, remote executive, FTP client, FTP server, TELNET client, TELNET server, and SMTP. |
| Keyword | Description |
| CLUSTER | Configures all specified components clusterwide (except for the BIND server and SMTP, which you cannot configure clusterwide). |
| ENABLE | Enables the specified components. |
| DISABLE | Disables the specified components. |
$ @SYS$MANAGER:TCPIP$CONFIG CLIENT ENABLE CLUSTER |
The procedure implements two levels of enabling and disabling: clusterwide and single node (except for SMTP, which is configured and enabled as node specific only). |
Whenever you configure the core TCP/IP Services software (the core environment), you must then start (or restart) TCP/IP Services to make the changes take effect. Do this before you run tests or customize the environment. Start TCP/IP Services from TCPIP$CONFIG by following the procedure described in Section 3.5.1.
If you made changes to the client, server, or optional components only (that is, not to the core environment), you do not have to restart TCP/IP Services: you can restart the affected components individually to initialize the changes, by selecting the "Start service" option in the affected component's configuration menu. Alternatively, you can use each component's startup command procedure, as described in Section 3.9.
You can have the TCP/IP Services software started automatically each
time the OpenVMS operating system is rebooted, or you can restart the
software manually, as explained in Section 3.8.
3.5.1 Starting TCP/IP Services Using TCPIP$CONFIG
After configuring the core environment, start TCP/IP Services on your system by selecting option 6 (Startup Compaq TCP/IP Services for OpenVMS) from the Main Configuration menu, as in the following example:
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: 6
Begin Startup...
|
%TCPIP-I-INFO, TCP/IP Services startup beginning at 5-DEC-2000 15:27:08.34 %TCPIP-I-NORMAL, timezone information verified %RUN-S-PROC_ID, identification of created process is 00000D42 %TCPIP-I-SETLOCAL, setting domain and/or local host %TCPIP-I-STARTCOMM, starting communication %TCPIP-I-SETPROTP, setting protocol parameters %TCPIP-I-DEFINTE, defining interfaces %TCPIP-I-STARTNAME, starting name service %TCPIP-S-STARTDONE, TCP/IP Kernel startup completed %TCPIP-I-LOADSERV, loading TCPIP server proxy information %TCPIP-I-SERVLOADED, auxiliary server loaded with 0 proxy records -TCPIP-I-SERVSKIP, skipped 0 communication proxy records -TCPIP-I-SERVTOTAL, total of 6 proxy records read %TCPIP-S-STARTDONE, TCPIP$PROXY startup completed %TCPIP-S-STARTDONE, TCPIP$PORTMAPPER startup completed %TCPIP-S-STARTDONE, TCPIP$FINGER startup completed %TCPIP-S-STARTDONE, TCPIP$FTP startup completed %TCPIP-S-STARTDONE, TCPIP$FTP_CLIENT startup completed %TCPIP-S-STARTDONE, TCPIP$LBROKER startup completed %TCPIP-S-STARTDONE, TCPIP$LOCKD startup completed %TCPIP-S-STARTDONE, TCPIP$LPD startup completed %TCPIP-S-STARTDONE, TCPIP$LPD_CLIENT startup completed %TCPIP-S-STARTDONE, TCPIP$METRIC startup completed %TCPIP-S-STARTDONE, TCPIP$NFS startup completed %TCPIP-S-STARTDONE, TCPIP$NFS_CLIENT startup completed %TCPIP-S-STARTDONE, TCPIP$NTP startup completed %TCPIP-S-STARTDONE, TCPIP$PCNFS startup completed %TCPIP-S-STARTDONE, TCPIP$POP startup completed %RUN-S-PROC_ID, identification of created process is 00000C4E %TCPIP-S-STARTDONE, TCPIP$PWIP_DRIVER startup completed %TCPIP-S-STARTDONE, TCPIP$REXEC startup completed %TCPIP-S-STARTDONE, TCPIP$RLOGIN startup completed %TCPIP-S-STARTDONE, TCPIP$RMT startup completed %TCPIP-S-STARTDONE, TCPIP$RSH startup completed %TCPIP-S-STARTDONE, TCPIP$SMTP startup completed %TCPIP-S-STARTDONE, TCPIP$SNMP startup completed %TCPIP-S-STARTDONE, TCPIP$STATD startup completed %TCPIP-S-STARTDONE, TCPIP$TELNET startup completed %TCPIP-S-STARTDONE, TCPIP$TELNETSYM startup completed %TCPIP-S-STARTDONE, TCPIP$TFTP startup completed %TCPIP-S-STARTDONE, TCPIP$XDM startup completed %TCPIP-S-STARTDONE, TCP/IP Services startup completed at 5-DEC-2000 15:27:50.47 Startup request completed. Press Return to continue ... |
You can verify the configuration by running the installation verification procedure (IVP).
You should run the IVP if the following apply:
Before you run the IVP, make sure TCP/IP Services has started and you have SYSPRV, OPER, NETMBX, and TMPMBX privileges.
You can run the IVP from the TCPIP$CONFIG configuration procedure or by
command line at the OpenVMS DCL prompt. When you run the IVP from
TCPIP$CONFIG, you have the option of running an additional test that
verifies the SNMP configuration.
3.6.1 Running the IVP from the TCPIP$CONFIG Command Procedure
In the TCP/IP Services for OpenVMS Main Configuration menu, select option 7 (Run tests). The Test menu appears, as in the following example:
Compaq TCP/IP Services for OpenVMS TEST Menu
Test options:
1 - Internet IVP
2 - SNMP IVP
A - Tests 1 - 2
[E] - Exit menu
Enter test option:
|
Select the appropriate option for the test you want to perform.
3.6.2 Running the IVP from the OpenVMS DCL Prompt
To run the IVP at the DCL prompt, any time after exiting the configuration procedure, enter the following command. This procedure performs the same test as option 1 of the TCPIP$CONFIG Test menu (Internet IVP).
$ @SYS$TEST:TCPIP$IVP |
When you select option 1 or A from the TCPIP$CONFIG Test menu, or run the TCPIP$IVP command procedure at the command line, the IVP tests the basic TCP/IP Services for OpenVMS software configuration, as in the following example. Here, the test completes successfully.
Enter test option: 1 [Return] %%% TCPIP IVP: started %%% UDP/IP test started at 31-MAR-2000 16:13:03.02 UDP/IP test ended at 31-MAR-2000 16:13:03.69 UDP/IP transferred successfully in 0 seconds 4198400 bytes TCP/IP test started at 31-MAR-2000 16:13:04.20 TCP/IP test ended at 31-MAR-2000 16:13:41.21 TCP/IP transferred successfully in 37 seconds 4198400 bytes RAW_IP test started at 31-MAR-2000 16:13:41.71 RAW_IP test ended at 31-MAR-2000 16:13:41.79 RAW_IP transferred successfully in 0 seconds 251000 bytes %%% TCPIP IVP: completed successfully %%% IVP request completed. Press Return to continue ... |
If the IVP does not complete successfully, the procedure displays error messages. All IVP errors use the same format as OpenVMS system messages. For example:
%TCPIP-E-IDENT, explanation of error. |
Table 3-2 lists some common problems that cause IVP error messages. If the recommended action does not correct the problem, contact your Compaq support representative.
| Problem | Corrective Action |
|---|---|
| Network configuration is incorrect. | Shut down TCP/IP Services and rerun the configuration procedure. |
| Startup fails. |
Check the system parameters in the MODPARAMS.DAT file and adjust them
if necessary. (See Section 1.2.7.)
Shut down and restart TCP/IP Services. |
| Installation kit is defective. | Request a replacement kit. |
| IVP fails because the PAK is missing. | Register a Compaq TCP/IP Services for OpenVMS PAK. |
If you select option 2 or A from the TCPIP$CONFIG Test menu, the IVP tests the SNMP service, as in the following example:
Begin SNMP IVP...
The SNMP IVP requires that TCPIP/IP Services be running.
It performs the following startups and shutdowns on the
SNMP service only (other TCP/IP services are not affected):
- If SNMP is running, shuts down SNMP before initial configuration
- Starts SNMP and runs tests
- Shuts down SNMP and restores initial configuration
- Before exiting, starts SNMP
Shutting down the SNMP service... done.
Creating temporary read/write community SNMPIVP_6520.
Enabling SET operations.
Starting up the SNMP service... done.
Saving sysContact: Ralph Nickleby
Setting sysContact to: Julius Caesar
Retrieved sysContact: Julius Caesar
(Retrieved value matches SET value.)
Restoring sysContact to: Ralph Nickleby
Saving snmpEnableAuthenTraps: 1 (enabled)
Setting snmpEnableAuthenTraps to: 2 (disabled)
Retrieved snmpEnableAuthenTraps: 2 (disabled)
(Retrieved value matches SET value.)
Restoring snmpEnableAuthenTraps: 1 (enabled)
Disabling SET operations.
Deleting temporary read/write community SNMPIVP_6520.
Shutting down and restarting the SNMP service...
Shutting down the SNMP service... done.
Starting up the SNMP service... done.
SNMP IVP request completed.
Press Return to continue ...
|
If one of the SNMP tests fails, you will see messages such as the following:
SNMPIVP: unexpected text in response to SNMP request: "No reply." See file SYS$SYSDEVICE:[TCPIP$SNMP]TCPIP$SNMP_REQUEST.DAT for more details. Verify that SNMP trace is not enabled. sysContact could not be retrieved. Status = 0 The SNMP IVP has NOT completed successfully. |
In this case, the error could indicate that not all SNMP components
have started, or that SNMP tracing is enabled and needs to be disabled.
For information about SNMP trace, see the Compaq TCP/IP Services for OpenVMS Management guide.
3.7 Additional Configuration Tasks
After you run TCPIP$CONFIG and enable the functionality and components appropriate for your network, you need to complete additional configuration tasks to enable access to product applications. TCP/IP Services provides a management command interface and logical names you can use to modify or customize the software for your environment.
The additional configuration tasks include:
Many of the services require additional configuration or optimization.
For more information about the additional configuration tasks and how
each service can be further configured, refer to the Compaq TCP/IP Services for OpenVMS Management
guide.
3.8 Starting and Stopping TCP/IP Services
You can use commands in your OpenVMS startup file to have TCP/IP Services started and stopped automatically when the OpenVMS system starts up or shuts down, as explained in Section 3.8.1. These commands start and stop all the TCP/IP Services components installed on your system. Alternatively, you can start and stop individual TCP/IP Services client or server components without affecting the other TCP/IP Services components currently running. For information about starting and stopping individual components, see Section 3.9.
If necessary, you can start and stop TCP/IP Services manually, as
explained in Section 3.8.2.
3.8.1 Automatically Starting and Stopping TCP/IP Services
To allow TCP/IP Services software to start automatically when the system starts up and to stop automatically when the system shuts down, edit the SYS$COMMON:[SYSMGR]SYSTARTUP_VMS.COM file and include the following command:
@SYS$STARTUP:TCPIP$STARTUP |
If your system had earlier versions of TCP/IP Services, UCX$STARTUP.COM and UCX$SHUTDOWN.COM files might be present. These are no longer applicable; delete any definition of them from SYS$MANAGER:SYSTARTUP_VMS.COM.
For TCP/IP Services to start after you log in to your OpenVMS account, the OpenVMS systemwide login procedure (typically SYS$MANAGER:SYLOGIN.COM) must have world read and execute protections (W:RE).
To display the current protections, enter the following command:
$ DIR/PROTECTION SYS$MANAGER:SYLOGIN.COM |
The protections are displayed for four groups, each separated by a comma, such as (RWED,RWED,WRE,RE). The protections for the World group are the last ones in the series (in this example, RE). If the protections are not RE, enter:
$ SET PROTECTION=(W:RE) SYS$MANAGER:SYLOGIN.COM |
To start TCP/IP Services manually, enter the following command:
$ @SYS$STARTUP:TCPIP$STARTUP |
To stop TCP/IP Services manually, enter the following command:
$ @SYS$STARTUP:TCPIP$SHUTDOWN |
On a system already running TCP/IP Services, you can configure an individual server or client component without affecting the other TCP/IP Services components running on your system and without having to restart TCP/IP Services.
Most services can be shut down and started independently. This is useful when you change parameters or logical names that require the service to be restarted.
The following files are provided:
To preserve site-specific parameter settings and commands, create the following files. These files are not overwritten when you reinstall TCP/IP Services:
In these file names, service is the name of the service to be started or shut down. For example, use TCPIP$NTP_SHUTDOWN to shut down the NTP service.
For more information, see the Compaq TCP/IP Services for OpenVMS Management guide.
3.10 Specifying TCP/IP Services as the Transport for DECwindows Applications
To enable TCP/IP Services as the transport interface for DECwindows applications, add the following line to the SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COM command procedure:
$ DECW$SERVER_TRANSPORTS == "DECNET,LOCAL,TCPIP" |
Then restart DECwindows:
$ @SYS$STARTUP:DECW$STARTUP RESTART |
If DECnet or DECnet-Plus software runs on the system, start it.
To display DECwindows applications from a DECwindows client (remote host) to a DECwindows server (your workstation), proceed as follows:
$ DECW$SERVER_TRANSPORTS == "DECNET,LOCAL,TCPIP" |
$ SET DISPLAY/CREATE/NODE=remote-host/TRANSPORT=TCPIP |
| Previous | Next | Contents | Index |