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.
To get TCPware up and working, you must perform the following steps:
|
Step |
Task |
Instructions |
|
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 |
TCPware installation involves using HPE'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.
|
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)
TCPware requires at least the following operating system versions:
· OpenVMS Alpha V6.1 and later
· OpenVMS VAX V5.5-2 and later
· OpenVMS Itanium V8.2 and later
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 6.0. 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.
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.
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 Itanium common system disk.
Be careful to install only those components for which you have a license. If you install a product for which you do not have a license, it is still consumes disk space, but you cannot use that product.
The TCPware Release Notes provide important information on the current release. A PDF version of the documentation set is available on the TCPware CD-ROM; both PDF and HTML versions of the documentation are publicly available on the Process Software web site at www.process.com.