TCPware V5.7 Installation & Configuration Guide

Previous PageTOCIndexNext Page

Chapter 6

Starting and Testing TCPware

Introduction

This chapter describes how to start and stop TCPware, and remove TCPware files. It is for the OpenVMS system manager, administrator, or operator responsible for system startup.

Prepare for Startup

Verify the Installation, Configuration, and Registration

Before you start TCPware for the first time, be sure you have:

• Installed your TCPware components.

• Correctly configured your TCPware components.

• Registered TCPware through your Product Authorization Key (PAK).

Running Other Products

If you run IP-over-X.25, DECnet, DECwindows, HYPERchannel, or another vendor's TCP/IP product, there are a few things you need to keep in mind:

If you...

Then you must...

Installed and configured IP-over-X.25 support

Install, configure, and run VAX P.S.I. See Chapter1.

Run DECnet

Start Decnet before starting TCPware. If DECnet and TCPware use the same Ethernet controller, DECnet cannot start if TCPware is already running. (You do not have to run DECnet to use TCPware).

Run DECwindows

Set up the HP windows transport interface. You can use the TCPware DECwindows transport interface only if your system runs VMS Version 5.5-2 or later, or OpenVMS, and if you enabled this feature during network configuration. To set up and use the TCPware DECwindows transport interface, see Chapter 28 in the Management Guide.

Use HYPERchannel support

Start and load the Network Systems Corporation H269 driver (as described in the H269 documentation) before starting TCPware.

System Parameters

You can use the SYSGEN utility in OpenVMS to examine the system parameters described in this section. Edit the SYS$SYSTEM:MODPARAMS.DAT file and use AUTOGEN to change the system parameters. System parameter settings need to be as follows:

• The TCPware shareable Socket Library, SMTP-OpenVMS ONC RPC Run-Time Library and the TCPware DECwindows transport interface require a modest number of global pages and sections for the shareable images they install.

GBLPAGES refers to the global page table entries. GBLSECTIONS refers to the number of global section descriptors. If an insufficient number of GBLPAGES or GBLSECTIONS are free, the shareable images might fail to install. If this happens, increase the number of each.

Table 6-1 lists the minimum free requirements for global pages and sections required after installation but before starting TCPware.

• If you plan to use Serial Line IP (SLIP) lines, make sure you set the maximum buffer size (MAXBUF) and alternate type-ahead (TTY_ALTYPAHD) system parameters properly. Change the following parameters:

– MAXBUF should be at least twice the maximum transmission unit (MTU) of the SLIP line plus 144. The default MTU for SLIP lines is 1006 bytes; therefore, MAXBUF must be at least 2156. Increase MAXBUF if necessary.

MAXBUF is dynamic. If you use SYSGEN to change it, you do not need to reboot the system for the change in value to take effect.

– TTY_ALTYPAHD should be larger than its default value. This prevents characters from being lost. The greater the line speed, the higher you should set this parameter. For most applications, 1024 is appropriate.

TTY_ALTYPAHD is not dynamic. If you use SYSGEN to change this parameter, you must reboot the system for the change to take effect.

Account Privileges

Make sure each TCPware user account has TMPMBX and NETMBX privileges. These are the normal default privileges required to use TCPware. Use the OpenVMS AUTHORIZE utility to grant these privileges to the appropriate users.

Table 6-1 Global Pages and Section: Minimum Requirements (Continued)

Shareable Image

GBLPAGES

GBLSECTIONS

DECW_TRANSPORT_TCPWARE*

8

2

SMTP_MAILSHR

20

2

SMTP_MAILSHRP*

10

2

TCPWARE_RPCLIB_SHR

5

1

TCPWARE_SOCKLIB_SHR

10

2

Automatic Startup Process

To automatically start TCPware each time you boot your system:

Step

Task

Action

1

Add TCPware to your system startup file

The name of the startup file for your system is in Table6-2. Edit the file and add these lines after the ones that start DECnet (note that they are valid only for the default TCPware installation common files location):

$ @SYS$SYSROOT:[TCPWARE]TCPWARE_LOGICALS

$ @TCPWARE:STARTNET

Configuring the TCPware Commands

