Chapter 2
Before the Installation


System Requirements

DYNIX/ptx V4.4.10 runs on IBM xSeries 430 systems, IBM NUMA-Q 2000 systems, and CSM-based Symmetry 5000 systems. It is not supported for SSM-based Symmetry 2000 systems.

To run V4.4.10, your system must meet these requirements:


Disk Space Requirements

Root and /usr are now distributed as a single filesystem. The combined root filesystem requires a minimum of 500 MB of disk space.

The default root VTOCs now have a 1-GB partition 0, where the root filesystem is typically installed. ptx/INSTALL can install the new default VTOC on the installation disk.

During the installation procedure, ptx/INSTALL will determine the total disk space needed to install the products you specify. If your system does not have adequate space available, ptx/INSTALL will report the amount of additional space needed. When you have freed the additional space, you can resume the installation.

After resuming, ptx/INSTALL will check the disk space again and will proceed if adequate space is available.


Operational Restrictions

The following restrictions must be followed when running DYNIX/ptx V4.4.10. In these restrictions, local refers to devices connected directly to the PCI/SCSI interface on IBM xSeries 430 and NUMA-Q 2000 systems or to devices connected directly to the HPSE portion of the CSM on CSM-based systems.

All other devices are shareable; they can be shared by nodes running ptx/CLUSTERS. Shareable devices are accessible only in multiuser mode.


Requirements for EMC Disk Subsystems

Each EMC Symmetrix® disk storage subsystem must be running the appropriate EMC microcode version before your NUMA system is upgraded to DYNIX/ptx V4.4.10. Contact either your local EMC service representative or the EMC customer support center to determine your current EMC microcode version and the correct version for systems running DYNIX/ptx V4.4.10. If you contact the support center, be sure to provide the EMC site number. The EMC support center can remotely log into the system and provide the version of the currently loaded microcode.

Currently, DYNIX/ptx supports a maximum of four multiport connections to each EMC disk storage subsystem. This means that there should be no more than four I/O paths to the disks in one EMC disk storage subsystem.


ATTENTION

In V4.4.10, you do not need to set timeouts for EMC devices in the mpt_space.c file.



Back Up System Files and Configuration Information


System Files

Before you begin the installation, we recommend that you perform a complete backup of the root filesystem (and /usr if it is a separate filesystem). At a minimum, back up files that have been modified at your site. Table 2-1 lists some of the files you should consider backing up.

Table 2-1. Files to Back Up

In /etc/

auclass

inittab

passwd

audit_aliases

motd

pass_seed

auevent

named.*

rc2.d/S20bootflags

checklist

net_conf/iftab

rc2.d/S40addswap

devtab

net_conf/netd.inst

rc2.d/S50TCP

dumpdates

net_conf/routetab

rc2.d/S50netservers

exports

net/ticlts/hosts

resolv.conf

fstab

net/ticlts/services

rpc

ftpusers

net/ticots/hosts

rpc.inetd.conf

gettydefs

net/ticots/services

services

group

net/ticotsord/hosts

shadow

hosts

net/ticotsord/services

site_sepc

hosts.equiv

netconfig

syslog.conf

inetd.conf

networks

TIMEZONE

init.d/addswap

nodename

vfstab

init.d/bootflags

In /usr/

admin.ptx/etc/bootflags.data

lib/cron/cron.allow

osi/ftam/config/AETABLE

agent/config/agt/snmpd.cnf

lib/cron/cron.deny

osi/ftam/config/ftam.cfg

lib/aliases

lib/cron/queuedefs

osi/ftam/config/ftam.auth

lib/cron/at.allow

lib/sendmail.cf

