HP OpenVMS Systems Documentation

HP TCP/IP Services for OpenVMS
Installation and 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.9.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:

HP 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.9.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

When you choose either option 1 or option A from the TCPIP$CONFIG Test menu, or if you run the TCPIP$IVP command procedure at the command line, the IVP tests the basic TCP/IP Services software configuration, as in the following example. Here, the test completes successfully:

Enter test option: 1 [Return]
Begin IVP...


%%% TCPIP IVP: started %%%

UDP/IP test started at 5-SEP-2004 16:13:03.62
UDP/IP test ended at 5-SEP-2004 16:13:03.69
UDP/IP transferred successfully in 0 seconds 4198400 bytes

TCP/IP test started at 5-SEP-2004 16:13:04.20
TCP/IP test ended at 5-SEP-2004 16:13:04:28
TCP/IP transferred successfully in 0 seconds 4198400 bytes

RAW_IP test started at 5-SEP-2004 16:13:41.71
RAW_IP test ended at 5-SEP-2004 16:13:41.72
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-4 lists some common problems that cause IVP error messages. If the recommended action does not correct the problem, contact your HP support representative.

If you choose either option 2 or option 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: 2 (disabled)
Setting snmpEnableAuthenTraps to: 1 (enabled)
 Retrieved snmpEnableAuthenTraps: 1 (enabled)
(Retrieved value matches SET value.)
 Restoring snmpEnableAuthenTraps: 2 (disabled)

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

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:

• Populating databases (for example, for BIND and DHCP)
• Setting up user accounts
• Setting up communication and NFS proxies
• Defining print queues
• Setting up, exporting, and maintaining file systems
• Tuning the system for optimum performance

Many of the services require additional configuration or optimization. For more information about how to configure each service, refer to the HP TCP/IP Services for OpenVMS Management manual.

3.11 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.11.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 services without affecting other TCP/IP Services components currently running. For information about starting and stopping individual services, see Section 3.11.3.

If necessary, you can start and stop TCP/IP Services manually, as explained in Section 3.11.2. You can also start and stop user-written services, as explained in Section 3.11.4.

3.11.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 to remove the exclamation point (!) from the beginning of the following line:

$!$ @SYS$STARTUP:TCPIP$STARTUP.COM

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.

If you want 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

For information about protections, refer to the OpenVMS documentation.

3.11.2 Starting and Stopping TCP/IP Services Manually

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:

• SYS$STARTUP:TCPIP$service_STARTUP.COM allows you to start the service service.
• SYS$STARTUP:TCPIP$service_SHUTDOWN.COM allows you to shut down the service service.

To preserve site-specific parameter settings and commands, create the following files. These files are not overwritten when you reinstall TCP/IP Services:

• SYS$STARTUP:TCPIP$service_SYSTARTUP.COM can be used as a repository for site-specific definitions and parameters to be invoked when service is started.
• SYS$STARTUP:TCPIP$service_SYSHUTDOWN.COM can be used as a repository for site-specific definitions and parameters to be invoked when service is shut down.

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

3.11.4 Starting and Stopping User-Written Services

TCP/IP Services supplies command procedures for starting and stopping user-written services. To start a user-written service, enter the following command:

$ SYS$STARTUP:TCPIP$CUSTOMER_SERVICE_STARTUP service

To stop the user-written service, enter the following command:

$ SYS$STARTUP:TCPIP$CUSTOMER_SERVICE_SHUTDOWN service

In either command, specify the name of the service as defined using the TCP/IP management command SET SERVICE.

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:

1. Set up security on the remote host.
2. Add the remote client to the local hosts database.
3. Add to SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COM the following line:

   $ DECW$SERVER_TRANSPORTS == "DECNET,LOCAL,TCPIP"

4. Set the display for the applications to the remote host:

   $ SET DISPLAY/CREATE/NODE=remote-host/TRANSPORT=TCPIP

After configuring TCP/IP Services for OpenVMS with the TCPIP$CONFIG.COM command procedure, you can configure your system to communicate in an IPv6 network environment by performing the tasks described in this chapter.