To configure the TCPware commands:

Step

Task

Action

1

Edit your SYLOGIN.COM file to define all the TCPware commands

Add the following line to the "all accounts" definition section of the system-wide login file, SYS$MANAGER:SYLOGIN.COM:

$ @TCPWARE:TCPWARE_COMMANDS

To prevent any errors in the SYLOGIN.COM file from causing a TCPware module to fail, you might want to include the $ SET NOON line at the beginning of the file to disable error checking.

Note! If you chose to install TCPware common files in a location other than the default, you must redefine SYS$SYSROOT to point to that location.

Table 6-2 System Startup File Name and Location

If your VMS version is...

Your startup file is...

OpenVMS VAX V6.x

SYS$MANAGER:SYSTARTUP_VMS.COM

OpenVMS Alpha

SYS$MANAGER:SYSTARTUP_VMS.COM

VMS V5.x

SYS$MANAGER:SYSTARTUP_V5.COM

Configuration Menu Startup or Shutdown Process

You can start all components or selected components from the configuration menu system. Enter at the DCL prompt:

@TCPWARE:CNFNET MENU

At the menu shown in Example 6-1, enter the number of the service you want to start up: TCP/IP Services (1), the only option.

Figure 6-1 First Menu in the Startup or Shutdown Procedure

TCPware(R) for OpenVMS Configuration Menu

Configuration Options:

1 - Configure TCPware Services

2 - Startup/Restart all TCPware Services
3 - Shutdown all TCPware Services

L - Display the software licensing information (PASSWORD)
E - Exit the configuration procedure (changes will be saved)

Enter configuration option: 1 Return

If you enter 1, another menu appears from which you can select to start or restart the entire service (4), or start or restart a particular component (6). In the latter case, a menu such as in Figure 6-2 appears. The shutdown menus available if you enter 3 at the menu in Example 6-1 are similar except that they are for shutdown purposes.

CAUTION! Do not use the STOP PROCESS/ID command to stop TCPware or any of its components. Use the SHUTNET command as described on the following page.

Figure 6-2 Component Configuration Menu for the TCPware Services

Configuring a Specific TCP/IP Component

Configuration options:

1 - ACCOUNTING Configure the TCP/IP Services accounting facility
2 - ACECLIENT Configure the ACE/Client Service
3 - CNFS Configure the NFS-OpenVMS Client
4 - DHCP Configure the Dynamic Host Configuration Protocol Server
5 - DNIP Configure DECnet over IP tunnels
6 - DNS Configure the Domain Name Server
7 - FTP Configure the FTP-OpenVMS Server
8 - GATED ConfigureConfigure the Gate Daemon
9 - IMAP Configure the Internet Message Access Protocol Server
10 - IPP Configure the Internet Printing Protocol Client
11 - KERBEROS Configure the Kerberos Services
12 - LPS Configure the Line Printer Services
13 - MISC Configure the Miscellaneous Services
14 - NFS Configure the NFS-OpenVMS Server
15 - NTP Configure the Network Time Protocol Daemon
16 - POP3 Configure the Post Office Protocol V3 Server
17 - PWIP Configure the PWIPDRIVER
18 - RCMD Configure the Berkeley R Commands
19 - SMTP Configure the Simple Mail Transfer Protocol Services
20 - SNMP Configure the Simple Network Management Protocol Agents
21 - SSH Configure the SSH-OpenVMS Server
22 - TALK Configure the TALK Server
23 - TELNET Configure the TELNET-OpenVMS Server
24 - TIMED Configure the TIMED Server
25 - XDM Configure the XDM Server

Enter menu option (E to exit):

Figure 6-3

Component Startup Menu for the TCPware Services

Starting a Specific TCP/IP Component

Startup options:

