Chapter 2
Before the Installation


System Requirements

DYNIX/ptx V4.6.0 runs on NUMA-Q systems only.

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


Disk Space Requirements

Root and /usr are distributed as a single filesystem. The combined root filesystem requires a minimum of 2 GB of disk space.

The default VTOCs contain a 1-GB root partition 0. If you are using the default VTOC or your root partition is smaller than 2 GB, you will need to increase the size of the partition as described in Appendix C.

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.


ATTENTION

The installation will require approximately 150 MB of disk space in addition to the amount calculated by ptx/INSTALL.



Operational Restrictions

The following restrictions must be followed when running DYNIX/ptx V4.6.0. In these restrictions, local refers to devices connected directly to the PCI/SCSI interface. All other devices are shareable; they can be shared by nodes running ptx/CLUSTERS.


Requirements for EMC Disk Subsystems

Each EMC® Symmetrix® disk storage subsystem must be running the appropriate EMC microcode version before your system is upgraded to DYNIX/ptx V4.6.0. 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.6.0.

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.


ATTENTION

In V4.6.0, 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. 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.

    Issue the following command for each disk group:

    # 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

You will need to enter a license key before installing certain layered products. When you purchase these products, you will receive installation license documents in a specially marked folder.

Each license document contains a license key:

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

You do not need to install ptx/LICENSE to enter the license key information. ptx/LICENSE is needed only for MicroFocus Cobol.

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.

