To display the Server Components Configuration menu, choose option 3 (Server components) from the Main Configuration menu. If you chose option A from the Main Configuration menu to configure all the TCP/IP Services components, the Server Components Configuration menu displays automatically after you finish configuring the client components.

Compaq TCP/IP Services for OpenVMS Server Components Configuration Menu 1 - BIND Enabled Started 12 - NTP Enabled Started 2 - BOOTP Disabled Stopped 13 - PC-NFS Enabled Started 3 - DHCP Enabled Started 14 - POP Enabled Started 4 - FINGER Enabled Started 15 - PORTMAPPER Enabled Started 5 - FTP Enabled Started 16 - RLOGIN Enabled Started 6 - IMAP Disabled Stopped 17 - RMT Disabled Stopped 7 - LBROKER Disabled Stopped 18 - SNMP Enabled Stopped 8 - LPR/LPD Disabled Stopped 19 - TELNET Enabled Started 9 - METRIC Enabled Started 20 - TFTP Enabled Started 10 - NFS Enabled Started 21 - XDM Enabled Started 11 - LOCKD/STATD Disabled Stopped A - Configure options 1 - 21 [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 choosing 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.10.3.

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 choose 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 are prompted about whether 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: 21 [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 or choose option E to exit from the Server Components Configuration menu. If you chose option A from the Main Configuration menu to configure all the TCP/IP Services components, the Optional Components Configuration menu displays next; otherwise, the procedure returns to the Main Configuration menu.

3.3.7 Configuring the Optional Components

You may need to configure optional product components if you plan to do one or more of the following:

• Run the PATHWORKS for OpenVMS (Advanced Server), the Advanced Server for OpenVMS, or DECnet over TCP/IP software.
• Run or develop applications that use the Stanford Research Institute's (SRI) QIO application programming interface (API).
• Allow Anonymous FTP access.
• Initialize Kerberos authentication for the TELNET server.

To display the Optional Components Configuration menu, choose option 4 (Optional components) from the Main Configuration menu. If you chose option A from the Main Configuration menu to configure all the TCP/IP Services components, the Optional Components Configuration menu displays automatically after you finish configuring the server components.

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 4 - Configure Kerberos Applications A - Configure options 1 - 3 [E] - Exit menu Enter configuration option:

Choose the options that are appropriate for your system: the PWIP Driver, the SRI QIO Interface, Anonymous FTP Accounts and Directories, or Kerberos authentication for TELNET.

• If you want to run PATHWORKS for OpenVMS (Advanced Server), Advanced Server for OpenVMS, or DECnet over TCP/IP, configure the PWIP driver by choosing option 1. In addition, refer to the appropriate documentation for the layered product.
• If you run or develop applications that use the SRI QIO API, choose option 2.
• If you want to allow Anonymous FTP access, choose option 3 to set up an Anonymous FTP account and directories. Make sure you obtain the necessary user information code (UIC) (see Section 1.2.8) and determine guest user privileges.
• If you want to provide the security benefits of Kerberos authentication for the TELNET server, choose option 4 to configure Kerberos. For details about configuring Kerberos support, see Section 3.3.7.1.

The following example shows the output for 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:

3.3.7.1 Configuring and Enabling Kerberos Support

To configure the TELNET service to support Kerberos, follow these steps. For more details about Kerberos features, including prerequisites and instructions for using Kerberos, see the Compaq TCP/IP Services for OpenVMS Release Notes.

1. From the the TCPIP$CONFIG.COM procedure Main Configuration menu, choose option 2 (Client components).
2. From the list of client components, choose option 6 (TELNET).
3. From the TELNET Configuration menu, choose option 1 (Enable service on all nodes). This step creates the TCPIP$TELNET user account and directory.
4. Return to the Main Configuration menu.
5. From the Main Configuration menu, choose option 4 (Optional components).
6. From the Optional Components Configuration menu, choose option 4 (Configure Kerberos Applications). The following menu is displayed:

   Kerberos Applications Configuration Menu TELNET Kerberos is not defined in the TCPIP$SERVICE database. Configuration options: 1 - Add Kerberos for TELNET server 2 - Remove Kerberos for TELNET server [E] - Exit menu Enter configuration option:

7. From the Kerberos Applications Configuration menu, choose option 1 (Add Kerberos for TELNET Server).
8. Exit the command procedure.
9. When you are prompted to start the TELNET service, enter N.
10. Start the TELNET service by executing the TELNET startup procedure, as shown in the following example:

    $ @SYS$STARTUP:TCPIP$TELNET_STARTUP.COM %TCPIP-I-INFO, image SYS$SYSTEM:TCPIP$TELNET_SERVER.EXE installed %TCPIP-I-INFO, image SYS$SYSTEM:TCPIP$TELNET.EXE installed %TCPIP-I-INFO, logical names created %TCPIP-I-INFO, telnet service enabled %TCPIP-I-INFO, telnet (kerberos) service enabled %TCPIP-S-STARTDONE, TCPIP$TELNET startup completed

    
    The information message confirms that the TELNET Kerberos service has been enabled.

If you are an experienced TCP/IP Services user, you may want to bypass the configuration menus to enable or disable functionality, as follows:

1. Log in to the SYSTEM account.
2. Run the TCPIP$CONFIG command procedure and include appropriate options and keywords in the command line, as shown:

   @SYS$MANAGER:TCPIP$CONFIG [option] {DISABLE | ENABLE} [CLUSTER]

   
   In this format, option can be one of the options described in the following table. The table also describes the function of the DISABLE, ENABLE, and CLUSTER keywords.

   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, Rlogin client, 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.

   
   For example, the following command enables the client components for the entire cluster:

   $ @SYS$MANAGER:TCPIP$CONFIG CLIENT ENABLE CLUSTER

   Note 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.7.

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; to initialize the changes, you can restart the affected components individually by choosing 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.10.3.

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.10.

3.6 Stopping TCP/IP Services Using TCPIP$CONFIG

Stop TCP/IP Services on your system by choosing option 5 (Shutdown 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: 5 Begin Shutdown... %TCPIP-I-INFO, TCP/IP Services shutdown beginning at 5-MAR-2002 15:26:14.39 %TCPIP-S-SHUTDONE, TCPIP$FINGER shutdown completed %TCPIP-S-SHUTDONE, TCPIP$FTP_CLIENT shutdown completed %TCPIP-S-SHUTDONE, TCPIP$FTP shutdown completed %TCPIP-S-SHUTDONE, TCPIP$IMAP shutdown completed %TCPIP-S-SHUTDONE, TCPIP$LBROKER shutdown completed %TCPIP-S-SHUTDONE, TCPIP$LOCKD shutdown completed %TCPIP-S-SHUTDONE, TCPIP$LPD_CLIENT shutdown completed %TCPIP-S-SHUTDONE, TCPIP$LPD shutdown completed %TCPIP-S-SHUTDONE, TCPIP$METRIC shutdown completed %TCPIP-S-SHUTDONE, TCPIP$NFS_CLIENT shutdown completed %TCPIP-S-SHUTDONE, TCPIP$NFS shutdown completed %TCPIP-S-SHUTDONE, TCPIP$NTP shutdown completed %TCPIP-S-SHUTDONE, TCPIP$PCNFS shutdown completed %TCPIP-S-SHUTDONE, TCPIP$POP shutdown completed %TCPIP-S-SHUTDONE, TCPIP$PORTMAPPER shutdown completed %TCPIP-S-SHUTDONE, TCPIP$PROXY shutdown completed %TCPIP-S-SHUTDONE, TCPIP$PWIP_DRIVER shutdown completed %TCPIP-S-SHUTDONE, TCPIP$REXEC shutdown completed %TCPIP-S-SHUTDONE, TCPIP$RLOGIN shutdown completed %TCPIP-S-SHUTDONE, TCPIP$RMT shutdown completed %TCPIP-S-SHUTDONE, TCPIP$RSH shutdown completed %TCPIP-S-SHUTDONE, TCPIP$SMTP shutdown completed %TCPIP-S-SHUTDONE, TCPIP$SNMP shutdown completed %TCPIP-S-SHUTDONE, TCPIP$STATD shutdown completed %TCPIP-S-SHUTDONE, TCPIP$TELNETSYM shutdown completed %TCPIP-S-SHUTDONE, TCPIP$TELNET shutdown completed %TCPIP-S-SHUTDONE, TCPIP$TFTP shutdown completed %TCPIP-S-SHUTDONE, TCPIP$XDM shutdown completed %TCPIP-S-SHUTDONE, TCP/IP Kernel shutdown completed %TCPIP-S-SHUTDONE, TCP/IP Services shutdown completed at 5-MAR-2002 15:26:17.78 Shutdown request completed.

3.7 Starting TCP/IP Services Using TCPIP$CONFIG

After configuring the core environment, start TCP/IP Services on your system by choosing 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-MAR-2002 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-PROXYLOADED, loaded 0 NFS proxy records %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 0 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$IMAP 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-MAR-2002 15:27:50.47 Startup request completed. Press Return to continue ...

3.8 Verifying the Configuration

You can verify the configuration by running the installation verification procedure (IVP).

You should run the IVP if any of the following apply:

• You loaded the Product Authorization Key (PAK), and you want to verify that the lower-layer software and the Portmapper service are installed correctly.
• You did not load the PAK, but you want to verify that TCP/IP Services is installed correctly for DECwindows to display the TCP/IP Services applications.
• You require the software to transfer device socket packets that continuously vary in size between a sender and a receiver.
• You need to test the Portmapper service with a pair of client/server programs. The IVP reports the time it took to run the test to SYS$OUTPUT.
• You need to test your SNMP service.

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.8.1 Running the IVP from the TCPIP$CONFIG Command Procedure

In the TCP/IP Services for OpenVMS Main Configuration menu, choose 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:

Choose the appropriate option for the test you want to perform.

3.8.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 (Internet IVP) of the TCPIP$CONFIG Test menu.

$ @SYS$TEST:TCPIP$IVP