1 - ACCOUNTING Startup the TCP/IP Services accounting facility
2 - ACECLIENT Startup the ACE/Client Service
3 - CNFS Startup the NFS-OpenVMS Client
4 - DHCP Startup the Dynamic Host Configuration Protocol Server
5 - DNIP Startup DECnet over IP tunnels
6 - DNS Startup the Domain Name Server
7 - FTP Startup the FTP-OpenVMS Server
8 - GATED Startup the Gate Daemon
9 - IMAP Startup the Internet Message Access Protocol Server
10 - IPP Startup the Internet Printing Protocol Client
11 - KERBEROS Startup the Kerberos Services
12 - LPS Startup the Line Printer Services
13 - MISC Startup the Miscellaneous Services
14 - NFS Startup the NFS-OpenVMS Server
15 - NTP Startup the Network Time Protocol Daemon
16 - POP3 Startup the Post Office Protocol V3 Server
17 - PWIP Startup the PWIPDRIVER
18 - RCMD Startup the Berkeley R Commands
19 - SMTP Startup the Simple Mail Transfer Protocol Services
20 - SNMP Startup the Simple Network Management Protocol Agents
21 - SSH Startup the SSH-OpenVMS Server
22 - TALK Startup the TALK Server
23 - TELNET Startup the TELNET-OpenVMS Server
24 - TIMED Startup the TIMED Server
25 - XDM Startup the XDM Server

Enter menu option (E to exit):

Command Startup or Shutdown Process

You can also use the DCL command method to start TCPware or one of its components:

@TCPWARE:STARTNET [component]

STARTNET by itself starts all TCPware. If you specify a component with the command, you start that component only (see Example6-2 for the TCP/IP Services; note that your list of available components may be different). Start the TCP/IP Services components using @TCPWARE:STARTNET TCPWARE.

Upon startup, TCPware checks for the logicals TCP, UDP, IP, INET, RMT, RCD, BG, and QX. If any of these logicals have been previously defined on your system, the following warning is generated:

%TCPWARE-W-BADLOGICAL

Redefine the conflicting logicals and restart TCPware.

If you need to shut down TCPware or any of its components, use the DCL command:

@TCPWARE:SHUTNET [component]

SHUTNET by itself shuts down all TCPware. If you specify a component with the command, you shut down that component only (use one of the component names listed in Example6-2). Shut down the TCP/IP Services components using @TCPWARE:SHUTNET TCPWARE.

Customizing Your Startup

If your network configuration has special requirements, you might need to create the file TCPWARE:TCPWARE_STARTUP.COM and call it from the OpenVMS system startup file. (See comments in the STARTNET.COM file for more details about special requirements.)

To configure special requirements:

1 Copy the TCPWARE:TCPWARE_STARTUP.TEMPLATE template file to the TCPWARE:TCPWARE_STARTUP.COM file.

$ COPY TCPWARE_COMMON:[TCPWARE]TCPWARE_STARTUP.TEMPLATE-
_$ TCPWARE_COMMON:[TCPWARE]TCPWARE_STARTUP.COM

2 Edit the VMS system startup file.

a Delete the following line or pair of lines, whichever the file contains:

$ @SYS$SYSROOT:[TCPIP]STARTNET

$ @SYS$SYSROOT:[TCPWARE]TCPWARE_LOGICALS

$ @TCPWARE:STARTNET

b Add the following line to the VMS system startup file:

$ @TCPWARE_COMMON:[TCPWARE]TCPWARE_STARTUP.COM

3 Edit the TCPWARE_STARTUP.COM file as needed and as described in the rest of this section.

Note! Changes you make to network parameters using Network Control Utility (NETCU) commands are active until TCPware shuts down. Update the TCPWARE_STARTUP.COM file with these commands to make them permanent.

For example, you might want to do the following (see Example 6-4):

Step

Task

Action

1

Override the default TCP maximum segment size or window size

See the description of the START/TCP command /MSS and /MWS qualifiers in the NETCU Command Reference, Chapter 2, NETCU Commands.

If you use TCP over a satellite link with a line speed greater than 384 Kbits, configure TCPware on both sides with a window size greater than 63448 bytes. See the description of the START TCP command for details on using satellite links.

2

Override the default UDP maximum datagram size

See the description of the START/UDP command /MDS qualifier.

3

Enable FORWARDING capability

See the description of the ENABLE FORWARDING command /MDS qualifier. You can also add the ENABLE FORWARDING command to the TCPWARE_STARTUP.COM file.

4

Join multicasting host group addresses

