| Previous | Contents | Index |
If you are using PATHWORKS Internet Protocol (PWIP) on an OpenVMS VAX system, you should increase the number of interrupt stack pages (INTSTKPAGES) to 10 or more to help eliminate system startup warnings and crashes. For information about PATHWORKS, see the PATHWORKS documentation.
To increase the number of interrupt stack pages, add a statement to the
MODPARAMS.DAT file that increases the value of the INTSTKPAGES system
parameter.
1.2.8 Assigning a User Identification Code
An OpenVMS user or group of users is identified by a unique, assigned user identification code (UIC) in the format [group,member], where group and member are numeric or alphanumeric characters. For example, a UIC can be either [306,210], [GROUP1, JONES], or simply JONES. The UIC is linked to a system-defined rights database that determines user and group privileges.
The TCPIP$CONFIG configuration procedure uses a group UIC to create accounts for components. If a user-specified UIC is not in place from a pervious configuration, the octal number 3655 (the default UIC group number for service accounts) is used. If this is an initial product configuration but the procedure detects that number 3655 is in use, you are prompted for a new UIC group number when you run TCPIP$CONFIG.
Before you assign a new group UIC, check that the number you chose is not already in use by entering the following commands:
$ RUN SYS$SYSTEM:AUTHORIZE UAF> SHOW /BRIEF [your_group_number,*] UAF> SHOW /IDENTIFIER /VALUE=UIC:[your_group_number,*] |
To specify a new UIC group number, assign the value TRUE to the logical
name TCPIP$ASK_GROUP_UIC. When you configure TCP/IP Services,
TCPIP$CONFIG prompts you for the group UIC.
1.3 Assembling Configuration Information
Use the worksheet in Table 1-2 to assemble configuration information.
If you are configuring TCP/IP Services on the system for the first time, the TCPIP$CONFIG procedure prompts you for the information listed in Table 1-2. If you are reconfiguring after a product upgrade, the procedure uses the previous configuration information as the default for the new configuration.
For information to help you answer the questions on the configuration worksheet, see appropriate chapters in the DIGITAL TCP/IP Services for OpenVMS Management guide.
| Question | Answer |
|---|---|
| What is the system's host name (for example, MYNODE)? | |
| What is the system's Internet domain name (for example, widgets.com)? | |
What are the system's addresses and masks?
|
|
| What is the system's network interface (for example, SE0)? | |
| What is the group UIC for TCP/IP Services (see Section 1.2.8)? For example, [GROUP1,JONES]. | |
Do you want to grant nonprivileged users world READ access to the NFS
proxy database (TCPIP$PROXY.DAT)?
|
|
Do you plan to enable SNMP? If yes:
|
|
Which type of routing is appropriate for the network?
|
|
Do you plan to enable the BIND resolver? If yes:
|
|
This chapter explains how to install the DIGITAL TCP/IP Services for OpenVMS software as a layered product application using the POLYCENTER Software Installation utility. The instructions are appropriate for an initial installation or an upgrade.
For information about how to install the product directly from the OpenVMS Alpha CD-ROM menu, refer to the Upgrade and Installation Manual for OpenVMS Alpha.
For information about the POLYCENTER Software Installation utility,
refer to the OpenVMS System Manager's Manual: Essentials.
2.1 Installation Procedure
When you have completed the recommended preinstallation tasks outlined in Chapter 1 and have read the release notes ( Section 1.2.2), you are ready to upgrade or install TCP/IP Services.
During a product upgrade, existing configuration files are preserved in case you want to use them when you configure this version of the software.
To install the TCP/IP Services software on an OpenVMS VAX or Alpha system, proceed as follows:
$ @SYS$MANAGER:UCX$SHUTDOWN |
$ SET HOST 0/LOG=file-name |
$ PRODUCT INSTALL TCPIP /SOURCE=device-name |
To stop the installation at any time, press Ctrl/Y. The installation procedure deletes any files that were created, then exits. |
| Example 2-1 TCP/IP Services Installation: Sample POLYCENTER Software Installation Utility Procedure |
|---|
The following product has been selected:
DEC AXPVMS TCPIP V5.0 Layered Product
(1)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 AXPVMS TCPIP V5.0: DIGITAL TCP/IP Services for OpenVMS.
(c) Compaq Computer Corporation 1999. All rights reserved.
Compaq Computer Corporation
DIGITAL TCP/IP Services for OpenVMS offers several license options.
(2)Do you want the defaults for all options? [YES] [Return]
(3)Do you want to review the options? [NO] YES [Return]
DEC AXPVMS TCPIP V5.0: DIGITAL TCP/IP Services for OpenVMS.
Applications: YES
(4)Are you satisfied with these options? [YES] [Return]
Execution phase starting ...
The following product will be installed:
DEC AXPVMS TCPIP V5.0 Layered Product
Portion done: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%
Portion done: 100%
The following product has been installed:
DEC AXPVMS TCPIP V5.0 Layered Product
|
$ PRODUCT LIST TCPIP/VERSION=5.0 |
Do not delete any files that remain from the previous version of the product. Many of these files are used by TCPIP$CONFIG for converting your existing configuration to the new configuration (Chapter 3). |
$ @SYS$UPDATE:TCPIP$CLEANUP_HELPLIB |
After you install DIGITAL TCP/IP Services for OpenVMS, you need to enable (configure) the components and characteristics you require for your particular system using the menu-driven TCPIP$CONFIG procedure.
This chapter explains the TCPIP$CONFIG menus, provides sample scripts,
and summarizes additional configuration and setup tasks.
3.1 Recommended Order for Configuring TCP/IP Services
Table 3-1 lists the tasks involved in configuring the TCP/IP Services components and functionality.
| Task | Action | Go to... |
|---|---|---|
| 1 | Assemble system information to prepare for running TCPIP$CONFIG. | Section 1.3 |
| 2 | Run TCPIP$CONFIG and answer prompts to convert existing databases or create new ones. | Section 3.2 |
| 3 | Configure the major components and functionality using TCPIP$CONFIG. | Section 3.2.4 |
| 4 | Configure the optional components using TCPIP$CONFIG, as applicable. | Section 3.2.5 |
| 5 | Start TCP/IP Services. | Section 3.4 |
| 6 | Verify the configuration. | Section 3.5 |
| 7 | Reboot the system, then complete additional configuration tasks, as appropriate. | Section 3.6 |
The TCPIP$CONFIG procedure displays menus from which you do the following:
To get started, enter:
$ @SYS$MANAGER:TCPIP$CONFIG |
If you have a TCP/IP Services configuration in place from a previous version of the product, the procedure begins by converting the existing configuration files to new configuration files unless you respond NO to the prompt Convert the old configuration files [Y].
The following sample script shows the start of the TCPIP$CONFIG procedure and a portion of the conversion of the previous configuration:
TCP/IP Network Configuration Procedure
This procedure helps you define the parameters required
to run DIGITAL TCP/IP Services for OpenVMS on this system.
NOTE:
TCP/IP has been previously configured from an earlier version
of this product. You can avoid a complete reconfiguration of
TCP/IP by allowing this procedure to automatically convert the
old configuration files. If you choose not to do this now, you
will not be asked again. At the end of the conversion you will
be able to further modify your configuration.
Convert the old configuration files [Y]: [Return]
Preparing files for conversion...
UCX$SERVICE.DAT --> TCPIP$SERVICE.DAT
UCX$HOST.DAT --> TCPIP$HOST.DAT
UCX$NETWORK.DAT --> TCPIP$NETWORK.DAT
UCX$ROUTE.DAT --> TCPIP$ROUTE.DAT
UCX$PROXY.DAT --> TCPIP$PROXY.DAT
UCX$CONFIGURATION.DAT --> TCPIP$CONFIGURATION.DAT
UCX$EXPORT.DAT --> TCPIP$EXPORT.DAT
UCX$PRINTCAP.DAT --> TCPIP$PRINTCAP.DAT
No new database files were created.
FTP SERVER Configuration
LPD SERVER Configuration
Service is not defined in the SYSUAF.
Nonprivileged user access is not enabled.
By default, DIGITAL TCP/IP Services for OpenVMS configures
LPD such that nonprivileged users cannot modify queue entries.
Creating TCPIP$AUX identifier with a value of 3655
DIGITAL TCP/IP Services for OpenVMS supports Line Printer Daemon
Protocol (see RFC 1179).
LPD requires the following:
- Name of the local queue
- Name of the remote queue
- Name of the remote host
- Spooling directory for the local queue
To add or delete printers in the TCPIP PRINTCAP database, use the
$RUN SYS$SYSTEM:TCPIP$LPRSETUP command.
.
.
.
|
If you do not have an existing TCP/IP Services configuration in place from a previous version of the product, the procedure begins by creating configuration database files, as shown in the following sample script:
TCP/IP Network Configuration Procedure
This procedure helps you define the parameters required
to run DIGITAL 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
For security purposes, the Proxy Database is created with no
world access. This denies nonprivileged users the use of
commands that access the Proxy Database.
Creating SYS$COMMON:[SYSEXE]TCPIP$PROXY.DAT
* Do you want to grant world read access to nonprivileged users [NO]:
Creating SYS$COMMON:[SYSEXE]TCPIP$CONFIGURATION.DAT
DIGITAL 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.
|
If you want to grant world access to the NFS proxy database, answer YES
at the prompt. If not, press Return.
3.2.3 Understanding the Configuration Menus
After the configuration files are converted or created, the main Configuration menu is displayed:
DIGITAL TCP/IP Services for OpenVMS Configuration Menu
Configuration options:
1 - Core environment
2 - Client components
3 - Server components
4 - Optional components
5 - Shut down DIGITAL TCP/IP Services for OpenVMS
6 - Start up DIGITAL TCP/IP Services for OpenVMS
7 - Run tests
A - Configure options 1 - 3
[E] - Exit configuration procedure
Enter configuration option:
|
The options are as follows:
If you do not have experience with the TCP/IP Services product, you
should use the configuration menus. However, if you have experience
configuring the software and want to bypass the menus, you can add one
or more command parameters when you run TCPIP$CONFIG. For information
about the command parameters, see Section 3.3.
3.2.4 Configuring the Core Environment and the Client and Server Components
From the main Configuration menu, enter option A to configure options 1 through 3.
The script examples in this section show the progression of the procedure when you choose to configure groups of components. Alternatively, you can configure one option at a time. |
The Core environment menu is displayed first. Enter option A to configure options 1 through 5. You are required to configure the Domain, Routing, and Interfaces options; the BIND Resolver and Time Zone are optional.
DIGITAL TCP/IP Services for OpenVMS Core Environment Configuration Menu
Configuration options:
1 - BIND Resolver
2 - Domain
3 - Routing
4 - Interfaces
5 - Time Zone
A - Configure options 1 - 5
[E] - Exit menu
Enter configuration option: A [Return]
|
The following sample script reflects a new TCP/IP Services product installation. The script varies for systems that have an existing configuration in place.
Enter your responses to the menu questions using the information from your configuration planning worksheet ( Section 1.3).
BIND RESOLVER Configuration
A BIND resolver has not been configured.
DIGITAL 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: MAINSV [Return]
MAINSV is not in the local host database.
Enter Internet address for MAINSV: 19.112.139.14 [Return]
You must provide the domain name in order to run
the BIND resolver. This information should be available
from your Internet network administrator.
DOMAIN Configuration
Enter Internet domain: widgets.com [Return]
INTERFACE Configuration
The Ethernet device(s) on your system are: ESA0: * Not Configured. *
Start of configuration questions for Internet interface SE0.
SE0 is the Ethernet device ESA0:
SE0 has not been configured.
* Do you want to configure SE0 [YES]: [Return]
Enter unqualified host name: WIDGTS
Host WIDGTS exists in the database.
Enter Internet address [19.112.139.15]: [Return]
Enter Internet network mask for widgts [225.255.0.0]: [Return]
Enter broadcast mask for widgts [19.225.225.225]: [Return]
The following parameters will be used to define the
Internet Interface SE0:
Host name: widgets.com
Internet address: 19.112.139.15
Network mask: 255.255.0.0
Broadcast mask: 19.225.225.225
* Is the above correct [YES]: [Return]
End of configuration questions for Internet interface SE0.
DYNAMIC ROUTING Configuration
You can configure dynamic ROUTED or GATED routing. However,
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]: YES [Return]
* Do you want to enable GATED routing configuration [NO]: [Return]
ROUTED option
If you enable the 'supply' option of dynamic routing,
this host will supply dynamic routing information to
other hosts on the network whether it is acting as an
internetwork gateway or not.
* Do you want this host to supply its dynamic routing information [NO]: [Return]
TIME ZONE Configuration
TCPIP uses time zone information provided by the OpenVMS Operating
System. No additional time zone configuration is needed for TCPIP
when the operating system is configured correctly.
This section verifies the current OpenVMS time zone 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, time zone information verified
Press Return to continue ...
|
After you configure options 1 through 5, the procedure returns to the Core Environment menu. Enter option E to exit. The Client Components menu is displayed.
Note that the menus in the following sample scripts show each component disabled (default). In fact, the procedure might show some of the components as enabled based on your past configuration or the selections you made from the Core Environment menu.
| Previous | Next | Contents | Index |