## TCPware V5.7 Installation & Configuration Guide

- Introduction
- Steps to Get TCPware Up and Running
- Prepare for Installation
  - Hardware Requirements
  - Software Requirements
  - Disk Space and Global Pages
- General Requirements
  - Where to Install TCPware
  - Which TCPware Components to Install
- Obtain IP Addresses for Your Network Devices
  - Using Private Addresses
- Release Notes and Online Documentation

Chapter 1

Before You Begin

# Introduction

This chapter introduces you to and prepares you for TCPware product installation, configuration, startup, and testing. It is for the OpenVMS system manager or technician responsible for product installation and configuration.

# Steps to Get TCPware Up and Running

To get TCPware up and working, you must perform the following steps:

Table 1-1 Getting TCPware Up and Running (Continued)

1 | Install the software (see the following section to prepare for installation). | See Chapter 2, Installing TCPware
2 | Configure the TCP/IP core environment. | See Chapter 3, Configuring the TCP/IP Core Environment
3 | Configure the individual TCP/IP components. | See Chapter 4, Configuring the TCP/IP Services
4 | Start and test the software. | See Chapter 5, Starting and Testing TCPware

# Prepare for Installation

TCPware installation involves using HP's VMSINSTAL procedure. Preparing for installation involves:

• Understanding the hardware and software requirements

• Determining if you have sufficient disk space and global pages for the installation

• Determining where to install the software

• Deciding which TCPware products to install

Note! You must shut down all other TCP/IP products previously running on the system without executing any of the other products' startup files, and reboot the system.

## Hardware Requirements

TCPware requires one or more of the following devices:

• HP Ethernet, FDDI, Token Ring (except DEQRA), LAN Emulation over Asynchronous Transfer Mode (ATM), or Classical IP over ATM controller

• IP-over-X.25 controller; all HP interfaces supported by VAX PSI (for VAX)

• HP controller for VAX WAN Device Drivers

• Network Systems HYPERchannel controller (for VAX)

• Proteon proNET-10/80 controller (VAX), or proNET-4/16 EISA NIC controller (Alpha)

## Software Requirements

TCPware requires at least the following operating system versions:

• OpenVMS Alpha V6.1 and later

• OpenVMS VAX V5.5-2 and later

• Open VMS I64 V8.2 and later

## Disk Space and Global Pages

The destination device for your TCPware software must have enough disk space so that you can run the software. The disk space requirements are documented in the TCPware Release notes.

You should also have at least 50,000 free global pages (GBLPAGES) on your system before installing TCPware 5.7. Use SHOW GBLPAGES in the SYSGEN utility to determine the parameter value and change it using SET GBLPAGES if necessary.

Insufficient GBLPAGES can abort the installation and leave your system command tables disconnected. The only way to recover is through a system reboot.

# General Requirements

Check at this point that you:

• Have OPER, SYSPRV, or BYPASS privileges

• Can log in to the system manager's account

• Are the only user logged in (recommended)

• Backed up your system disk on a known, good, current, full backup (recommended)

• Need to reinstall TCPware after performing a major VMS upgrade

• If TCPware is currently running, shut it down. This is mandatory.

## Where to Install TCPware

Install TCPware in a location depending on the following:

• Generally, on your system disk, but you can install TCPware anywhere, just answer the question when it appears. This is also where you would keep your "common" files. Node-specific files should always be on your system disk.

• If the machine is in a single node cluster, on a common disk.

• If the machine is in a mixed node cluster, once on the Alpha system disk (or disks) , once on the VAX common system disk, and once on the I64 common system disk.

## Which TCPware Components to Install

Be careful to install only those components for which you have a license. If you answer YES during the VMSINSTAL procedure for a product for which you do not have a license, it is still installed and consumes disk space, but you cannot use that product.

# Obtain IP Addresses for Your Network Devices

Each of your network devices should be assigned a unique IP address. You can apply for these IP addresses by sending mail to:

