ptx/INSTALL provides an installation procedure for installing DYNIX/ptx, layered products, and the system software. The installation procedure is invoked from the ptx/ADMIN® menu system. You do not need to install the ptx®/INSTALL product; it is installed on your system automatically. For supplementary information about ptx/INSTALL, refer to the ptx/INSTALL Software Installation Guide.
ptx/INSTALL can be used to install the products listed in Table 1-1 and Table 1-2.
Apache Web Server V1.3.4 |
ptx/NFS® V4.6.4 |
Backup Toolkit V4.4.2 |
ptx/OSI Transport V4.4.1 |
CommandPointTM Admin V4.4.0 |
ptx/PDC V1.2.0 |
CommandPoint Clusters V2.1.1 |
ptx/RAID V2.0.5 |
CommandPoint for Unicenter TNG V1.0.0 |
ptx/SDI V2.0.0 |
CommandPoint SVM V2.1.0 |
ptx/SESMON V1.0.1 |
DYNIX/ptx V4.4.7 |
ptx/SNA 3270 V4.5.0 |
edb Debugger V3.3.6 |
ptx/SNA APPC V4.5.0 |
Encryption Software V4.4.7 |
ptx/SNA LU0 API V4.5.0 |
MQSeriesTM for DYNIX/ptx V1.1.0 |
ptx/SNA LU6.2 V4.5.0 |
ptx/AGENT V1.3.2 |
ptx/SNA PU2.1 Base Server V4.5.0 |
ptx/ATM V2.0.1 |
ptx/SNA RJE (3770) V4.5.0 |
ptx/BaseComms V1.1.2 |
ptx/SNA SDLC & LLCI V4.5.0 |
ptx/C++ V5.2.2 |
ptx/SNA TN3270 Client V4.5.0 |
ptx/CFS V1.0.4 |
ptx/SNA TN3270 Server V4.5.0 |
ptx/Channel Attach V1.0.1 |
ptx/SPDRIVERS V2.3.0 |
ptx/CLUSTERS V2.1.3 |
ptx/SVM V2.1.3 |
ptx/CTC V1.1.2 |
ptx/SYNC V4.4.2 |
ptx/EES V1.0.1 |
ptx/TCP/IP V4.5.3 |
ptx/EFS V1.3.6 |
ptx/X.25 V4.4.1 |
ptx/ITX V4.4.0 |
ptx/XWM V4.5.0 |
ptx/JSE V1.1.2, V1.2.1 |
ptx/XWM Contributed V4.5.0 |
ptx/LAN V4.6.2 |
Public Software V4.4.7 |
ptx/LICENSE V1.1.0 |
SequentLINKTM V4.3.2 |
NUMA-Q® |
Symmetry® |
Fibre Channel Bridge V1.5.3 |
CSM V1.6.1 |
Fibre Channel Switch V1.6.c3 or V2.0.3a |
QCIC V3.4.1 |
Fibre Channel Host Adapter FF2.30 or SF2.22 |
SSM/VBAD V4.9.2 |
NUMA-Q Online Diagnostics V2.6.0a |
ptx/Online Diagnostics V1.4.1 |
a. The NUMA-Q Online Diagnostics Dispatcher software is now located on the DYNIX/ptx V4.4.7 and Layered Products CD. The console portion of the software remains on the NUMA-Q Console Software CD. |
New systems are shipped with the following software and firmware already installed. You do not need to reinstall this software.
Software |
Firmware |
DYNIX/ptx |
Fibre Channel Bridge (NUMA-Q) |
ptx/BaseComms |
Fibre Channel Host Adapter (NUMA-Q) |
ptx/LAN |
Fibre Channel Switch (NUMA-Q with switch) |
ptx/TCP/IP |
CSM (Symmetry) |
SequentLINK |
QCIC (Symmetry) |
To complete the installation, perform the following steps:
ATTENTION Before the upgrade to DYNIX/ptx V4.4.7, a patch to prevent device name slippage must be installed on NUMA-Q systems running DYNIX/ptx V4.4.2 with a patch level earlier than Issue 7. See "Install Device Naming Patch on NUMA-Q Systems" later in this chapter, for more information.
Rolling upgrades of clustered systems can be performed only if both nodes of the cluster are currently running either DYNIX/ptx V4.4.2, V4.4.4, V4.4.5, or V4.4.6 and the corresponding layered products and firmware. If the nodes are running earlier versions of software, they must be upgraded one-at-a-time.
Chapter 11 describes how to perform a rolling upgrade on a Symmetry 5000 cluster.
Rolling upgrades for NUMA-Q clusters can be performed only by Customer Support personnel. Contact your service representative for assistance.
[ ] | NUMA-Q only: If your system is currently running DYNIX/ptx V4.4.2 with a patch level earlier than Issue 7, you must install fast patch 243144, which prevents device name slippage. This patch must be installed before upgrading the operating system. See "Install Device Naming Patch on NUMA-Q Systems" later in this chapter.
| ||
[ ] | Gather the materials needed for the installation. See "Installation Materials" later in this chapter. | ||
[ ] | Gather current information about your system. See "Obtain System Information" later in this chapter. | ||
[ ] | Determine the software products that need to be installed. See "Upgrade Notes" later in this chapter. Also review the later section "Software Dependencies," which lists layered products that require the installation of other products. | ||
[ ] | Verify that your system meets the requirements for running DYNIX/ptx V4.4.7. See "System Requirements" in Chapter 2. Also review "Operational Restrictions" in Chapter 2. | ||
[ ] | If your system includes an EMC disk storage subsystem, verify that it is running the correct version of the EMC firmware. See "Requirements for EMC Disk Subsystems" in Chapter 2. | ||
[ ] | Back up your current software. See "Back Up System Files and Configuration Information" in Chapter 2. | ||
[ ] | Gather your license key information for those software products that require licensing. See "Software Licensing" in Chapter 2. | ||
[ ] | Deinstall any unsupported software. See "Deinstall Unsupported Software" in Chapter 2. | ||
[ ] | Perform pre-installation tasks for the products that you will be installing. Be sure to complete the steps in the section for ptx/TCP/IP. See "Product-Specific Pre-Installation Information" in Chapter 2. | ||
[ ] | Determine the type of installation you will be performing and plan your installation strategy. If you are not familiar with the installation types, see Chapter 3. |
[ ] | Install the new software. Select one of these options:
|
[ ] | Review the installation log file and resolve any errors. Output from the installation is written to the screen and to the log file/usr/options/<product>/progress_log.<installation_date-time>. This log file is placed on the target installation disk when the installation is complete. | ||
[ ] | During the installation, ptx/INSTALL will attempt to update the /etc/vfstab file on the target disk to point to the new root disk. If it is unable to do so, it will write a warning message to the screen and to the log file. If you see this message, be sure to update the /installmnt/etc/vfstab file manually on the target disk. | ||
[ ] | Modify the /etc/inetd.conf file if necessary. See "ptx/TCP/IP" in the section "Product-Specific Tasks" in Chapter 13. | ||
[ ] | Resolve file conflicts if you have not done so already. See Appendix B. | ||
[ ] | If auditing is enabled on your system, ensure that the root account has a password and that at least one other user account exists and has a password.
| ||
[ ] | If you broke a ptx/SVM mirror and installed on a plex, return the device where the installation was performed to the rootdg. See "Prepare to Reboot the System" in Chapter 4 for NUMA-Q or Chapter 5 for Symmetry. | ||
[ ] | NUMA-Q only: If you need to install the console software, shut down the operating system and install and flash the software, including the stand-alone kernel (sak.dat) and bootstrap program (ptxldr.elf), from the NUMA-Q Console software CD-ROM. See the NUMA-Q Console Software Release Notes.
| ||
[ ] | Symmetry only: If system firmware was installed, shut down the operating system to monitor Level B and download the firmware. For CSM, see the CSM Software Release Notes; for QCIC, see the QCIC Software Release Notes; for SSM, see the SSM/VBAD Software Release Notes. | ||
[ ] | Symmetry only: If you booted from the distribution CD-ROM, reset the loaderPath and lvlBPath to point to your boot disk. This step must be done from monitor Level-B. The following example assumes that /usr/ssw is located on qd0s0. ---> bh loaderPath=qd(0,0)usr/ssw/boot | ||
[ ] | Reboot the operating system.
| ||
[ ] | Perform a ROOT installation of any remaining layered products. See Chapter 8. Review the installation log files to resolve any errors. | ||
[ ] | Build the kernel and reboot the operating system. See Chapter 12, "Build a Custom Kernel." | ||
[ ] | NUMA-Q only: If you installed the Fibre Channel Switch, Bridge, or Host Adapter software, download it as described in the Fibre Channel Software Release Notes.
| ||
[ ] | Remove installation directories that are no longer needed. See "Remove Unneeded Installation Directories" in Chapter 13. | ||
[ ] | For installations on an alternate disk, sync files between the original root disk and the alternate disk. (This step is optional. It locates files on the original root disk that were changed after the image of the root filesystem was copied to the alternate disk.) See "Sync Files Between the Original Root Disk and the Alternate Disk" in Chapter 13. | ||
[ ] | Complete other post-installation steps as described under "Product-Specific Tasks" in Chapter 13. | ||
[ ] | Create a custom miniroot for your system. See "Create a Custom Miniroot" in Chapter 13. Also see Chapter 1 in the DYNIX/ptx System Recovery and Troubleshooting Guide. | ||
[ ] | If you installed on a mirrored plex, reestablish the mirror of the root volume. See "Mirror the Original Root Partition to the Upgraded Root Volume," Chapter 4 for NUMA-Q or Chapter 5 for Symmetry. |
ATTENTION If you have installed either the "Software Patches Issue 7" or "Software Patches Issue 8" CD, you do not need to install fast patch 243144. This fast patch is included in the DYNIX/ptx V4.4.2.5 patch provided with the Issue 7 and Issue 8 CDs.
Before upgrading a NUMA-Q system from DYNIX/ptx V4.4.2 to DYNIX/ptx V4.4.7, you must install fast patch 243144 on your system. This patch prevents device name slippage. If this patch is not installed, devices on the PCI bus can be assigned the wrong name when the system is booted after the upgrade to V4.4.7. You may then see messages such as device not found when the system attempts to access an expected device name.
When the patch is installed, it determines the existing names of all PCI devices. When the system is then booted on the new kernel, a script will run that matches the PCI devices with their correct names. This script is run only once-during the boot following the installation of the patch. Device names will be assigned correctly on subsequent reboots.
To ensure that the patch works correctly, be sure that all devices have permanent names before the patch is installed. Also, do not rename any devices between the time that you install the patch and when you reboot the kernel.
This patch must be installed on both nodes of a clustered system.
The device naming fast patch is on the CD-ROM labeled "Patch for Upgrading from DYNIX/ptx V4.4.2." To install the fast patch, complete the following steps:
Use the su command or log in as root to become superuser.
Insert the CD-ROM into the CD-ROM drive.
Go to the /usr/options directory:
# cd /usr/options
Load the fast patch from the CD-ROM:
# devbuild vtoc /dev/rdsk/cd0
# mount -r -F ufs /dev/dsk/cd0s0 /mnt
# tar -xf /mnt/v4.4.2/FP#243144.tar
# umount /mnt
# devdestroy /dev/rdsk/cd0
This step creates a subdirectory named FP#243144.999999 in the /usr/options directory. This subdirectory contains the fast patch and a README file. Be sure to review the information in the file before installing the patch.
Go to the fast patch subdirectory and issue the installpatch command to install the fast patch:
# cd FP#243144.999999
# ./installpatch
Compile the kernel with the ptx/ADMIN menu system. Use System Administration -> Kernel Configuration.
Reboot the operating system on the new kernel.
# init 6
After you have installed the patch, compiled the kernel, and rebooted, you can proceed with the DYNIX/ptx V4.4.6 upgrade.
The following CD-ROMs are needed for the installation:
Patch for Upgrading from DYNIX/ptx V4.4.2 (for NUMA-Q upgrades from DYNIX/ptx V4.4.2 only)
DYNIX/ptx V4.4.7 OS and LP Software, 08/00, Revision B (either US or International)
Systems Mgmt Software (for DYNIX/ptx V4.4.4 to V4.4.x), 12/99, Revision F (optional, contains CommandPoint products)
NUMA-Q Console V1.7.1 Software, 12/99, Revision A
In addition to these release notes, you will also need the following documents:
NUMA-Q Console Software Release Notes, 12/99 (NUMA-Q systems only)
DYNIX/ptx V4.4.x Fibre Channel Software Release Notes, 08/00 (NUMA-Q systems only)
CSM Software V1.6.1 Release Notes (if upgrading CSM software on Symmetry systems)
QCIC Software V3.4.1 Release Notes (if upgrading QCIC software on Symmetry systems)
SSM/VBAD Software V4.9.2 Release Notes (if upgrading SSM/VBAD software on Symmetry systems)
You may also need to refer to layered product release notes for configuration information.
Gather the following information about your system:
Currently installed software and firmware. Check /etc/versionlog or use the ptx/ADMIN "List Software Packages" option (select System Administration -> Software Management -> List Software Packages).
Whether auditing is enabled. Run the audit command with no options.
The kernel environment type. Check the value of the environment directive in the file /etc/conf/uts/symmetry/unix.<kernel_name>.
The current root partition. Run the /etc/bootflags command and check the setting for the n0 string.
On NUMA-Q systems, the Emulex version of the Fibre Channel 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. If your system has Emulex version 3 Host Adapters, install Fibre Channel Host Adapter software version FF2.30. If you have Emulex version 4 Host Adapters, install version SF2.22.
DYNIX/ptx must be upgraded to V4.4.7. If the following software and firmware products are installed on your system, update them with the new versions:
Encryption |
ptx/C++ |
ptx/NFS |
FC Bridge (NUMA-Q) |
ptx/CFS |
ptx/RAID |
FC Host Adapter (NUMA-Q) |
ptx/ChannelAttach |
ptx/SESMON |
FC Switch (NUMA-Q) |
ptx/CLUSTERS |
ptx/SVM |
ptx/ATM |
ptx/EFS |
ptx/TCP/IP |
ptx/BaseComms |
ptx/LAN |
SequentLINK |
If your system contains earlier versions of the following products, also upgrade them to these versions:
CP Clusters V2.1.1 |
QCIC V3.4.1 (Symmetry) |
For NUMA-Q systems, the console software must be upgraded.
DYNIX/ptx must be upgraded to V4.4.7. If the following products are installed on your system, update them with the new versions:
CP Clusters |
ptx/C++ |
ptx/RAID |
Encryption |
ptx/CFS |
ptx/SESMON |
FC Bridge (NUMA-Q) |
ptx/ChannelAttach |
ptx/SVM |
FC Host Adapter (NUMA-Q) |
ptx/CLUSTERS |
ptx/TCP/IP |
FC Switch (NUMA-Q) |
ptx/EFS |
QCIC (Symmetry) |
ptx/ATM |
ptx/LAN |
SequentLINK |
ptx/BaseComms |
ptx/NFS |
For NUMA-Q systems, the console software must be upgraded.
DYNIX/ptx must be upgraded to V4.4.7. If the following products are installed on your system, update them with the new versions:
CP Clusters |
ptx/C++ |
ptx/SESMON |
Encryption |
ptx/CFS |
ptx/RAID |
FC Bridge (NUMA-Q) |
ptx/CLUSTERS |
ptx/SPDRIVERS |
FC Host Adapter (NUMA-Q) |
ptx/EFS |
ptx/SVM |
FC Switch (NUMA-Q) |
ptx/JSE |
ptx/TCP/IP |
ptx/AGENT |
ptx/LAN |
ptx/WINDOWS |
ptx/ATM |
ptx/NFS |
QCIC (Symmetry) |
ptx/BaseComms |
ptx/PDC |
SequentLINK |
For NUMA-Q systems, the console software must be upgraded.
Note than the name of the ptx/WINDOWS product has been changed to ptx/XWM.
DYNIX/ptx must be updated to V4.4.7. If the following products are installed on your system, update them with the new versions:
Encryption |
ptx/CLUSTERS |
ptx/SNA |
FC Bridge (NUMA-Q) |
ptx/CTC |
ptx/SPDRIVERS |
FC Host Adapter (NUMA-Q) |
ptx/EES |
ptx/SVM |
FC Switch (NUMA-Q) |
ptx/EFS |
ptx/SYNC |
ptx/AGENT |
ptx/JSE |
ptx/TCP/IP |
ptx/ATM |
ptx/LAN |
ptx/WINDOWS |
ptx/BaseComms |
ptx/NFS |
ptx/X.25 |
ptx/C++ |
ptx/PDC |
QCIC (Symmetry) |
ptx/CFS |
ptx/RAID |
SequentLINK |
For NUMA-Q systems, the console software must be updated.
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.
The name of the ptx/WINDOWS product has been changed to ptx/XWM.
Symmetry systems running DYNIX/ptx V4.2.3 or V4.2.4 can update to V4.4.6. The operating system and all layered products must be updated.
Some products contain configuration changes that must be addressed either during the delta installation process or immediately afterward to ensure a smooth conversion to the new software. In most cases, the configuration changes are handled automatically and invisibly by the software update process and require no user intervention.
However, ptx/SVM and ptx/CLUSTERS have conversion issues that must be addressed; these issues are discussed under "Product-Specific Information" in Chapter 2. For information about modifying your ptx/CTC configuration after the software has been updated, see Chapter 13, "After the Installation."
ptx/INSTALL provides several enhancements that were not available with the previous ptx/ADMIN installation procedure:
Multiple products can be installed at the same time. The products can be both new installations and updates to existing products.
Disk space requirements are checked automatically. If necessary, you can halt the installation, free up the necessary disk space, and resume the installation.
Software compatibility is checked. ptx/INSTALL determines whether the products currently on the system are compatible with the products being installed. When a product requires that another product be installed, ptx/INSTALL also verifies that the required product has been selected for installation.
ptx/INSTALL can compile the default kernel during the installation. If you want to use a custom kernel, you must compile it after the installation is complete.
The INIT ALT DISK DELTA and ROOT procedures are the only supported installation methods for S2000 systems.
If you are updating to DYNIX/ptx V4.4.7 from a version earlier than V4.4, you must first install and boot DYNIX/ptx V4.2. You may also need to replace the disk that will be used for the V4.4.7 installation. See Appendix C for installation information.
If your system is currently running DYNIX/ptx V4.4.x and you have only one wd disk, you must reinstall V4.2 on a qd disk and then do an INIT ALT DISK DELTA update to V4.4.7, as described in Appendix C.
Most layered products require that DYNIX/ptx V4.4.7 be installed on your system. Certain layered products also require that other layered products be installed. Table 1-9 lists those dependencies.
When you select a product for installation, ptx/INSTALL verifies that other products required by that product have also been selected for installation. It also determines whether the products currently on the system are compatible with the products being installed.
Layered Product |
Dependencies |
CommandPoint Admin |
ptx/Base_Comms, ptx/LAN, ptx/TCP/IP, ptx/JSE, ptx/XWM |
CommandPoint Clusters |
ptx/Base_Comms, ptx/LAN, ptx/TCP/IP, ptx/CLUSTERS, ptx/CTC |
CommandPoint SVM |
ptx/Base_Comms, ptx/LAN, ptx/TCP/IP, ptx/JSE, ptx/SVM, ptx/XWM |
MQ Series for DYNIX/ptx |
ptx/Base_Comms, ptx/LAN, ptx/TCP/IP |
ptx/AGENT |
ptx/Base_Comms, ptx/LAN, ptx/TCP/IP |
ptx/ATM |
ptx/Base_Comms/ ptx/LAN, ptx/TCP/IP, ptx/EES |
ptx/CFS |
ptx/Base_Comms, ptx/LAN, ptx/TCP/IP, ptx/EFS, ptx/CLUSTERS |
ptx/Channel Attach |
ptx/Base_Comms, ptx/LAN, ptx/TCP/IP |
ptx/CLUSTERS |
ptx/Base_Comms, ptx/LAN, ptx/TCP/IP |
ptx/CTC |
ptx/Base_Comms, ptx/LAN, ptx/TCP/IP, ptx/CLUSTERS |
ptx/EES |
ptx/Base_Comms, ptx/LAN, ptx/TCP/IP |
ptx/ITX |
ptx/Base_Comms, ptx/LAN, ptx/TCP/IP, ptx/SYNC, ptx/X.25 |
ptx/JSE |
ptx/Base_Comms, ptx/LAN, ptx/TCP/IP, ptx/XWM |
ptx/LAN |
ptx/Base_Comms |
ptx/LICENSE |
ptx/Base_Comms, ptx/LAN, ptx/TCP/IP |
ptx/NFS |
ptx/Base_Comms, ptx/LAN, ptx/TCP/IP |
ptx/OSI Transport Services |
ptx/Base_Comms, ptx/LAN |
ptx/PDC |
ptx/Base_Comms, ptx/LAN, ptx/TCP/IP |
ptx/SDI |
ptx/Base_Comms, ptx/LAN, ptx/TCP/IP |
ptx/SNA 3270 Terminal Emulator |
ptx/Base_Comms, ptx/LAN, ptx/TCP/IP, ptx/XWM |
ptx/SNA APPC |
ptx/Base_Comms, ptx/LAN, ptx/TCP/IP |
ptx/SNA LU6.2 |
ptx/Base_Comms, ptx/LAN, ptx/TCP/IP |
ptx/SNA PU2.1 Base Server |
ptx/Base_Comms, ptx/SYNC and/or ptx/LAN |
ptx/SNA RJE (3770) |
ptx/Base_Comms, ptx/LAN, ptx/TCP/IP |
ptx/SNA SDLC & LLCI |
ptx/Base_Comms, ptx/SYNC and/or ptx/LAN |
ptx/TCP/IP |
ptx/Base_Comms, ptx/LAN |
ptx/XWM |
ptx/Base_Comms, ptx/LAN, ptx/TCP/IP |
ptx/XWM Contributed |
ptx/Base_Comms, ptx/LAN, ptx/TCP/IP, ptx/XWM |
ptx/X.25 |
ptx/Base_Comms, ptx/LAN, ptx/SYNC |