spool/cron/crontabs/*

lib/cron/at.deny

In /var/

netls/nodelock

tcp/ifaddrs

tcp/routetab

tcp/hostname

tcp/ifnets

Other Files

lp configuration files

Mail and mail alias files

User files

Kernel configuration files with site-specific changes



ptx/SVM Database

Use the following procedure to back up a ptx/SVM configuration database. You must be root to perform the procedure.

  1. List the disks in each disk group and save the information either into a filesystem that is a not a ptx/SVM volume, or into the root filesystem. For each disk group, issue the following command:

    # vxdisk -g diskgroup list > /xxx/diskgroup.disks

  2. Save the contents of each disk group's configuration database by placing records of volumes, plexes, and subdisks either into a filesystem that is not a ptx/SVM volume, or into the root filesystem. For each disk group, issue the following command:

    # vxprint -g diskgroup -m >  /xxx/diskgroup.objects
  3. Back up each disk group's diskgroup.disks and diskgroup.objects files onto tape as a precautionary measure.


ptx/X.25 Configuration

Before installing a new version of ptx/X.25, we recommend that you save your current configuration. Complete the following steps:

  1. As root, enter the following command, where directory is an existing, writable directory.

    # /usr/lib/x25/savx25conf directory 

    All X.25 configuration information is saved in various subdirectories and files under directory.

    When the configuration information has been saved, the following message appears:

    Current X.25 configuration has been saved in directory

Software Licensing

Certain layered products require that you enter a license key before the product can be installed from the CD-ROM. When you purchase these products, you will receive installation license documents in a specially marked folder.


ATTENTION

ptx/LICENSE is not needed to install products that require an installation license.


Each license document will contain a license key such as the following:

License Type:       Installation
Product Name:       ptx/NFS
Product Version:    4.6.5
Vendor ID:          68b948b47ef4.02.8a.5f.3d.1e.00.00.00
License Password:   thzk2b9cjknskriivt6jntnx9e
Expiration Date:    05/15/37
License Checksum:   11339  

When you select a licensed product for installation, you will be prompted for the license key information if you have not already entered a valid license key for that product. The license key information is stored in the system nodelock file, /var/netls/nodelock.

If DYNIX/ptx V4.4 is already installed on your system, you can use the Add Installation License menu option to enter the license key information before you install products requiring a license.

MENU PATH

ptx/ADMIN Path

System Administration -> Software License Management -> Add Installation License

Table 2-2 lists the layered products that require a license key for installation.

Table 2-2. Products Requiring a License Key

ptx/ATM

ptx/NFS

ptx/C++

ptx/OSI Transports

ptx/CFS

ptx/SNA TN3270 Client

ptx/CLUSTERS

ptx/SVM

ptx/EFS

ptx/X.25

ptx/ITX



Deinstall Unsupported Software

You must deinstall any unsupported software before starting the update to V4.4.10. The update will fail if these products are not removed.

To deinstall products, use the ptx/ADMIN Remove Software Package form (System Administration -> Software Management -> Remove Software Package). Table 2-3 lists unsupported products and specific versions of supported products that must be deinstalled.

Table 2-3. Software to Deinstall

ptx/AUTOCHANGER

ptx/LAT

ptx/OPTICAL

ptx/BACKUP

ptx/LDAPa

ptx/PEP

ptx/C++ V2.1.3

ptx/LICENSEb

ptx/SDI

ptx/CKM

ptx/MEMDISK

ptx/VJ

ptx/DLTTM

ptx/NQS

ptx/VT

ptx/DNA

ptx/NWS

ptx/X.400 Base Services

ptx/FTAM

ptx/NWSmigrate

ptx/X.400 Sendmail Gateway

ptx/JUKEBOX


a. After deinstalling ptx/LDAP, you must remove the LDAP startup script /etc/rc2.d/S97LDAP.

b. Although ptx/LICENSE is a supported product, it must be removed before the upgrade to DYNIX/ptx V4.4.10. Otherwise, the upgrade will fail.

The Annex3® and MicroAnnex third-party products must also be removed. Delete the following:


Product-Specific Pre-Installation Information

This section contains information that you should be aware of or steps that you must perform before starting the installation. Only the products listed in this section require pre-installation steps.


ATTENTION

If you need to upgrade ptx/SVM from V1.x, you must contact Customer Support before the installation. Do not install DYNIX/ptx V4.4.10 or any layered software before contacting your customer service representative.



Apache Web Server

This product is no longer available from IBM. However, existing DYNIX/ptx customers who already have Apache Web Server V1.3.12 can use this product with DYNIX/ptx V4.4.10.


Backup Toolkit

Backup Toolkit is a prerequisite for installing the SAMS:Alexandria backup software. Refer to the Backup Toolkit Release Notes for information about installing SAMS:Alexandria.


CommandPoint Products

CommandPoint Clusters and CommandPoint SVM clients can be installed on a system running DYNIX/ptx or on a PC running Windows NTTM. See the CommandPoint Clusters Release Notes and User's Guide and the CommandPoint SVM Release Notes for Windows NT installation requirements and software installation instructions.

These products are included on the Systems Management Software CD-ROM.


CSM

When the CSM software is installed, you may see a message stating that /usr/ssw is not mounted. The message can incorrectly appear even though /usr/ssw is mounted. Also, the complete message is not displayed. When the message appears, you must enter N to continue the installation. For more information about this message, see "CSM Installation Problem" in the installation chapters later in these release notes.


DYNIX/ptx

DYNIX/ptx V4.4.10 can be upgraded from DYNIX/ptx V4.4.4 or later. Upgrades from other versions of DYNIX/ptx are not supported. If you are currently running a different version of DYNIX/ptx, either perform a scratch installation of V4.4.10, or upgrade first to V4.4.4 or later and then upgrade to V4.4.10.

Appendix B describes file conflicts that may occur during an update to V4.4.10. This information can help you determine whether you want to handle file conflicts during or after the installation.


Encryption

The encryption software should be reinstalled whenever the base operating system is updated.


Fibre Channel Software

The FC Bridge, FC Switch, and FC Host Adapter software is installed on new systems before they ship from the factory.

If you are updating the FC software on an existing system, you should be aware that the FC Switch software is intended only for systems with switched fabric. Do not install the FC Switch software on a system with arbitrated loop (FC-AL Hub).

This release provides two versions of the FC Switch software. Version 1.6c3 is for the SilkWorm® 1000 family of switches; Version a2.2.1a is for the IBM 2109 and SilkWorm 2000 family of switches. In ptx/INSTALL, Version 1.6c3 is listed as V1.6.3 and Version a2.2.1a is listed as V2.2.1.

There are also two versions of the Fibre Channel Host Adapter software. Version FF2.30 (V2.3.0) for Emulex 3 Host Adapters and version SF3.22a0 (V3.2.2) for Emulex 4 Host Adapters. To determine the Emulex version of your Host Adapters, run the /etc/showcfg command and check the entries for the FF devices. Emulex version 3 is referred to as hw ver 3; Emulex version 4 is referred to as hw ver 4. Be sure to install and download the appropriate version of the Fibre Channel Host Adapter software. If your system includes both Emulex 3 and Emulex 4 Host Adapters, you will need to install both versions of the software and then download the appropriate version to each host adapter.


ATTENTION

If your system has a CLARiiON disk subsystem, you may need to deconfigure all rd devices before using ffutil to download the Fibre Channel Host Adapter firmware. The DYNIX/ptx V4.4.x Fibre Channel Software Release Notes describe this procedure.



Micro Focus COBOL

Micro Focus COBOL Developer Suite V4.1.0 and Micro Focus Application Server/OSX V4.1.0 are no longer available from IBM. However, existing DYNIX/ptx customers who already have these versions of the Micro Focus products can continue to use them with DYNIX/ptx V4.4.10.


MQSeries for DYNIX/ptx

This product is no longer available from IBM. However, existing DYNIX/ptx customers who already have MQSeries for DYNIX/ptx V1.1.0 can use this product with DYNIX/ptx V4.4.10.


Online Diagnostics

The online diagnostic V1.4.1 software for Symmetry systems is located on the DYNIX/ptx and Layered Products CD-ROM and is listed as ol_diag in ptx/INSTALL.

The NUMA Online Diagnostics product consists of two portions, one that must be installed on the console and one that must be installed on DYNIX/ptx as follows:

Additionally, to run the online diagnostics on NUMA systems with 0300-Series quads, you must increase the values of the following kernel parameters:

SHMMAX
81920000
SHMMNI
200

You must recompile and reboot the kernel for the changes to take effect. See the DYNIX/ptx System Configuration and Performance Guide for information about modifying kernel parameters.


ptx/BaseComms

ptx/BaseComms contains facilities such as interface definitions that are common to all networking products running on DYNIX/ptx, and is a prerequisite for their installation.


ptx/Channel Attach

This product is no longer available from IBM. However, existing DYNIX/ptx customers who already have ptx/Channel Attach V1.0.1 can use this product with DYNIX/ptx V4.4.10.


ptx/CLUSTERS


Upgrade From ptx/CLUSTERS V1.1 or V1.3

The installation procedure for ptx/CLUSTERS automatically upgrades existing cluster configurations on systems that are properly configured and running ptx/CLUSTERS V1.1.x or V1.3.x.

The ptx/CLUSTERS installation does the following:

The conversion process requires that ptx/CLUSTERS V1.x or V1.3.x be installed so that configuration parameters from the existing implementation can be migrated to ptx/CLUSTERS V2.1.4. Therefore, ptx/CLUSTERS V2.1.4 must be installed through either the INIT ALT DISK DELTA or the ALT DISK DELTA procedure.

For Customer Support and Professional Services personnel who install ptx/CLUSTERS: Once the cluster upgrade process has been completed, consult the ptx/CLUSTERS Installer's Guide for additional procedures.


Install ptx/CLUSTERS From Scratch

Only Customer Support and Professional Services personnel perform scratch installations of ptx/CLUSTERS.

When you install ptx/CLUSTERS on a system for the first time or choose not to migrate existing ptx/CLUSTERS software, during the ptx/INSTALL installation process you will be prompted for the following configuration parameters.

Parameter

Action

Cluster ID

The unique ID of the cluster. Must be an integer between 1 and 31, inclusive. Must be set the same on all cluster nodes.

Cluster password

The password of the cluster. Can consist of a maximum of 15 characters. Must be set the same on all cluster nodes.

Node index

The unique ID of each node. Must be a non-negative integer between 0 and 7 (inclusive). Set a different ID for each node.

Expected votes

The total number of nodes in the cluster plus the quorum disk, if you plan to configure one. Must be set the same on all cluster nodes.


These parameters are then placed in the ptx/CLUSTERS configuration file, /etc/clusters/clustcfg.

Once ptx/CLUSTERS is installed on all the nodes, consult the ptx/CLUSTERS Installer's Guide and the ptx/CLUSTERS Administration Guide for information on setting up and configuring the cluster.


ptx/ESBM and ptx/OSBM

ptx/ESBM and ptx/OSBM have been replaced by Backup Toolkit and SAMS:Alexandria. Do not deinstall ptx/ESBM and ptx/OSBM before installing Backup Toolkit and SAMS:Alexandria.


ptx/JSE

ptx/JSE V1.1.2 and ptx/JSE V1.2.1 can be installed from the DYNIX/ptx and Layered Products CD-ROM. Refer to the appropriate version of the ptx/JSE Release Notes for information about the contents of each of these versions.


ptx/LDAP

ptx/LDAP has been retired. It is not supported on DYNIX/ptx V4.4.10 and must be deinstalled before the upgrade. After deinstalling ptx/LDAP, you must remove the LDAP startup script /etc/rc2.d/S97LDAP.


ptx/LICENSE

ptx/LICENSE is needed only if you will be running Micro Focus® COBOL. ptx/TCP/IP must be configured for networking before you configure ptx/LICENSE.

If ptx/LICENSE V1.x is currently installed on your system, it must be deinstalled before the DYNIX/ptx V4.4.10 installation.


ptx/NWS

ptx/NWS has been retired. It is not supported on DYNIX/ptx V4.4.10 and must be deinstalled before the upgrade.


ptx/RAID

When ptx/RAID is upgraded from V1.4.0 to V2.0.5, the /etc/dumpconf command will be removed if you do not modify the preview.log file during the ptx/RAID installation. In the preview.log, change the entry for /etc/dumpconf from CONFLICT-DELETE to CONFLICT-SKIP.


ptx/SNA

The ptx/SNA products cannot be installed with the INIT ALT DISK DELTA or ALT DISK DELTA procedures. Use the ROOT procedure to install these products after updating the base operating system.

The ptx/SNA products can be installed as part of a scratch installation.


ptx/SPDRIVERS

ptx/SPDRIVERS contains driver support for several devices used on NUMA systems. It also provides the ffutil utility, which is used to download the FC Host Adapter firmware, and a Fibre Channel diagnostic utility used by Customer Support. ptx/SPDRIVERS must be installed on IBM xSeries 430 and NUMA-Q 2000 systems to obtain the driver support and the FC utilities. It should also be installed on Symmetry systems to obtain the driver support.

ptx/SPDRIVERS should be installed before you build the kernel; you will see warnings if it is not installed.


ptx/SVM

The ptx/SVM V2.1.4 release contains major changes from ptx/SVM V1.x. If you want to upgrade to ptx/SVM V2.1.4 from ptx/SVM V1.x, contact your customer service representative. Do not install DYNIX/ptx V4.4.10 or any layered software before arranging with Customer Support for the ptx/SVM migration.

If you are upgrading from ptx/SVM 2.x, you can perform a normal delta upgrade installation. For details, see Chapter 4 for IBM xSeries 430 and NUMA-Q 2000 systems or Chapter 5 for Symmetry 5000 systems.


ATTENTION

If you are installing a new version of ptx/SVM and are not upgrading the base operating system, we recommend that you perform the installation on an alternate disk, as described above. Although the ROOT method can be used for the installation, it must be performed in single-user mode and requires more system downtime.


ptx/SVM automatically places the root filesystem and the primary swap device under its control (and places them in the rootdg disk group) when the software is first installed and the system is first started. Once under ptx/SVM control, the root and primary swap devices appear as volumes and have the same characteristics as other ptx/SVM volumes. The volume that is configured for use as a swap area is named SWAPVOL by ptx/SVM; the volume that contains the root filesystem is named ROOTVOL by ptx/SVM.

The ROOTVOL and SWAPVOL volumes, as well as other parts of the root disk required for a successful boot of the system, can be mirrored. See the ptx/SVM Administration Guide for more information.


ptx/SYNC

Verify with Customer Support that the hardware for the synchronous controller board is installed.

This product cannot be installed with the INIT ALT DISK DELTA or ALT DISK DELTA procedures. Use the ROOT procedure to install this product after updating the base operating system. ptx/SYNC can also be installed as part of a scratch installation.


ptx/TCP/IP

If you are upgrading from an earlier version of ptx/TCP/IP, take the following actions before starting the upgrade:

During the installation, you may need to modify the preview log for ptx/TCP/IP. See "File Conflicts in ptx/TCP/IP V4.5.4" in Appendix B for more information.


ptx/WINDOWS

This product has been renamed ptx/XWM. See the next section, "ptx/XWM," for more information.


ptx/XWM

ptx/XWM consists of X Window SystemTM X11R6.5.1 and OSF/Motif® V2.1.30 software. This software is supported by Customer Support. In ptx/INSTALL, this product is named windows.

ptx/XWM Contributed is no longer provided by IBM. However, existing DYNIX/ptx customers who already have ptx/XWM Contributed V4.5.x installed can use this product with DYNIX/ptx V4.4.10.

ptx/XWM installs files in /usr/src. If /usr/src is a separate filesystem on your machine, this product cannot be installed with the INIT ALT DISK DELTA procedure.


ptx/XWM Upgrade Issues


Increase in Product Size.

The previous ptx/WINDOWS V4.4.1 product used approximately 47 MB of space. ptx/XWM requires approximately 76 MB.


.Xdefaults File.

The X11R5 .Xdefaults user configuration file was renamed in X11R6 to .Xresources. The ptx/WINDOWS default $HOME/.Xdefaults file (/usr/admin.ptx/etc/base.dir/.Xdefaults), which was used when creating new user accounts, will be removed during the ptx/XWM installation. If you have made any modifications to the default /usr/admin.ptx/etc/base.dir/.Xdefaults file, be sure to save it before you begin the ptx/XWM installation. When the installation is complete, you can merge your changes into the new /usr/admin.ptx/etc/base.dir/.Xresources file.


Obsolete Software.

Certain X11R5 and Motif 1.2 libraries, client applications, and source code provided with ptx/WINDOWS V4.4.1 are now obsolete and will be removed when ptx/XWM is installed. If you want to retain any of this software, take one of the following actions:


ptx/X.25

This product cannot be installed on an alternate disk. Use the ROOT procedure to install this product after updating the base operating system.

ptx/X.25 can be installed as part of a scratch installation.


Public Software

This software is no longer available from IBM. However, existing DYNIX/ptx customers who already have Public Software V4.4.x can use this product with DYNIX/ptx V4.4.10. This software is not supported by Customer Support.


SequentLINK

SequentLINK is installed on new systems before they are shipped from the factory. For factory-installed SequentLINK, refer to Chapter 2 of the SequentLINK Customer's Manual.

To install SequentLINK on a system that does not already have it, or to upgrade SequentLINK to the current version, refer to Chapter 2 of the SequentLINK Customer's Manual. You must use the ROOT procedure to install SequentLINK.