Starting with Version 5.5, TCP/IP Services introduced many significant changes and improvements to the IPv6 configuration procedure (TCPIP$IP6_SETUP.COM). For instructions on configuring your node as an IPv6 host or router, use the documentation in this chapter rather than that provided in the HP TCP/IP Services for OpenVMS Guide to IPv6.

The following table describes each section in this chapter and, where relevant, indicates the section of the Guide to IPv6 that it replaces. The section on configuring failSAFE IP IPv6 addresses is newly documented with this release of TCP/IP Services for OpenVMS. For information about IPv6 concepts and processes, DNS domain name and address registration, and so forth, continue to refer to Chapter 2 of the Guide to IPv6.

You can configure your node as either an IPv6 host or IPv6 router. You make this choice while running the IPv6 configuration procedure (TCPIP$IP6_SETUP.COM). After you run this configuration procedure and restart TCP/IP Services, IPv6 processes associated with your choices are started on your system.

The IPv6 configuration procedure requires you to specify:

• Whether the system is to be configured as an IPv6 host or an IPv6 router.
• Whether the system needs a 6to4 interface (required for communicating between IPv4-only networks and IPv6 sites). If so, you must specify the system's IPv4 address, the 6to4 tunnel address prefix, whether the system will support a 6to4 relay router and, if applicable, the address of a relay router.
• You must specify the interface names of interfaces that will be enabled for IPv6.
• Whether to configure an automatic tunnel. If so, you must also specify the IPv4 address of the tunnel's endpoint.
• You must specify whether the system requires IPv6-over-IPv4 tunnels. For each tunnel, you need to supply the tunnel's source IPv4 address, the tunnel's destination IPv4 address, and the address prefix for the IPv6-over-IPv4 tunnel. You can create multiple IPv6-over-IPv4 tunnels.
• Whether the system requires IPv6-over-IPv6 tunnels. For each tunnel, you must supply the tunnel's source IPv6 address, the tunnel's destination IPv6 address, and the the address prefix for the IPv6-over-IPv6 tunnel. You can create multiple IPv6-over-IPv6 tunnels.
• Whether the system requires manual IPv6 routes. For each route, you must supply the address prefix of the destination IPv6 network, the interface to use to send traffic for the route, and the link-local IPv6 address of the first router in the path or the IPv4-compatible IPv6 address of the automatic tunnel to use. You can create multiple manual IPv6 routes.
• For an IPv6 router, you also must specify:
  • Whether to enable the RIPng protocol on each interface.
  • Whether to advertise an IPv6 address prefix on each interface and, if so, the IPv6 address prefix.
  • For each tunnel you create, whether to enable the RIPng protocol on the tunnel, whether to advertise an IPv6 address prefix on the tunnel interface, and if so, the IPv6 address prefix.
  • For each manual route you create, the interface to use to forward traffic to the remote IPv6 network.

After you use the TCPIP$IP6_SETUP.COM configuration procedure to configure your system as an IPv6 host or router, you can optionally configure your system as a BIND server (see the HP TCP/IP Services for OpenVMS Guide to IPv6). In addition, you can configure failSAFE IP IPv6 addresses, as explained in Section 4.3.

Once you configure IPv6 using the TCPIP$IP6_SETUP.COM configuration procedure, you must enable IPv6 on your system by shutting down and restarting TCP/IP Services.

You can make other changes to your IPv6 configuration later. Chapter 4 of the HP TCP/IP Services for OpenVMS Guide to IPv6 describes how to make further changes.

4.1 Configuring an IPv6 Host

To configure your system as an IPv6 host, do the following:

1. Invoke the TCPIP$IP6_SETUP.COM configuration procedure by entering the following command:

   $ @SYS$MANAGER:TCPIP$IP6_SETUP

   
   The procedure displays information about the IPv6 network configuration procedure and tells you that you can configure the system as either an IPv6 host or an IPv6 router.
2. Choose to configure the system as an IPv6 host by taking the default to the following prompt (press Enter or enter NO):

   Configure this system as an IPv6 router? [NO]:

3. At the following prompt, indicate whether you want to configure a 6to4 interface:

   Configure a 6to4 interface? [NO]:

   
   A 6to4 interface is needed if this host is connected to an IPv4-only network and needs to communicate with other 6to4 or native IPv6 sites. If this system is a host within a 6to4 site, do not create a 6to4 interface; a 6to4 address is automatically configured on this system using standard IPv6 mechanisms.
   If you do not want to configure a 6to4 interface, press Enter. The configuration procedure continues at step 8.
   If you want to configure a 6to4 interface, enter YES. The configuration procedure then displays the 6to4 tunnel interface:

   The 6to4 tunnel is: TN1

   
   You are prompted to enter information about the interface in subsequent steps.
4. Enter this host's IPv4 address:

   Enter this node's IPv4 address to use when generating your site's 6to4 prefix:

   
   Enter the IPv4 address in dotted-decimal format (d.d.d.d). The configuration procedure automatically generates a 6to4 site prefix based on the IPv4 address entered, and displays the prefix as in the following example:

   Your 6to4 site prefix is: 2002:x:x::/48

5. Enter the address prefix for the 6to4 tunnel in response to the following prompt:

   Enter an address prefix to use on interface TN1 [2002:x:x::/64]:

   
   To accept the IPv6 address prefix generated in step 4, take the default.

   Note The high-order 48 bits of the 6to4 address prefix must be the same as your 6to4 site prefix.

6. Indicate whether you want to configure a 6to4 relay router:

   Configure a 6to4 relay router? [NO]:

   
   A relay router is needed to connect your system to native IPv6 sites. If you do not configure a relay router, your system can connect to other 6to4 sites but not to native IPv6 sites.
   If you do not want to configure a 6to4 relay router, press Enter. The configuration procedure continues at step 8.
   If you want to configure a 6to4 relay router, enter YES.
7. Specify the address of a relay router:

   Enter the 6to4 address of a 6to4 relay router [2002:C058:6301::]:

   
   The address of the default relay router is displayed. To use the default, press Enter. Otherwise, enter the 6to4 unicast address of a 6to4 relay router.
8. For each interface on your system, the configuration procedure asks whether you want to enable IPv6 on that interface, as in the following example, where ddn is the interface name (such as WE0):

   Enable IPv6 on interface ddn? [YES]:

   
   If you want to enable IPv6 on this interface, press Enter; if you do not, enter NO.
   If your system has multiple interfaces, the procedure repeats this question for each interface.
9. Indicate whether you want to configure an automatic tunnel:

   Configure an IPv6 over IPv4 automatic tunnel interface? [NO]:

   
   If you do not want to configure an automatic tunnel, press Enter; the procedure continues at step 11. If you want to configure an automatic tunnel, enter YES; the procedure displays the automatic tunnel interface as in the following example. In step 10, the procedure prompts you for the tunnel's address.

   The automatic tunnel is: TN0

   Note Because of potential IPv4-compatible address routing problems, HP recommends that you avoid using automatic tunnels.

10. Enter the IPv4 address to use when constructing the automatic tunnel's endpoint:

    Enter this node's IPv4 address to use when creating your automatic tunnel:

    
    Enter the IPv4 address in dotted-decimal format (d.d.d.d).
11. The configuration procedure asks whether you want to create an IPv6-over-IPv4 configured tunnel:

    Create IPv6 over IPv4 configured tunnels? [NO]:

    
    If you want to create an IPv6-over-IPv4 configured tunnel, enter YES. You are prompted for information about this tunnel in subsequent steps.
    If you do not want to create an IPv6-over-IPv4 configured tunnel, press Enter; the procedure continues at step 16.
12. Enter the tunnel's source IPv4 address in response to the following prompt:

    Enter the source IPv4 address of tunnel ITn:

    
    Enter the tunnel's source IPv4 address in the dotted-decimal format (d.d.d.d).
13. Enter the tunnel's destination IPv4 address in response to the following prompt:

    Enter the destination IPv4 address of tunnel ITn:

    
    Enter the tunnel's destination IPv4 address in dotted-decimal format d.d.d.d. The tunnel's destination address must differ from the source address entered in step 12.
14. Enter an address prefix to use on the tunnel interface:

    ---

    Previous

    Next

    Contents

    Index