You may have applications that rely on multicasting yet do not want to change the application code to join the specific groups so that they can receive the multicast datagrams. Therefore, you can include ADD MULTICAST_GROUP commands to the TCPWARE_STARTUP.COM file to add the multicast IP addresses.

Example 6-1 Customizing Startup

START/TCP/MWS= value/MSS= value /NOKEEPALIVE [1]

START/UDP/MDS= value [2]

ENABLE FORWARDING [3]

ADD MULTICAST_GROUP 224.0.0.2 /LINE=ISA-0 [4]

Starting User-Written Servers

If you want any user-written servers to start automatically when you start TCPware, edit the SERVERS.COM file. CNFNET creates a template of this file if none existed previously.

To start a user-written server automatically, see Example 6-5 and do the following:

1 Edit the TCPWARE:SERVERS.COM file.

2 Enter the ADD SERVICE command in the file for each server you add.

For example, if you built FINGERD from the sources TCPware provides, you might add the command in Example 6-2 to the end of the SERVERS.COM file.

The various quotas and parameters might be different for your system, or you might chose to take the defaults for most values.

See the description for the ADD SERVICE command in the NETCU Command Reference, Chapter 2, NETCU Commands.

Example 6-2 Configuring User-Written Servers

ADD SERVICE FINGER TCP TCPWARE:FINGERD - [2]
/PROCESS_NAME = FINGERD -
/NOACCOUNTING -
/NOAUTHORIZE -
/INPUT = NLA0: -
/OUTPUT = NLA0: -|
/ERROR = NLA0: -
/UIC = [SYSTEM] -
/AST_LIMIT = 10 -
/BUFFER_LIMIT = 10240 -
/ENQUEUE_LIMIT = 100 -
/EXTENT = 500 -
/FILE_LIMIT = 20 -
/IO_BUFFERED = 6 -
/IO_DIRECT = 6 -
/MAXIMUM_WORKING_SET = 300 -
/PAGE_FILE = 10000 -
/PRIORITY = 4 -
/PRIVILEGES = (NOSAME, SYSPRV, NETMBX, TMPMBX, WORLD) -
/QUEUE_LIMIT = 8 -
/WORKING_SET = 200 -
/SUBPROCESS_LIMIT = 0

Installing and Configuring INGRES/Net

This section describes how to install and configure Ingres Corporation's INGRES/Net product to use TCPware as the TCP/IP network protocol. For INGRES/NET Version 6.4, use TCPware's UCX Compatibility mode, which is the TCP_HP protocol at INGRES/Net startup. For earlier versions, follow these steps:

1 Define the TWG$ETC logical name.

2 Define the ETC logical name to be TWG$ETC:[000000], as described in the INGRES/Net installation procedures.

3 Be sure that the HOSTS. file in the directory referenced by the ETC logical name defined in step 2 (ETC:HOSTS.) defines localhost and all the hostnames you need for INGRES/Net access. You can define localhost as the 127.0.0.1 loopback address.

4 If you plan to use the default symbolic form of the Wollongong TCP/IP listen address (II0), define that logical name. Use the format described in the INGRES/Net installation instructions for specifying the value of a Wollongong TCP/IP listen address.

For example, if your local host's internet address is 128.100.200.50, and you use the default port number for a production installation (21064), define II0 as shown in Example 6-6. Make sure to replace the dots in the internet address with underscores.

5 Install INGRES/Net following the instructions described in the INGRES/Net User's and Administrator's Guide. Follow the directions specified for using Wollongong TCP/IP as a network protocol.

6 For an easier INGRES/Net startup, add the definitions of the TWG$ETC, ETC, and IIO logical names to your system startup file before the INGRES startup commands.

Install and start TCPware for OpenVMS before you install INGRES/Net.

Example 6-3 Installing and Configuring INGRES/Net

$ DEFINE/SYSTEM/EXECUTIVE/TRANSLATION=CONCEALED TWG$ETC- [1]
_$ SYS$SYSDEVICE:[SYS0.SYSCOMMON.TCPWARE]

Use this command line for INGRES/Net Version 6.4

$ DEFINE/SYSTEM/EXECUTIVE ETC TWG$ETC:[000000] [2]

