|
HP OpenVMS Systems Documentation |
|
Compaq TCP/IP Services for OpenVMS
|
| Previous | Contents | Index |
When you choose either option 1 or option 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 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 5-MAR-2002 16:13:03.02 UDP/IP test ended at 5-MAR-2002 16:13:03.69 UDP/IP transferred successfully in 0 seconds 4198400 bytes TCP/IP test started at 5-MAR-2002 16:13:04.20 TCP/IP test ended at 5-MAR-2002 16:13:41.21 TCP/IP transferred successfully in 37 seconds 4198400 bytes RAW_IP test started at 5-MAR-2002 16:13:41.71 RAW_IP test ended at 5-MAR-2002 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.) 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 Compaq 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: 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.9 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 how to configure each service, refer to the
Compaq TCP/IP Services for OpenVMS Management guide.
3.10 Starting and Stopping TCP/IP Services by Command
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.10.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 other TCP/IP Services components currently running. For information about starting and stopping individual components, see Section 3.10.3.
If necessary, you can start and stop TCP/IP Services manually, as
explained in Section 3.10.2. You can also start and stop user-written
services, as explained in Section 3.10.4.
3.10.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.
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.10.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, see the Compaq TCP/IP Services for OpenVMS Management guide.
3.10.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-name |
For service-name, specify the name of the service as defined using the TCP/IP management command SET SERVICE.
To stop the user-written service, enter the following command:
$ SYS$STARTUP:TCPIP$CUSTOMER_SERVICE_SHUTDOWN service-name |
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 |
This appendix shows a sample installation and configuration of the
TCP/IP Services product on a system on which the product has never been
installed.
A.1 Sample New Installation Procedure
The following example shows a sample installation dialog for the TCP/IP Services. In this example, the installation takes place on a system where the product has not been installed. If TCP/IP Services had been installed previously on the system, the installation dialog would differ slightly (see Chapter 2).
The symbols xx in the following example represent the product's two-digit update version number. |
Choose one or more items from the menu separated by commas: 1
The following product has been selected:
DEC VAXVMS TCPIP V5.3-xx Layered Product
Do you want to continue? [YES] [Return]
Configuration phase starting ...
You will be asked to choose options, if any, for each selected product and for
any products that may be installed to satisfy software dependency requirements.
DEC VAXVMS TCPIP V5.3-xx: Compaq TCP/IP Services for OpenVMS.
Copyright 2002 Compaq Information Technologies Group, L.P
Compaq Computer Corporation
Compaq TCP/IP Services for OpenVMS offers several license options.
Do you want the defaults for all options? [YES] [Return]
Do you want to review the options? [NO] [Return]
Execution phase starting ...
The following product will be installed to destination:
DEC VAXVMS TCPIP V5.3-xx DISK$OVMSVAXSYS:[VMS$COMMON.]
Portion done: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%
%PCSI-I-PRCOUTPUT, output from subprocess follows ...
% TCPIP-W-PCSI_INSTALL
% - Execute SYS$MANAGER:TCPIP$CONFIG.COM to proceed with configuration of
% Compaq TCP/IP Services.
%
Portion done: 100%
The following product has been installed:
DEC VAXVMS TCPIP V5.3-xx Layered Product
DEC VAXVMS TCPIP T5.3-xx: Compaq TCP/IP Services for OpenVMS.
Check the release notes for current status of the product.
|
The following example shows a sample configuration dialog for the TCP/IP Services, in which the following components are configured:
In this example, the configuration takes place on a system where the product has never been configured. If TCP/IP Services had been configured previously on the system, the dialog would differ significantly (see Chapter 3).
TCP/IP Network Configuration Procedure
This procedure helps you define the parameters required
to run Compaq TCP/IP Services for OpenVMS on this system.
Checking TCP/IP Services for OpenVMS configuration database files.
Creating SYS$COMMON:[SYSEXE]TCPIP$SERVICE.DAT
Creating SYS$COMMON:[SYSEXE]TCPIP$HOST.DAT
Creating SYS$COMMON:[SYSEXE]TCPIP$NETWORK.DAT
Creating SYS$COMMON:[SYSEXE]TCPIP$ROUTE.DAT
Creating SYS$COMMON:[SYSEXE]TCPIP$PROXY.DAT
Creating SYS$COMMON:[SYSEXE]TCPIP$CONFIGURATION.DAT
Creating TCPIP$ETC:SYSCONFIGTAB.DAT
Compaq TCP/IP Services for OpenVMS requires a definition for at
least one interface. There are no interfaces defined on this
system.
Please select the Interface option from the Core Environment Menu.
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: 1 [Return]
Compaq TCP/IP Services for OpenVMS Core Environment Configuration Menu
Configuration options:
1 - Domain
2 - Interfaces
3 - Routing
4 - BIND Resolver
5 - Time Zone
A - Configure options 1 - 5
[E] - Exit menu
Enter configuration option: A [Return]
DOMAIN Configuration
Enter Internet domain: budget.acme.com
INTERFACE Configuration
The Ethernet device(s) on your system are: EWA0: * Not Configured *
Start of configuration questions for Internet interface WE0.
WE0 is the Ethernet device ESA0:
WE0 has not been configured
Compaq TCP/IP Services for OpenVMS Interface WE0 Configuration Menu
Configuration options:
1 - Configure interface manually
2 - Let DHCP configure interface
[E] - Exit menu (Do not configure interface WE0)
Enter configuration option: 1 [Return]
Enter fully qualified host name: HEARTS.BUDGET.ACME.COM [Return]
Enter Internet address for hearts: 10.0.2.4 [Return]
Enter Internet network mask for hearts [255.0.1.0]: 255.1.12.1[Return]
Enter broadcast mask for hearts [10.0.2.255]: [Return]
The following parameters will be used to define the
Internet interface WE0:
Host name: hearts.budget.acme.com
Internet address: 10.0.2.4
Network mask: 255.0.0.0
Broadcast mask: 10.0.2.255
* Is the above correct [YES]: [Return]
End of configuration questions for Internet interface WE0
DYNAMIC ROUTING Configuration
Dynamic routing has not been configured.
You may configure dynamic ROUTED or GATED routing.
You cannot enable both at the same time. If you want
to change from one to the other, you must disable the
current routing first, then enable the desired routing.
If you enable dynamic ROUTED routing, this host will use the
Routing Information Protocol (RIP) - Version 1 to listen
for all dynamic routing information coming from other
hosts to update its internal routing tables.
It will also supply its own Internet addresses to
routing requests made from remote hosts.
If you enable dynamic GATED routing, you will be able to
configure this host to use any combination of the following
routing protocols to exchange dynamic routing information
with other hosts on the network:
Routing Information Protocol (RIP) - Version 1 & 2
Router Discovery Protocol (RDISC)
Open Shortest Path First (OSPF)
Exterior Gateway Protocol (EGP)
Border Gateway Protocol (BGP-4)
Static routes
* Do you want to configure dynamic ROUTED or GATED routing [NO]:[Return]
A default route has not been configured.
* Do you want to configure a default route [YES]: [Return]
Enter your Default Gateway host name or address: GATE1.BUDGET.ACME.COM
gate1.budget.acme.com is not in the local host database.
Enter Internet address for gate1.budget.acme.com: 10.0.2.66
BIND RESOLVER Configuration
A BIND resolver has not been configured.
Compaq TCP/IP Services for OpenVMS supports the Berkeley Internet Name
Domain (BIND) resolver. BIND is a network service that enables clients
to name resources or objects and share information with other objects
on the network.
Before configuring your system as a BIND resolver, you should
first be sure that there is at least one system on the network
configured as either a BIND primary or secondary server for
this domain.
You can specify a BIND server by its address or name;
however, if specified by name, an entry for it must
exist in the TCPIP$HOST database.
You will be asked one question for each server.
Press Return at the prompt to terminate the list.
Enter your BIND server name: NUMB9.BUDGET.ACME.COM [Return]
numb9.budget.acme.com is not in the local host database.
Enter Internet address for numb9.budget.acme.com: 10.0.2.11
Enter your BIND server name: [Return]
Creating file TCPIP$ETC:IPNODES.DAT
Creating file TCPIP$ETC:SERVICES.DAT
TCPIP uses timezone information provided by the OpenVMS Operating
System. No additonal timezone configuration is needed for TCPIP
when the operating system is configured correctly.
This section verifies the current OpenVMS timezone configuration.
A warning message (TCPIP-W-) indicates that corrective action should
be taken. TCPIP will appear to operate but components may display
either the wrong time or a time inconsistent with other applications.
%TCPIP-I-INFO, Logical name SYS$TIMEZONE_RULE found.
-TCPIP-I-INFO, Software for automatic Summer/Winter time (TDF) change
-TCPIP-I-INFO, is present.
-TCPIP-I-INFO, Further action to ensure TDF change is not necessary.
%TCPIP-I-NORMAL, timezone information verified
Press Return to continue ... [Return]
Compaq TCP/IP Services for OpenVMS Core Environment Configuration Menu
Configuration options:
1 - Domain
2 - Interfaces
3 - Routing
4 - BIND Resolver
5 - Time Zone
A - Configure options 1 - 5
[E] - Exit menu
Enter configuration option: [Return]
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: 2 [Return]
Compaq TCP/IP Services for OpenVMS Client Components Configuration Menu
Configuration options:
1 - FTP Disabled Stopped
2 - NFS Client Disabled Stopped
3 - REXEC and RSH Disabled Stopped
4 - RLOGIN Disabled Stopped
5 - SMTP Disabled Stopped
6 - TELNET Disabled Stopped
7 - DHCP Disabled Stopped
8 - Telnetsym Disabled Stopped
A - Configure options 1 - 8
[E] - Exit menu
Enter configuration option: 6 [Return]
TELNET Configuration
Service is not defined in the TCPIP$SERVICE database.
Service is not enabled.
Service is stopped.
TELNET configuration options:
1 - Enable service on this node
[E] - Exit TELNET configuration
Enter configuration option: 1 [Return]
Creating TELNET Service Entry
Compaq TCP/IP Services for OpenVMS Client Components Configuration Menu
Configuration options:
1 - FTP Disabled Stopped
2 - NFS Client Disabled Stopped
3 - REXEC and RSH Disabled Stopped
4 - RLOGIN Disabled Stopped
5 - SMTP Disabled Stopped
6 - TELNET Enabled Stopped
7 - DHCP Disabled Stopped
8 - Telnetsym Disabled Stopped
A - Configure options 1 - 8
[E] - Exit menu
Enter configuration option: [Return]
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: 3 [Return]
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: 5 [Return]
FTP Configuration
Service is defined in the SYSUAF.
Service is not defined in the TCPIP$SERVICE database.
Service is not enabled.
Service is stopped.
FTP configuration options:
1 - Enable service on this node
[E] - Exit FTP configuration
Enter configuration option: 1 [Return]
Creating FTP Service Entry
The FTP CLIENT is enabled.
* Do you want to configure FTP CLIENT [NO]: [Return]
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: [Return]
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 [Return]
Begin Startup...
%TCPIP-I-INFO, TCP/IP Services startup beginning at 5-MAR-2002 13:22:27
.82
%TCPIP-I-INFO, creating UCX compatibility file SYS$COMMON:[SYSEXE]UCX$S
ERVICE.DAT
%TCPIP-I-NORMAL, timezone information verified
%RUN-S-PROC_ID, identification of created process is 00000058
%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$FTP startup completed
%TCPIP-S-STARTDONE, TCPIP$TELNET startup completed
%TCPIP-S-STARTDONE, TCP/IP Services startup completed at 5-MAR-2002 13:
23:00.49
Startup request completed.
Press Return to continue ...
|
| Index | Contents |