DYNIX/ptx V4.5.2 runs on IBM xSeries 430, NUMA-Q 2000, and Symmetry 5000 systems only.
To run V4.5.2, your system must meet these requirements:
Contain adequate swap space. At a minimum, your system must have as much swap space as it has physical memory, plus at least 10 MB. (The /etc/showcfg -s command lists the amount of physical memory on your system.)
Contain adequate physical memory for your system's configuration. The amount of memory required depends on the following factors.
The value of the MAXUSERS kernel parameter. This parameter is a "system load factor" used to size other kernel parameters. It is typically set to the number of users that are expected to be using the system simultaneously. (MAXUSERS is specified in the system configuration file, /etc/conf/uts/symmetry/unix.<config>. You can also view the value of MAXUSERS with the ptx/ADMIN Kernel Configuration option.)
Changes to kernel parameters that affect memory.
The performance requirements of your applications.
For IBM xSeries 430 and NUMA-Q 2000 systems, the minimum memory requirement is 512-MB per Quad. An average IBM xSeries 430 and NUMA-Q 2000 configuration might have 2 - 3 GB of physical memory for MAXUSERS up to 64 and .75 MB to 1 MB for each additional user.
The minimum memory requirement for Symmetry 5000 systems is 64 MB of physical memory for MAXUSERS up to 64. An additional 1 MB is needed for every two users beyond 64.
An average Symmetry configuration might have 512 MB - 1 GB of physical memory for MAXUSERS up to 64 and .75 MB to 1 MB for each additional user.
More physical memory will typically increase overall system performance.
If the system is configured to support a process and networking load that is unreasonably high for the amount of physical memory available, the system will perform poorly, with very high paging and swapping rates.
In the worst possible case of extraordinary memory starvation, where all pageable memory resources are exhausted, it is possible that the system will deadlock when it attempts to dynamically allocate additional kernel pages.
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.
The following restrictions must be followed when running DYNIX/ptx V4.5.2. 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.
The root, dump, and primary swap partitions must be located on local (not sharable) SCSI disks connected to a bootable Pbay. They cannot be located on disks attached to the Fibre Channel.
If the root and primary swap partitions are under ptx/SVM control, they must be a single complete plex with exactly one subdisk (that is, they can be mirrored, but not striped or concatenated).
The miniroot partition must be located on a local (not shareable) SCSI disk. It must occupy the entire partition.
The /etc/dumplist file, which lists devices that can be used for a memory dump, should not contain the primary swap partition. If you are using swap partitions as dump devices, you must have enough secondary swap partitions to accommodate an entire crash dump.
When powering up a IBM xSeries 430 and NUMA-Q 2000 system, power on all Pbays before powering on the Fibre Channel Bridges. On power-up, the FC Bridge will attempt to spin up all disks. If the Pbay is off, the FC Bridge will not be able to register the disks.
In general, the stand-alone kernel should not be used for system maintenance operations, except as noted in the release notes. System maintenance operations should be done while running the standard kernel in single-user mode. The SAK is primarily a boot loader. It has limited memory availability and does not support the full set of services available in a standard kernel. Applications that rely on services that are not available or that use large amounts of memory may hang or panic the SAK. For details about running commands from the SAK, refer to the DYNIX/ptx System Administration Guide.
Each EMC Symmetrix® disk storage subsystem must be running the appropriate EMC microcode version before your system is upgraded to DYNIX/ptx V4.5.2. 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.5.2.
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.5.2, you do not need to set timeouts for EMC devices in the mpt_space.c file.
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.
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 |
Use the following procedure to back up a ptx/SVM configuration database. You must be root to perform the procedure.
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
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 on a system running DYNIX/ptx V4.4.2, issue the following command:
# vxprint -g diskgroup -mvps > /xxx/diskgroup.objects
For each disk group on a system running DYNIX/ptx V4.4.4 or later, issue the following command:
# vxprint -g diskgroup -m > /xxx/diskgroup.objects
Back up each disk group's diskgroup.disks and diskgroup.objects files onto tape as a precautionary measure.
Before installing a new version of ptx/X.25, we recommend that you save your current configuration. Complete the following steps:
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
Certain layered products require that you enter a license key before the product can be installed from the CD. 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.0 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.
Alternatively, you can use the Add Installation License menu option to enter the license key information before you install products requiring a license.
![]() | MENU PATHptx/ADMIN PathSystem Administration -> Software License Management -> Add Installation License |
Table 2-2 lists the layered products that require a license key for installation.
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 |
You must deinstall the unsupported software listed in Table 2-3 before starting the update to V4.5.2. 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).
ptx/DNA |
ptx/LICENSE V1.0.0 |
ptx/VT |
ptx/FTAM |
ptx/NWS |
ptx/X.400 Base Services |
ptx/LAT |
ptx/PEP |
ptx/X.400 Sendmail Gateway |
ptx/LDAP |
ptx/SDI |
After deinstalling ptx/LDAP, you must remove the LDAP startup script /etc/rc2.d/S97LDAP.
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.5.2 kernel compile will fail.
The ptx/TCP/IP parameters are removed or renamed automatically during the ptx/TCP/IP installation.
The following kernel parameters are now obsolete. If these parameters are in your site file (/usr/conf/uts/symmetry/sci/site.<machine_name> or /usr/conf/uts/symmetry/sb8000/site.<machine_name>), remove them before starting the installation.
The FDIV_BUG parameter has been renamed to FDIV_BUG_FLAG. If this parameter is included in your site file, rename it before performing the installation.
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.
N_TCP_PCB_FREE
N_UDP_PCB_FREE
N_RAW_PCB_FREE
MAX_REASSQ (replaced by MAX_IPQ_HDRS and MAX_IPQ_NODES)
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.
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.
The Apache Web Server is no longer available from IBM. However, existing DYNIX/ptx customers who already have Apache Web Server V1.3.12 can use it with this release of DYNIX/ptx.
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.
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 Base provides a common infrastructure for CommandPoint ADMIN, CommandPoint CLUSTERS, and CommandPoint SVM, and is a prerequisite for those products.
CommandPoint Clusters, CommandPoint SVM clients, and CommandPoint for Unicenter TNG can be installed on an NUMA systems running DYNIX/ptx or on a PC running Windows NTTM. See the CommandPoint Clusters Release Notes and User's Guide, the CommandPoint SVM Release Notes, and the CommandPoint for Unicenter TNG Release Notes for Windows NT installation requirements and software installation instructions.
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.
Appendix B describes file conflicts that may occur during an update to V4.5.2. This information can help you determine whether you want to handle file conflicts during or after the installation.
If /var/ees is created as a separate filesystem, it must not be under SVM control.
The encryption software should be reinstalled whenever the base operating system is updated.
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 IBM 2109 and 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 automatically download the appropriate firmware for your system.
The online diagnostic V1.4.1 software for Symmetry systems is located on the DYNIX/ptx and Layered Products, Volume 1 CD and is listed as ol_diag in ptx/INSTALL.
The NUMA-Q online diagnostics consists of a portion that must be installed on the console and a portion that must be installed on DYNIX/ptx, as follows:
The DYNIX/ptx portion, provided as NUMA-Q Online Diagnostics Dispatcher, is included on the DYNIX/ptx and Layered Products, Volume 1 CD, and it is installed with ptx/INSTALL. It is listed as onldiag in ptx/INSTALL.
The console portion is included on the NUMA Console Software CD and is installed with the NUMA Console Software Setup program. For details on this installation, refer to the NUMA Console Software Release Notes.
To run the online diagnostics on NUMA systems, you must increase the value of the following kernel parameter on the V4.5 system:
Additionally, to run the online diagnostics on NUMA systems with 0300-Series quads, you must increase the values of the following kernel parameters:
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.
Before upgrading from ptx/ATM V2.0.0 to ptx/ATM V4.5.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.5.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 contains facilities such as interface definitions that are common to all networking products for DYNIX/ptx, and is a prerequisite for their installation.
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/Configuration Assistant provides an interface to perform some initial configuration and setup of your system. The following tasks are included:
Set or verify the system date and time
Set the root password
Manage system swap space
Configure ptx/TCP/IP for network communications
If you install this product, it will run the first time the system is booted on DYNIX/ptx V4.5.2.
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/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.
This product can be installed from the DYNIX/ptx and Layered Products CD. Refer to the appropriate version of the ptx/JSE Release Notes for information about the contents of a particular ptx/JSE version.
ptx/LDAP has been retired. It is not supported on DYNIX/ptx V4.5 and must be deinstalled before the upgrade. After deinstalling ptx/LDAP, you must remove the LDAP startup script /etc/rc2.d/S97LDAP.
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.0.0 is currently installed on your system, it must be deinstalled before the DYNIX/ptx V4.5.2 installation.
This product contains an rc script that completes the installation of several layered products. It is automatically installed and is run the first time that the system is booted on DYNIX/ptx V4.5.
This product is labeled "Layered product Install Patch" on the ptx/INSTALL product selection screen.
ptx/NWS has been retired. It is not supported on DYNIX/ptx V4.5 and must be deinstalled before the upgrade.
ptx/SPDRIVERS contains driver support for several devices used on NUMA systems. It should be installed before you build the kernel; you will see warnings if it is not installed.
ptx/SPDRIVERS must be installed on IBM xSeries 430 and NUMA-Q 2000 systems. It provides the cfwdl utility, which is used to download firmware, and a Fibre Channel diagnostic utility used by Customer Support. ptx/SPDRIVERS should also be installed on Symmetry systems to obtain the driver support.
ATTENTION If you are upgrading from a host running DYNIX/ptx V4.4.x or V4.5.1, a change in the way DYNIX/ptx V4.5.2 generates UUIDs for tape drives causes device name slippage for tc and tl devices that are attached at the time of the upgrade. When the system reboots, these devices will have temporary names in the device naming database. Any applications, such as backup applications, that physically configure these device names will be unable to locate the associated devices.
This scenario occurs because DYNIX/ptx V4.5.1 and V4.4.x do not use device serial numbers to generate the UUID for a tape device, but DYNIX/ptx V4.5.2 does. These modifications to DYNIX/ptx V4.5.2 resulted in a change in the unit number which caused the device number to be recalculated by the device naming database.
Before upgrading to DYNIX/ptx V4.5.2 and ptx/SPDRIVERS V3.2.x, note the names of all tc and tl devices that are attached to the system. Then, after the upgrade, delete the previous device names from the device naming database (devctl -D) and rename the newly named devices to the previous names (devctl -n).
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.
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.
Verify with Customer Support that the hardware for the synchronous controller board is installed.
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 performs the following actions:
Changes the netmask of the loop device to 255.255.255.255 in the /var/tcp/ifaddrs file.
Removes the inetd_conf directory.
Preserves the state of rexecd (either commented or uncommented) as it was in the old inetd.conf file.
This product has been renamed ptx/XWM. See the next section, "ptx/XWM," for more information.
ptx/XWM consists of two products:
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.
The following issues apply only to upgrades from ptx/WINDOWS.
The previous ptx/WINDOWS V4.4.1 product used approximately 47 MB of space. ptx/XWM requires approximately 76 MB. The ptx/XWM Contributed product is the same size as ptx/WINDOWS Contributed.
The X11R5 .Xdefaults user configuration file was renamed in X11R6 to .Xresources. The previous 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.
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:
To retain certain individual binaries, edit the preview log during the ptx/XWM installation. The preview log will specify the files to be deleted during the installation. Remove the entries for those binaries that you want to retain on your system. This is the preferred method to save old binaries; it avoids saving unneeded or duplicate binaries.
To retain all of the old binaries or software, rename the following directories before updating to ptx/XWM.
/usr/bin/X11
/usr/lib/X11
/usr/src/ptxWINDOWS
After the installation, you can add the renamed bin directory to your PATH. For example, if you rename /usr/bin/X11 to /usr/bin/X11R5, be sure to place the renamed directory after the new /usr/bin/X11 in your PATH environment variable.
The Public Software product includes 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 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.