Use this command line for INGRES/Net Version 6.2 or 6.3

$ DEFINE/SYSTEM ETC TWG$ETC:[000000]

$ DEFINE/SYSTEM II0 128_100_200_50:21064 [4]

Installing and Configuring Oracle's SQL*Net

This section describes how to install and configure Oracle's SQL*Net product to support TCPware as the TCP/IP network protocol. You need ORACLE for OpenVMS for VAX Version 6.1.

Note! Install and operate TCPware for OpenVMS before installing SQL*Net.
For Oracle's SQL*Net Version 7.1.5 and later (with Protocol Adapter 2.1.5), just install the product. It is fully compatible with TCPware's TCP/IP driver. You can ignore the configuration steps that follow.

To install and configure SQL*Net versions before 7.1.5 to use TCPware (see Example 6-7):

1 Install the SQL*Net product as described in the Oracle SQL*Net documentation. Make sure you configure it to make use of the Wollongong TCP/IP driver.

2 Load and build SQL*Net. Do not edit the HOSTS. and SERVICES. files as described in the Oracle documentation. Instead:

a Create a [NETDIST.ETC] directory on the system disk, as shown.

b Define the TWG$TCP system logical to be the name of the device on which you create the [NETDIST.ETC] directory.

c Edit the TCPWARE:SERVICES. file to add the definition for the orasrv service. For example:

orasrv 1525/tcp

See your Oracle documentation for the exact entry information.

d Make sure the TCPWARE:HOSTS. file defines localhost and all of the hostnames you need for ORACLE access. You can define localhost as the 127.0.0.1 loopback address. SQL*Net does not use the Domain Name Services.

e Copy the SERVICES. and HOSTS. files from the TCPWARE: directory to the TWG$TCP:[NETDIST.ETC] directory. Remember to copy these files each time you update them.

3 Start the SQL*Net TCP server process. See your Oracle documentation.

4 Add the TWG$TCP logical name to either the system or ORACLE startup command procedure to make the changes permanent. Note that device is the name of the device on which you create the [NETDIST.ETC] directory.

To undo SQL*Net support of TCPware:

1 Delete the TWG$TCP:[NETDIST.ETC] files and directory.

2 Remove the TWG$TCP system logical definition from the running system. Enter:

$ DEASSIGN/SYSTEM TWG$TCP

3 Remove the TWG$TCP system logical definition from any startup command procedures to which you added it.

Example 6-4 Installing and Configuring Oracle's SQL*Net

$ CREATE/DIRECTORY SYS$SYSDEVICE:[NETDIST.ETC]/PROT=(WO:RE) [2a]

$ DEFINE/SYSTEM/NOLOG TWG$TCP SYS$SYSDEVICE: [2b]

$ EDIT TCPWARE:SERVICES.orasrv 1525/tcp Ctrl/Z [2c]

$ COPY TCPWARE:SERVICES.,HOSTS.TWG$TCP:[NETDIST.ETC]/PROT=(WO:RE) [2e]

$ DEFINE/SYSTEM/NOLOG TWG$TCP device [4]

Configuring HP's TEAMLINKS and AIDA Products

TCPware also supports HP's TEAMLINKS and AIDA products. To configure the TEAMLINKS and AIDA products for use with TCPware:

1 For TEAMLINKS, use the NETCU ADD SERVICE command to add two services to the TCPWARE:SERVICES. file, for the Teamlinks Connection and the Mailworks process, assigning ports as in Example 6-7.

2 For AIDA, use the NETCU ADD SERVICE command to add two services to the TCPWARE:SERVICES. file for the File Cabinet Server and the AIDA Server, assigning ports as in Example 6-7.

Port numbers must be in the range 1024 to 65535. This is valid for ALL-IN-1 IOS Teamlinks Connection Version 2.1 for OpenVMS VAX (it may not apply to earlier or future versions).

For more information, see the ALL-IN-1 IOS Teamlinks Connection Installation and Management Guide, Section 6.2.

Example 6-5 Installing and Configuring TEAMLINKS

tlinks 6161/tcp # teamlinks connect [1]
muas 8484/tcp # mailworks process

