[an error occurred while processing this directive]

HP OpenVMS Systems Documentation

Content starts here

HP TCP/IP Services for OpenVMS
Installation and Configuration


Previous Contents Index

3.4.6 Configuring the Server Environment

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

Note

Starting with Version 5.4 of the TCP/IP Services, you can configure and use Secure Shell (SSH) to provide secure login, remote command execution, file copying, and file transfer. For more information about configuring, managing, and using the SSH software, refer to the HP TCP/IP Services for OpenVMS Guide to SSH and the TCP/IP Services release notes.



HP 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         Disabled Stopped    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 - SSH         Enabled  Started
  9 - METRIC       Enabled  Started    20 - TELNET      Enabled  Started
 10 - NFS          Enabled  Started    21 - TFTP        Enabled  Started
 11 - LOCKD/STATD  Disabled Stopped    22 - XDM         Enabled  Started


  A  -  Configure options 1 - 22
 [E] -  Exit menu

Enter configuration option:

Servers are enabled for startup 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 server, without having to restart TCP/IP Services, by choosing the Start service option from that server's configuration menu. In addition, you can use command procedures to start or stop a specific server, as explained in Section 3.11.3.

The initial status of the servers depends on whether you have other TCP/IP Services installations in place on the system, and whether the software or individual servers have been started. To minimize resource consumption, enable and start the specific servers you plan to use, and disable those you do not plan to use. You can choose option A to configure all the servers.

For servers that have associated client services (such as the FTP server and client), when you configure the server you are prompted about whether to configure the corresponding client.

Note

TELNET and RLOGIN are enabled from the client menu. If you want to disable the TELNET or RLOGIN server, then you must disable the service. To enable or disable the TELNET server or the RLOGIN server, use the Client Components Configuration menu, choose the appropriate client, and disable and stop the service by choosing the Disable and Stop service on this node option.

The following is an example of an XDM server configuration output. The configuration displays for other servers 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:

Note

XDM requires the following DECwindows components to be installed:
  • SYS$COMMON:[SYSLIB]DECW$XLIBSHR.EXE
  • SYS$COMMON:[SYSLIB]DECW$XTLIBSHRR5.EXE

The TCPIP$CONFIG configuration procedure checks whether these components are installed. If they are not found, TCPIP$CONFIG notifies you and gives you the option of configuring XDM and installing the DECwindows components later before you attempt to activate XDM. The notification and prompt are as follows:


XDM requires DECwindows components that are not installed.
Attempts to activate XDM will fail.

Type C to continue with XDM configuration, or E to exit [ E ]:

After you configure the servers, 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.4.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.
  • Where a node or cluster has multiple interfaces, enable failSAFE IP to monitor the health of network interface cards and, when an interface fails, to perform a failover to another interface to maintain network connectivity.

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

The Optional Components Configuration menu displays the following menu options:



HP 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
        5 - Configure failSAFE IP

        A - Configure options 1 - 5
       [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, Kerberos authentication for TELNET, and failSAFE IP (provides IP address failover capability for multiple interfaces on a host or cluster).

  • 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.4.7.1.
  • If you want to provide IP address failover capability for multiple interfaces on a host or cluster, choose option 5 to configure failSAFE IP. For details about configuring failSAFE IP support, see Section 3.4.7.2. More information is available also in the HP TCP/IP Services for OpenVMS Management manual.

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.4.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, refer to the HP TCP/IP Services for OpenVMS Management manual.

Note

Before you begin the following steps, make sure the TELNET service is stopped.
  1. From the the TCPIP$CONFIG.COM procedure Main Configuration menu, choose option 2 (Client components).
  2. From the list of client services, 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.

3.4.7.2 Configuring and Enabling failSAFE IP Support

Two steps are necessary to configure failSAFE IP:

  1. Configure the standby IP address on the interfaces for which failover is desired, as explained in Section 3.4.4.4; these are the failover target interfaces for each home interface.
  2. Configure failSAFE IP support by choosing option 5 (Configure failSAFE IP) from the Optional Components Configuration menu.

In addition, you can configure failSAFE IP IPv6 addresses. Information about this is in Section 4.3.

Choosing option 5 from the Optional Components Configuration menu displays the following menu. Note that in this menu, Option 1 (Enable service on all nodes) appears only in a cluster configuration. Choose Option 1 to enable failSAFE IP on all nodes in the cluster, or choose option 2 to enable failSAFE IP on the local node only.


        failSAFE configuration options:

                 1 - Enable service on all nodes
                 2 - Enable service on this node

                 3 - Enable & Start service on this node

                [E] - Exit FAILSAFE configuration

Enter configuration option:

For more details about failSAFE IP, refer to the HP TCP/IP Services for OpenVMS Management manual.

3.5 Using TCPIP$CONFIG Option Commands to Bypass TCPIP$CONFIG Menus

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, using the following format:


    @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 services.
    CLIENT Configures all client services 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 servers 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 services for the entire cluster:


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

    Note

    The procedure implements two levels of enabling and disabling: clusterwide and node specific (except for SMTP, which is configured and enabled as node specific only).

3.6 Making Configuration Changes Take Effect

Configuration changes made to TCP/IP Services software do not take effect until you start (or restart) the affected services. You may need to restart TCP/IP Services or simply the individual services affected, as explained in Table 3-3.

Table 3-3 Making Configuration Changes Take Effect
When you change the following services... Do the following to make the changes take effect Comments
Core environment (domain, Internet interface, routing, BIND resolver, time zone) Start or restart the TCP/IP Services software. Do this before you run tests (verification procedures) or customize the environment. Methods to start TCP/IP Services are described in Sections 3.8 and 3.11.
Client, server, or optional services only If you did not make changes to the core environment, you need only start or restart each affected service individually. Do this by choosing the Start service option in the service's configuration menu. Alternatively, you can use each service's startup command procedure.

If you also made changes to core environment services, start TCP/IP Services.

Usage of startup command procedures for individual services is explained in Section 3.11.3.

Note

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

3.7 Stopping TCP/IP Services Using TCPIP$CONFIG

Stop TCP/IP Services on your system by choosing option 5 (Shutdown HP TCP/IP Services for OpenVMS) from the Main Configuration menu, as in the following example:


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: 5

The TCP/IP Services shutdown procedure displays a series of messages similar to the following example (the messages displayed depend on the configuration):



Begin Shutdown...


%TCPIP-I-INFO, TCP/IP Services shutdown beginning at  5-SEP-2004
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$INET_DRIVER 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$RSH shutdown completed
%TCPIP-S-SHUTDONE, TCPIP$SMTP shutdown completed
%TCPIP-S-SHUTDONE, TCPIP$SNMP shutdown completed
%TCPIP-S-SHUTDONE, TCPIP$SSH_CLIENT shutdown completed
%TCPIP-S-SHUTDONE, TCPIP$SSH shutdown completed
%TCPIP-S-SHUTDONE, TCPIP$TELNET shutdown completed
%TCPIP-S-SHUTDONE, TCPIP$TFTP shutdown completed
%TCPIP-S-SHUTDONE, TCPIP$XDM shutdown completed
%TCPIP-I-SERVSTOPPED, BIND service already stopped
%TCPIP-S-SHUTDONE, TCPIP$BIND shutdown completed
%TCPIP-S-SHUTDONE, TCP/IP Kernel shutdown completed
%TCPIP-S-SHUTDONE, TCP/IP Services shutdown completed at  5-SEP-2004
15:26:17.78

Shutdown request completed.

3.8 Starting TCP/IP Services Using TCPIP$CONFIG

After configuring the core environment, start TCP/IP Services on your system by choosing option 6 (Startup HP TCP/IP Services for OpenVMS) from the Main Configuration menu, as in the following example:


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: 6

The TCP/IP Services startup procedure displays a series of messages similar to the following example (the messages displayed depend on the configuration):


Begin Startup...

%TCPIP-I-INFO, TCP/IP Services startup beginning at 5-SEP-2004
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-I-STARTDROUT, starting dynamic routing
%RUN-S-PROC_ID, identification of created process is 00000C4E
%TCPIP-S-STARTDONE, TCP/IP Kernel startup completed
%TCPIP-S-STARTDONE, TCPIP$BIND 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$INET_DRIVER startup completed
%TCPIP-S-STARTDONE, TCPIP$METRIC startup completed
%TCPIP-I-NOMAP, no filesystem mapping information available
%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 000002DC
%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$RSH startup completed
%TCPIP-S-STARTDONE, TCPIP$SMTP startup completed
%TCPIP-S-STARTDONE, TCPIP$SSH startup completed
%TCPIP-S-STARTDONE, TCPIP$SSH_CLIENT startup completed
%TCPIP-S-STARTDONE, TCPIP$TELNET 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-SEP-2004
15:27:50.47
Startup request completed.
Press Return to continue ...

Note

The TCPIP-I-NOMAP message in this example appears only if no file systems are mapped in the TCP/IP configuration database. If you need NFS services, set up mapping to a valid file system, as explained in the HP TCP/IP Services for OpenVMS Management manual. If you do not need NFS services, you can safely ignore this message; you can prevent recurrence of this message during future startups by disabling the NFS server using the TCPIP$CONFIG configuration procedure.


Previous Next Contents Index