DYNIX/ptx V4.4.7 runs on NUMA-Q, CSM-based Symmetry 5000, and SSM-based Symmetry 2000 systems only.
To run V4.4.7, 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 NUMA-Q systems, the minimum memory requirement is 512-KB per Quad. An average NUMA-Q 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 CSM-based systems is 64 MB of physical memory for MAXUSERS up to 64. An additional 1 MB is needed for every two users beyond 64. For SSM-based systems, the minimum memory requirement is 160 MB. 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 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.
The following restrictions must be followed when running DYNIX/ptx V4.4.7. In these restrictions, local refers to devices connected directly to the PCI/SCSI interface on NUMA-Q systems, to devices connected directly to the HPSE portion of the CSM on CSM-based systems, or to devices connected directly to the SSM bus on SSM-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 or bootbay. 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).
If /usr is a separate filesystem, it must be located on a local (not shareable) SCSI disk.
The miniroot partition must be located on a local (not shareable) SCSI disk. It must occupy the entire partition.
The optional /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 NUMA-Q 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.
On NUMA-Q systems, do not run commands that use large amounts of memory while the system is in the stand-alone kernel (SAK), particularly when it is in restricted mode. The system may hang or panic if an attempt is made to use too many memory resources. 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 NUMA-Q or Symmetry system is upgraded to DYNIX/ptx V4.4.7. The minimum supported versions are as follows:
To determine the EMC microcode version, contact either your local EMC service representative or the EMC customer support center. 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 If you are running a version of DYNIX/ptx earlier than V4.4.2 on a host that is connected to one or more EMC disk storage subsystems, contact your customer service representative for assistance.
ATTENTION In V4.4.7, 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 (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.
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-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.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.
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 PATHptx/ADMIN PathSystem Administration -> Software License Management -> Add Installation License |
Table 2-2 lists the layered products that require a license key for installation.
MQSeries for DYNIX/ptx |
ptx/ITX |
ptx/ATM |
ptx/NFS |
ptx/C++ |
ptx/OSI Transports |
ptx/CFS |
ptx/SDI |
ptx/Channel Attach |
ptx/SNA TN3270 Client |
ptx/CLUSTERS |
ptx/SVM |
ptx/EFS |
ptx/X.25 |
You must deinstall any unsupported software before starting the update to V4.4.7. 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.
ptx/AUTOCHANGER |
ptx/DLTTM |
ptx/NQS |
ptx/BACKUP |
ptx/JUKEBOX |
ptx/OPTICAL |
ptx/C++ V2.1.3 |
ptx/MEMDISK |
ptx/VJ |
ptx/CKM |
The Annex3® and MicroAnnex third-party products must also be removed. Delete the following:
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.7 or any layered software before contacting your customer service representative.
This product can be downloaded from the SequentDirectTM Web page and then installed with ptx/INSTALL. It is not provided on the DYNIX/ptx and Layered Products CD-ROM. Refer to the Apache Web Server Release Notes, also on the SequentDirect Web page, for information about downloading this product from the Web.
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 Clusters, CommandPoint SVM clients, and CommandPoint for Unicenter TNG 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, the CommandPoint SVM Release Notes, and the CommandPoint for Unicenter TNG Release Notes for Windows NT installation requirements and software installation instructions.
These products are included on the Systems Management Software CD-ROM.
When the CSM or SSM 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/SSM Installation Problem" in the installation chapters later in these release notes.
DYNIX/ptx V4.4.7 can be upgraded from DYNIX/ptx V4.2.3 or later, and from V4.4.2 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.7, or upgrade first to V4.2.4 or V4.4.x and then upgrade to V4.4.7.
Appendix B describes file conflicts that may occur during an update to V4.4.7. This information can help you determine whether you want to handle file conflicts during or after the installation.
The encryption software is available only in the United States and Canada. It 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.
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 2.0.3a is for the SilkWorm 2000 family of switches. In ptx/INSTALL, Version 1.6c3 is listed as V1.6.3; Version 2.0.3a is listed as V2.0.3.
There are also two versions of the Fibre Channel Host Adapter software. Version FF2.30 is for Emulex 3 Host Adapters; version SF2.22 is 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 Fibre Channel Software Release Notes describe this procedure.
As a minimum, MQSeries for DYNIX/ptx requires approximately 20 MB of disk space for the product code and data. By default, working data for this product is stored in /var/mqm. See Figure C-1 in the MQSeries for DYNIX/ptx System Management Guide for the directory structure.
For added confidence in the integrity of your data, you are strongly advised to put your logs on a different physical drive from the one that you use for the queues.
MQSeries requires certain files to be located in /opt/mqm or subdirectories thereof, and other files to be located in /var/mqm or subdirectories thereof. By default, MQSeries for DYNIX/ptx installs these as directories in the root filesystem and not as separate filesystems.
We recommend that you do not install this product in the root filesystem, as it may cause the filesystem to fill up. Instead, determine where you have adequate storage space. The installation program prompts you for the location in which to install these files. If you supply a path, it automatically creates a symbolic link between the location you supply and the expected location /opt/mqm or /var/mqm.
The files in /usr/mqm are not likely to fill the filesystem and therefore require no symbolic link.
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-Q Online Diagnostics Dispatcher is now located on the DYNIX/ptx and Layered Products CD and can be installed at the same time as the operating system. It is listed as onldiag in ptx/INSTALL. The NUMA-Q Online Diagnostics Console software is located on the NUMA-Q Console Software CD-ROM and is installed with the console software.
To run the online diagnostics on NUMA-Q 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.
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.
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:
Sets core configuration parameters
During the preview phase, the software sets the following ptx/CLUSTERS core configuration parameters.
Parameter |
Action |
Cluster ID |
Set to 17 by default on all cluster nodes |
Cluster password |
Set to password on all cluster nodes |
Node index |
Set to the value of the existing node index |
Expected votes |
Set to be the length of the master node list |
These parameters are then placed in the ptx/CLUSTERS configuration file, /etc/clusters/clustcfg.
Converts LLI information for use by CCIs
The installation procedure modifies entries in the /var/tcp/ifnets and /var/tcp/ifaddrs files so that they will work properly with ptx/CLUSTERS.
Converts Lock Manager domains
The installation procedure converts existing Lock Manager domains to the proper format for ptx/CLUSTERS.
Names shared devices
The installation procedure ensures that the shared device names used in ptx/CLUSTERS V1.x and V1.3.x are retained for use by ptx/CLUSTERS.
Creates a quorum disk from an existing CMA
The installation procedure designates the last CMA listed by the immbroker -t command as a quorum disk.
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.3. Therefore, ptx/CLUSTERS V2.1.3 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.
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 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 V1.1.2 can be installed from the DYNIX/ptx and Layered Products CD-ROM, or it can be downloaded from the SequentDirect web page and then installed with ptx/INSTALL. ptx/JSE V1.2.1 is available only from the SequentDirect web page. Refer to the ptx/JSE Release Notes for information about downloading this product from the web.
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.
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.
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 with the following exception: ptx/SNA RJE (3770) and ptx/SNA LU6.2 cannot be scratch installed on an alternate disk on Symmetry systems that are currently running a version of DYNIX/ptx earlier than V4.4.2. Use the ROOT procedure to install these products after the scratch installation of the base operating system.
ptx/SPDRIVERS contains driver support for several devices used on NUMA-Q and Symmetry 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 NUMA-Q 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.
The ptx/SVM V2.1.3 release contains major changes from ptx/SVM V1.x. If you want to upgrade to ptx/SVM V2.1.3 from ptx/SVM V1.x, contact your customer service representative. Do not install DYNIX/ptx V4.4.7 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 NUMA-Q 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.
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.
If you are upgrading from an earlier version of ptx/TCP/IP, take the following actions before starting the upgrade:
Remove the /usr/options/tcp/inetd_conf directory, if present, from both the current root disk and the alternate disk to be used for the installation.
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. See "File Conflicts in ptx/TCP/IP V4.5.3" in Appendix B for more information.
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 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 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 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.
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.
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 with the following exception: a scratch installation on an alternate disk is not supported on Symmetry systems currently running a version of DYNIX/ptx earlier than V4.4.2. On these systems, ptx/X.25 must be installed with the ROOT procedure after updating the base operating system.
The public software includes less, EMACSTM, and the gdb debugger. Installing EMACS is optional. This software is not supported by Customer Support.
The public 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.