Example 6-6 Installing and Configuring AIDA

oa$fcs 7373/tcp # teamlinks connect [2]
oa$aida 7300/tcp # mailworks process

Removing TCPware Components

You can remove any or all TCPware components using the DCL command:

• To remove a single component:

@TCPWARE:TCPWARE_REMOVE component

• To remove all the TCPware components:

@TCPWARE:TCPWARE_REMOVE TCPware

CAUTION! This command deletes all relevant files in all TCPware-specific directories and the TCPWARE directory.

Register Your Product Authorization Key (PAK)

Registering this PAK allows you to start and run TCPware for all the products you install.

To register your PAK, do the following (see Example 6-7):

1 Copy down the string of digits representing your Hardware ID.This is your Ethernet controller's hardware ID.

2 With your Hardware ID number and product names and version information available, contact Process Software's Licensing Desk.

3 The Licensing Desk will ask you for the required information and provide you with the various values you have to enter during the LMF procedure. Be sure to enter these values exactly as you see them, especially the Authorization Number.

4 Use the OpenVMS License Management Facility (LMF) in one of the two following ways, depending on your preference (Figure 5-9 shows a sample menu and PAK information display):

• SYS$UPDATE:VMSLICENSE command — The menu- and prompt-driven method that takes you through each licensing step in detail. Enter:

@SYS$UPDATE:VMSLICENSE

• LICENSE REGISTER command — The single command method where you can specify licensing information through qualifiers. Enter:

LICENSE REGISTER TCPWARE /qualifier /qualifier ....

See HP's OpenVMS License Management Utility Manual (or A Practical Guide to OpenVMS Software License Management and Tools) for details on the VMSLICENSE or LICENSE REGISTER procedures.

Example 6-7 Registering Your PAK

Sample Hardware ID Information (EXAMPLE ONLY: Do Not Use)

Provide your distributor or Process Software with the following information to obtain Product Authorization Key(s) for this system:

o Hardware ID: "12-34-56". [1]
o The product name and version number for the product(s) you are
installing on this system.

Refer to your product documentation for more information on obtaining Product Authorization Key(s).

Sample VMSLICENSE Command Procedure Menu

VMS License Management Utility Options: [4]

1. REGISTER a Product Authorization Key
2. AMEND an existing Product Authorization Key
3. CANCEL an existing Product Authorization Key
4. LIST the Product Authorization Keys
5. MODIFY an existing Product Authorization Key
6. DISABLE an existing Product Authorization Key
7. DELETE an existing Product Authorization Key
8. COPY an existing Product Authorization Key
9. MOVE an existing Product Authorization Key
10. ENABLE an existing Product Authorization Key
11. SHOW the licenses loaded on this node
12. SHOW the unit requirements for this node

99. EXIT this procedure

Type '?' at any prompt for a description of the information requested.
Press Ctrl/Z at any prompt to exit this procedure.

Enter one of the above choices [1]

Sample VMS PAK Information

ISSUER: PSC
AUTHORIZATION NUMBER: 9145685760
PRODUCT NAME: TCPWARE-TCP
PRODUCER: PSC
NUMBER OF UNITS: 200
VERSION:
PRODUCT RELEASE DATE:
KEY TERMINATION DATE:
AVAILABILITY TABLE CODE: F
ACTIVITY TABLE CODE:
KEY OPTIONS: NO_SHARE
PRODUCT TOKEN:
HARDWARE I.D.:
CHECKSUM: 4-ABCD-EFGH-IJKL-MNOP

Test TCPware

Use the following steps to test your TCPware connections after a startup:

1 Verify that the databases you need are properly updated by the startup. Among these are:

• TCPWARE:HOSTS.

• TCPWARE:HOSTS.EQUIV

• .RHOSTS

• ROUTING.COM

2 Log out of the system account — TCPware for OpenVMS is ready for general use.

3 Test TCPware — Perform connectivity tests for each TCPware component you installed and configured. For example, use FTP to transfer some files.

If you uncover problems during testing, review the network configuration. If you need to reconfigure a component, stop TCPware first.

Previous PagePage TopTOCIndexNext Page