Alternatively, you can use ptx/ADMIN to enter the license key information before you install the products. (Select 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/EFS

ptx/C++

ptx/ITX

ptx/CFS

ptx/NFS

ptx/Channel Attach

ptx/SVM

ptx/CLUSTERS

ptx/X.25



Deinstall Unsupported Software

You must deinstall the unsupported software listed in Table 2-3 before starting the update to V4.6.0. 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. Software to Deinstall

ptx/DNA

ptx/NWS

ptx/SNA

ptx/FTAM

ptx/OSI

ptx/VT

ptx/LAT

ptx/PEP

ptx/X.400 Base Services

ptx/LDAP

ptx/SDI

ptx/X.400 Sendmail Gateway


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


Modify the Local site File

Certain DYNIX/ptx and ptx/TCP/IP parameters have been obsoleted or renamed. If the affected DYNIX/ptx parameters are in your site file, you should manually remove or rename them before upgrading the operating system. If the parameters are not removed, the V4.6.0 kernel compile will fail.

The ptx/TCP/IP parameters are removed or renamed automatically during the ptx/TCP/IP installation.


DYNIX/ptx Parameters

The following kernel parameters became obsolete in the V4.5 or V4.6 releases. If these parameters are in your site file (/usr/conf/uts/symmetry/sci/site.<machine_name>), remove them before starting the installation.

Table 2-4. Obsolete Kernel Parameters

CDFS_MOUNT

FLINO_MULT

NFIFO

CDFS_NCDIV

MFILE_DIV

NFILE

CDFS_NCMULT

MFILE_MULT

NMFILE

CDFS_NCSIZE

MSGMAP

NMOUNT

FDIV_BUG_FLAG

MSGMNI

P_LOCK_DEBUG

FIFO_MULT

MSGSEG

SEMMAP

FILCK_MULT

MSGSSZ

SEMMNI

FILE_DIV

NABUF_DYN_MULT

SHMMNI

FILE_MULT

NABUF_DYN_DIV

SHMSEG

FIST_BUG

NDQUOT

STRMEDFRAC



ptx/TCP/IP Kernel Parameters

When ptx/TCP/IP is installed, it will remove the following parameters from your local site file. These parameters are either obsolete or have been replaced by other parameters.

The ptx/TCP/IP installation will also rename the MAX_IP_PROTO parameter to N_DEV_IP. The default value of this parameter has changed from 15 to 16.


Set the Node ID and Master ID

Set the Node ID and Master ID, either from the VCS Console window:

Settings -> Advanced -> Nodeid, Master Id

Or from the CLI command line:

-> cd /sys_name/quad_name
-> bootflags nodeid node_id
-> bootflags masterid master_id

The Node ID is specified in your service contract. On a single-node system, the Master ID should match the Node ID. On a clustered system, each node will have a unique Node ID; however, all nodes must use the same Master ID, which should be set to the lowest-numbered Node ID in the cluster.


Pre-Installation Information for Specific Products

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.


Apache Web Server

This product can be downloaded from the SequentDirect Web page and then installed with ptx/INSTALL. It is not provided on the DYNIX/ptx and Layered Products CD. Refer to the Apache Web Server Release Notes, also on the SequentDirect Web page, for information about downloading this product.


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.


cfwdl-Compatible Firmware Bundle

This product contains firmware that can be downloaded with the cfwdl utility. The firmware includes the FC Bridge and Host Adapter, as well as firmware for various types of disks. The cfwdl-Compatible Firmware Bundle Release Notes list the firmware provided with the product.


CommandPoint Products

CommandPoint Base provides a common infrastructure for CommandPoint ADMIN, CommandPoint CLUSTERS, and CommandPoint SVM, and is a prerequisite for those products.

CommandPoint Clusters and CommandPoint SVM clients can be installed on a NUMA-Q 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.


DYNIX/ptx

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


EES

If /var/ees is created as a separate filesystem, it must not be under SVM control.


Encryption

The encryption software is available only in the United States and Canada. It 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.

This release provides two versions of the FC Switch software. Version 1.6c3 is for the SilkWorm® 1000 family of switches and is listed in ptx/INSTALL as V1.6.3. Version 2.1.7 is for the SilkWorm 2000 family of switches.

The FC Bridge and Host Adapter software are included in the cfwdl-Compatible Firmware Bundle product. The common firmware downloader, cfwdl, will download the appropriate firmware for your system.


Online Diagnostics

The NUMA-Q online diagnostics consist of a portion that must be installed on the console and a portion that must be installed on DYNIX/ptx. The DYNIX/ptx portion is included on the DYNIX/ptx and Layered Products, Volume 1 CD; the console portion is included on the NUMA-Q Console Software CD.

To run online diagnostics, you must modify the value of the following kernel parameter on the V4.6 system:

SEMMSL

32


This parameter can be changed dynamically with the sysdef command. To make the change permanent across system reboots, you will need to add a script containing the change to the /etc/ktune.d directory. You can also change the parameter with the ptx/ADMIN "Kernel Configuration" option. The change take place after you compile the kernel and reboot.

You will also need to increase the "red" attribute for the following memory pools:

base.sem

3500

base.shm

3000


To change these attributes dynamically, use the kmstune command. To make the changes permanent across system reboots, edit the base.sem and base.shm scripts in the /etc/ktune.d directory.


ptx/ATM

Before upgrading from ptx/ATM V2.0.0 to ptx/ATM V4.7.0, check the /usr/options directory for the files atmtab and cliptab. If these files are present, they must be removed (or renamed, if you prefer to keep a copy) before starting the ptx/ATM V4.7.0 upgrade.

These files are likely to be present if the machine had been upgraded earlier from ptx/ATM 1.0.x to ptx/ATM 2.0.0. Because of a problem with ptx/ATM 2.0.0 (PR# 246943), these files were left behind after they were migrated from the ptx/ATM 1.0.0 format to the ptx/ATM 2.0.0 format.


ptx/BaseComms

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


ptx/CLUSTERS

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, ptx/INSTALL will prompt you for the following configuration parameter:

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.


This parameter is 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/Configuration Assistant

ptx/Configuration Assistant provides an interface to perform some initial configuration and setup of your system. The following tasks are included:

If you install this product, it will run the first time the system is booted on DYNIX/ptx V4.6.0.

When you exit ptx/Configuration Assistant, you will be asked whether you want it to start automatically the next time you reboot the operating system.


ptx/JSE

This product can be installed from the DYNIX/ptx and Layered Products CD, or it can be downloaded from the SequentDirect web page and then installed with ptx/INSTALL. Refer to the ptx/JSE Release Notes for information about downloading this product from the Web.


ptx/LDAP

ptx/LDAP has been retired. It is not supported on DYNIX/ptx V4.6 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.


ptx/NWS

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


ptx/SPDRIVERS

ptx/SPDRIVERS contains driver support for several devices used on NUMA-Q systems. It should be installed before you build the kernel; you will see warnings if it is not installed.


ptx/SVM

When upgrading from ptx/SVM V2.1.1 or ptx/SVM V2.2.1, the ptx/SVM preview log may show the following conflict:

CONFLICT /usr/lib/vxvm/type/fsgen/fs.d/efs/vxresize - NEW, 
non-matching file already exists
   ----555 bin       bin          nnn nnnnn New BOM entry
   ----555 bin       bin         nnnn nnnnn Fileystem entry

You do not need to change the entry for the vxresize file and can safely ignore this conflict message. ptx/SVM will install the correct version of the vxresize file.

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. Although the ROOT method can be used for the installation, it must be performed in single-user mode and requires more system downtime.

When you perform the initial ptx/SVM setup, you will need to place the root filesystem and the primary swap device under SVM control and place them in the rootdg disk group. 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

Before installing ptx/SYNC, verify with Customer Support that the hardware for the synchronous controller board is installed.


ptx/TCP/IP

If you are upgrading from an earlier version of ptx/TCP/IP, save your current /etc/inetd.conf file in case you need to restore it.

During the installation, you may need to modify the preview log for ptx/TCP/IP. You may also need to merge local information with new files that will be installed. See "File Conflicts in ptx/TCP/IP" in Appendix B for a list of the affected files.

The ptx/TCP/IP installation makes the following changes to the /etc/inetd.conf and /etc/services files. The changes are made regardless of the entry in the preview log (CONFLICT-SKIP or CONFLICT-REPLACE) for these files.

If you are upgrading from a version of ptx/TCP/IP earlier than V4.6.1, the installation also performs the following actions.


ptx/XWM

ptx/XWM consists of two products:

ptx/XWM
X Window SystemTM version X11R6.5 and Motif® version 2.1.30 software. This software is supported by Customer Support. In ptx/INSTALL, this product is named windows.
ptx/XWM Contributed
Software contributed by outside developers or gleaned from the network. This unsupported software is provided as a convenience to the user.

In ptx/INSTALL, this product is named windows-contrib. The name is truncated to windows-co on the software installation screen; however, the full name appears on the product installation directory in /usr/options.

ptx/XWM is located on the DYNIX/ptx and Layered Products Software, Volume 1 CD. ptx/XWM Contributed is located on the Volume 2 CD.

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.


Public Software

The Public Software product includes the less command, EMACSTM, the gdb debugger, and the mkisofs utility. This software is not supported.

The public software is located on the DYNIX/ptx Layered Products Software, Volume 2 CD. This software is installed in /usr/local. If /usr/local is a separate filesystem on your machine, this product cannot be installed with the INIT ALT DISK DELTA procedure.


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.