Network Solutions
www.networksolutions.com
ATTN: InterNIC Registration Services
505 Huntmar Park Drive
Herndon, VA 22070

You can also contact Network Solutions by phone at 1-703-742-4777 between 7:00 A.M. and 7:00 P.M. ET, or by email at HOSTMASTER@RS.INTERNIC.NET. The network address of the Registration Services domain root server is 198.41.0.4.

## Using Private Addresses

The Internet Assigned Numbers Authority (IANA) also reserves a range of IP addresses for hosts that use TCP/IP but do not need network layer connectivity outside their enterprise. The reserved address ranges for these "private" networks are listed in Table 1-2.

Table 1-2 Private Network Addresses (Continued)

Class | Has the reserved address range | For network (range)
A | 10.0.0.0 10.255.255.255 | 10
B | 172.16.0.0 172.31.255.255 | 172.16172.31
C | 192.168.0.0 192.168.255.255 | 192.168

You can use these host numbers without coordinating them with IANA or an Internet registry. However, the addresses must be unique to your enterprise. If you ever want to connect the host directly to the Internet without using an application layer gateway, you must obtain another "global" address for it from a registry.

# Release Notes and Online Documentation

The TCPware for OpenVMS Release Notes provide important information on the current release. TCPware also provides PostScript versions of its full documentation on CD-ROM.

• If you are installing from CD-ROM, you can access the Release Notes and the full TCPware documentation as PostScript files using a viewing facility such as the CDA Viewer. View the PostScript files directly or copy them. They are in the [DOCUMENTATION] directory. The Release Notes are in the first file listed, TCPWARE057.RELEASE_NOTES. The documentation encompasses the eight remaining files.

• If you are installing from disk, you can read or print the Release Notes as a text file, which you can obtain in one of three ways:

– By performing a partial installation

– During the full installation

– After the installation

To perform a partial installation (see Example 1-1):

1 Invoke VMSINSTAL at the system prompt:

$ @SYS$UPDATE:VMSINSTAL TCPWARE 057 d evice OPTIONS N

The device is the mount location of the distribution volumes.

2 Press Return at the prompt

Are you satisfied with the backup of your system disk [YES]?.

3 Select the option by number as to whether you want to display or print the Release Notes, or both.

4 If you requested a printout, enter the queue name for the printer. The default is SYS$PRINT.

5 Press Return at the prompt

Do you want to continue the installation [NO]?:.

(Note that if you enter YES at the prompt, you proceed with the full installation.)

6 You see the message

Product's release notes have been moved to SYS$HELP.

7 If you want to read or print the Release Notes after you exit the installation, access the TCPWARE057.RELEASE_NOTES file in the SYS$HELP directory, as in:

$ TYPE SYS$HELP:TCPWARE 057.RELEASE_NOTES

Note! For this command to work as desired, do not redefine the SYS$HELP directory logical.

Example 1-1 Performing a Partial Installation to Obtain the Release Notes

$ @SYS$UPDATE:VMSINSTAL TCPWARE05 7 M UA0: OPTIONS N [1]

OpenVMS AXP Software Product Installation Procedure V7.1
It is 1-MAY-2005 at 11:01.
Enter a question mark (?) at any time for help.
* Are you satisfied with the backup of your system disk [YES]? Return [2]
The following products will be processed:
TCPWARE V5.7
Beginning installation of TCPWARE V5.7 at 11:01
%VMSINSTAL-I-RESTORE, Restoring product save set A ...
Release notes included with this kit are always copied to SYS$HELP.
Additional Release Notes Options:
1. Display release notes
2. Print release notes
3. Both 1 and 2
4. None of the above
* Select option [2]: Return [3]

* Queue name [SYS$PRINT]: Return [4]
Job TCPWARE057 (queue SYS$PRINT, entry 1) started on SYS$PRINT

* Do you want to continue the installation [NO]? Return [5]
%VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP.
VMSINSTAL procedure done at 11:02

.
.
.
$ TYPE SYS$HELP:TCPWARE 057.RELEASE_NOTES [6]