| Previous | Contents | Index |
You can verify the configuration by running the installation verification procedure (IVP).
You should run the IVP if any of 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.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 the problem is... | Do the following... |
|---|---|
| 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.) Then shut down and restart TCP/IP Services. |
| Installation kit is defective. | Request a replacement kit. |
| IVP fails because the PAK is missing. | Register a TCP/IP Services for OpenVMS PAK. |
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.
If options debug is listed in the resolv.conf file, the SNMP ivp will fail. Refer to the Release Notes for further information. |
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 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:
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, 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.
Remember that any service name with lowercase characters is interpreted by the startup and shutdown procedures as uppercase unless you enclose the name in quotation marks. If you defined the service using quotation marks to preserve the case, be sure to use quotation marks when you specify the service name with the startup or shutdown command. |
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 |
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.
| Section... | Describes.... | Replaces Guide to IPv6 Section ... |
|---|---|---|
| 4.1 | How to configure your system as an IPv6 host. | 2.5.1 |
| 4.2 | How to configure your system as an IPv6 router. | 2.6.1 |
| 4.3 | How to configure failSAFE IP IPv6 addresses. | N/A |
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.
Before running the TCPIP$IP6_SETUP.COM configuration procedure, IPv4 must already be configured on your system. (The TCPIP$CONFIG.COM configuration procedure configures IPv4.) If you are upgrading TCP/IP Services from a previous release, you must run the TCPIP$IP6_SETUP.COM configuration procedure again. |
The IPv6 configuration procedure requires you to specify:
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:
$ @SYS$MANAGER:TCPIP$IP6_SETUP
|
Configure this system as an IPv6 router? [NO]: |
Configure a 6to4 interface? [NO]:
|
The 6to4 tunnel is: TN1
|
Enter this node's IPv4 address to use when generating your site's
6to4 prefix:
|
Your 6to4 site prefix is: 2002:x:x::/48
|
Enter an address prefix to use on interface
TN1 [2002:x:x::/64]:
|
The high-order 48 bits of the 6to4 address prefix must be the same as your 6to4 site prefix. |
Configure a 6to4 relay router? [NO]:
|
Enter the 6to4 address of a 6to4 relay router
[2002:C058:6301::]:
|
Enable IPv6 on interface ddn? [YES]:
|
Configure an IPv6 over IPv4 automatic tunnel interface? [NO]:
|
The automatic tunnel is: TN0
|
Because of potential IPv4-compatible address routing problems, HP recommends that you avoid using automatic tunnels. |
Enter this node's IPv4 address to use when creating
your automatic tunnel:
|
Create IPv6 over IPv4 configured tunnels? [NO]:
|
Enter the source IPv4 address of tunnel ITn:
|
Enter the destination IPv4 address of tunnel ITn:
|
| Previous | Next | Contents | Index |