This procedure must be used if your system is currently running ptx/SVM V2.x and you want to upgrade DYNIX/ptx and/or layered products on an alternate disk. Be sure to review the entire procedure before you begin the upgrade.
You should be aware of the following before starting the upgrade:
If you are upgrading from DYNIX/ptx V4.4.x, the "Software Patches for Upgrading from DYNIX/ptx V4.4.x to V4.5.x/V4.6.x" CD must be installed before the upgrade to V4.6.0. Consult the README file on the CD for more information.
If /var/ees is created as a separate filesystem, it must not be under SVM control.
/usr/ssw cannot be a separate filesystem.
For NUMA-Q systems having a single bootbay, you must perform the installation on another partition of the current root disk. See "Requirements for NUMA-Q Systems with a Single Bootbay" in Chapter 3 for more information.
Be sure to delete any unsupported products before starting the installation. See Table 2-3, "Software to Deinstall."
Following is a summary of the upgrade procedure. The "Upgrade Checklist" in Chapter 1 and this chapter contain detailed information for each step.
Perform the pre-installation tasks described in Part 1 of the "Upgrade Checklist" in Chapter 1. Be sure to back up the root filesystem and record the system bootflags.
Break the ptx/SVM mirror of the root volume. (If the root volume is not mirrored, you will need to create a mirror.) See "Prepare for the Installation" in this chapter.
ATTENTION If you need to increase the size of the root partition, follow the instructions in Appendix C instead of using the "Prepare for the Installation" section.
Install the new software. See "Install Software With the ALT DISK DELTA Procedure" in this chapter. Build the kernel, but do not have ptx/INSTALL reboot the system.
Complete the installation as described in Part 3 of the "Upgrade Checklist" in Chapter 1. Be sure to complete the following tasks before you reboot the system:
Follow the remaining steps in "Part 3: Complete the Installation" of the upgrade checklist in Chapter 1.
When you have completed the installation and have rebooted the system, reestablish the mirror. See "Mirror the Original Root Partition to the Upgraded Root Volume" in this chapter.
ATTENTION If you need to increase the size of the root partition, follow the instructions in Appendix C instead of using the information in this section.
Complete the following steps to prepare your system for the installation:
If your root volume is not mirrored, create a mirror on another partition. The partition must be on a local bus, be the same size as the original root plex, and be type 8. This partition will be used as the alternate disk partition during the software installation. Use the procedure appropriate for your system configuration. In the examples, the mirror is created on partition sd3s0.
Systems having the original root partition and the alternate disk partition on separate disks.
NUMA-Q 1000 systems having the original root partition and the alternate disk partition on the same disk. In the first vxmake command, the len you specify must match the length of the original root partition.
# vxdg adddisk sd0s1
# vxmake sd sd0s1-01 disk=sd0s1 offset=0 len=5120000
# vxmake plex ROOTVOL-01 sd=sd0s1-01
# vxplex att ROOTVOL ROOTVOL-01
These procedures can take several minutes. The following message may appear; it can be ignored.
vxbootsetup: NOTE: Root file system is not defined on a volume.
Determine the location of the current root partition and the partition that will be used for the alternate disk installation. The alternate disk partition must be a mirror of the root volume. It cannot be the partition from which the system is currently booted.
To determine the current root partition, enter the following command.
# bfget -r
root_dev=sd0s0:0:0
ATTENTION bfget reports the current bootflag setting for the boot disk. If the installation fails and is restarted, the bootflag may have already been reset to the alternate disk.
To determine the partition to be used for the alternate disk installation, enter the following command.
# vxprint -ht -g rootdg ROOTVOL
Select the plex that is not associated with the boot disk.
Disassociate the selected mirrored plex from the root volume. Before performing this step, ensure that your system is as idle as possible to avoid filesystem corruption on the alternate disk. (Later in this procedure, you will run fsck to verify the integrity of that filesystem.)
# sync; sync; vxplex dis ROOTVOL-sd3s0
Remove the plex and subdisk from the rootdg's records:
# vxedit -r rm ROOTVOL-sd3s0
Remove the disk media record from the rootdg.
# vxdg rmdisk sd3s0
ATTENTION If you should need to reboot the system after this point, you must boot on your current boot device, not on the new alternate disk. This may require changing your current boot flags to match those recorded earlier. (You cannot boot from the alternate disk until you have completed step 3 in the later section "Prepare to Reboot the System.")
Check the integrity of the filesystem on the newly detached device. If you are using an EFS filesystem, include the -F efs option.
ATTENTION If the device has not previously been devbuilt, run the devbuild vtoc <device_name> command on the device before invoking fsck.
# fsck -y /dev/rdsk/sd3s0
Mount the partition to be used for the install as /mnt. If you are using an EFS filesystem, include the -F efs option.
# /etc/mount /dev/dsk/sd3s0 /mnt
Perform the installation as described in the next section, "Install Software with the ALT DISK DELTA Procedure." Build the default kernel, but do not have ptx/INSTALL reboot the system.
When performing the installation, be sure to specify the alternate disk partition you set up earlier (for example, /dev/dsk/sd3s0) as the alternate disk.
You can install both operating system CDs (Volumes 1 and 2) with the ALT DISK DELTA procedure. You need to compile the kernel only after the Volume 1 installation. Do not have ptx/INSTALL reboot on the new kernel.
ATTENTION The SequentLINK and NUMA-Q Online Diagnostics products cannot be installed with the ALT DISK DELTA procedure. Use the ROOT procedure to install these products after updating the base operating system.
To install software packages, use the following procedure. You must be root to perform the installation.
Insert the distribution CD into the CD drive.
Set the TERM type so that ptx/ADMIN will work properly:
# TERM=vu320; export TERM
# stty -tabs
Issue the menu command to start ptx/ADMIN; then go to the Software Management Menu.
Use System Administration -> Software Management
c1admapp Software Management _______________________________________________________ A Install Software Package F View/Edit Preview Log B Remove Software Package G Update Man Page Databases C List Software Packages H Change Installation Disk D Check Package Consistency I Alternate Disk Compare E List Software Packages Available on Installation Distribution
If you want to check the contents of the CD, select the "List Software Packages Available on Installation Distribution" option.
Select the Install Software Package option.
Specify the installation source, which can be either CD-ROM, nfs, or directory.
Installation Source Type Enter installation source type ___________
Specify the location of the installation source on the screen that appears next:
If the source is CD-ROM, enter the name of the CD-ROM device, such as cd0.
If the source is nfs, specify the remote host and directory containing the software. For example, if you are installing software from a CD-ROM on a remote machine, specify the mount point of the cd device as the directory.
If the source is directory, specify the pathname to the directory.
On the Installation Type window, select the ALT DISK DELTA installation type.
Installation Type Installation Type Description ________________________________________________________________________ ROOT Install on current root, /usr partitions # ALT DISK DELTA Install on mounted alternate root partition INIT ALT DISK DELTA Make copies of current partitions and install on it SCRATCH Initial install on alternate disk #
The Change Installation Disk form will ask you to specify the root partition on the alternate disk (for example, /dev/dsk/sd3s0). The disk containing the partition is considered to be the installation disk for the Software Management menu options listed on the form.
ATTENTION If you are installing on a NUMA-Q system with a single boot bay, you must specify a partition (typically either 0 or 2) on the current root disk. If the root filesystem is currently on partition 0, specify partition 2 as the alternate disk partition, and vice versa.
Change Installation Disk Enter root partition on alternate disk _______ (use the form /dev/dsk/sd0s0). If the corresponding /usr directory is on a separate partition, that partition must be mounted before using this form. The alternate-disk mountpoint must be in the root directory (/mnt is valid; /a/mnt is not). The current installation root disk is disk_name The installation disk value affects these menu selections: Install SW Pkg, Remove SW Pkg, List SW Pkg, Check SW Pkg, and View/Edit Preview Log. The installation disk value stays in effect until changed.
If the CD contains a version of ptx/INSTALL that is newer than the version currently on your system, the new version will be installed automatically.
If you want to install only products that provide C2-level security, answer y on the following screen.
C2-Certifiable Product Installation Install only those products which N are C2-Certifiable? (Y/N) Enter 'Y' to install only products which are C2-Certifiable
Select the software packages to be installed from the window that appears next. You can select multiple packages. The packages can be both new installations and updates to existing products. Following is an example of this window.
Select one or more software packages to install/update Part Number Name Description Version _________________________________________________________________ 1003-xxxxx-xx base DYNIX/ptx(R) Base V4.6.0 # U 1003-xxxxx-xx base_comms ptx/BaseComms V1.2.0 N 1003-xxxxx-xx nfs ptx/NFS V4.7.0
If the distribution CD contains a version of a product that is newer than the version currently installed on your system, that product will be marked with a U to indicate that you should upgrade the product.
Certain software products require that you enter a license key into the system nodelock file before the product can be installed. If the license key has already been entered, the letter L will precede the entry for that package in the Select Software Packages window. If the license key has not been entered, the letter N will appear. License keys are not required for packages that do not specify one of these letters.
ATTENTION If you selected several products that require licenses, it might take a few minutes for the next installation screen to appear.
If you have selected a software package that requires a license password but you have not yet entered the password into the system nodelock file, a window listing the name of the product will be displayed. Select either "enter the license for that product" or "deselect the product."
If you choose to enter the license password, the following form will be displayed. You must enter the license password, the expiration date, and the license checksum. The other values will be filled in for you. (The license information for the products you have purchased is located in the license folder shipped with your software.)
Add Installation License Enter the product name ________ Enter the product version ________ Enter the node ID ________ Enter the vendor ID ________ Enter the license password ________ Enter the expiration date ________ Enter the license checksum ________
The license entries you specify are added to the system nodelock file, /var/netls/nodelock.
Some software products are automatically installed when you select another product. For example, if you are installing the base operating system, products such as ptx/BaseComms and ptx/edb will automatically be installed. If you did not select the automatically installed products on the software selection screen, ptx/INSTALL will now display a list of products to be installed. The list includes both the products you selected and products that are automatically installed. The letter A precedes the automatically installed products. At this point, you can deselect any unwanted products. (This screen does not appear if you selected the automatically installed products on the software selection screen.)
Confirm: Products to be installed Part Number Name Description Version _______________________________________________________________________ 1003-xxxxx-xx base DYNIX/ptx(R) Base V4.6.0 # A 1003-xxxxx-xx base_comms ptx/BaseComms V1.2.0 1003-xxxxx-xx nfs ptx/NFS V4.7.0 A = automatically included. Please deselect unwanted product
ptx/INSTALL now 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. If certain products are not compatible or if required products have not been selected, the following form will appear. You can either reselect products or abort the installation.
Compatibility Error View compatibility errors? (Y/N) _ Enter 'Y' to display the product incompatibilities identified. You can then reselect products to install and continue the installation. Answer 'N' to abort installation
ptx/INSTALL requires additional information to install certain layered products. At this point, you will be asked for that information. For example, a product might include optional components; you will need to specify whether you want to install those components. Most of these screens are self-explanatory.
If you are installing ptx/LICENSE, refer to the ptx/LICENSE Release Notes for a description of the installation and configuration screens that appear. In particular, do not configure ptx/LICENSE if ptx/TCP/IP is not already configured for networking on your system.
ptx/INSTALL now verifies that there is adequate filesystem space to install the selected products.
ATTENTION The installation will require approximately 150 MB of disk space in addition to the amount calculated by ptx/INSTALL.
If there is not enough space, ptx/INSTALL halts the installation and displays the following form. Enter Y at the prompt to review the problems found.
Disk Space Error View info on disk space insufficiencies? ___ Enter 'Y' to display products whose disk space requirements will not be met. Enter 'N' to abort the installation. You may restart the installation once the disk space requirements for all selected products have been resolved.
When adequate disk space is available, you can resume the installation by selecting the Install Software Package option from the Software Management menu.
ptx/INSTALL now creates a preview log for each product to be installed. The preview log specifies whether file conflicts exist for the product. File conflicts can occur when the version of a file currently on the system differs from the original file, from the version of the file on the CD, or from both. You will need to resolve certain file conflicts manually. You can either halt the installation and resolve those file conflicts now, or continue with the installation and resolve the conflicts after the software is installed.
Appendix B lists file conflicts that may occur for DYNIX/ptx and ptx/TCP/IP. Be sure to review this information to help you determine whether you want to resolve file conflicts now or after the installation is complete.
Conflict File Resolution Resolve files in conflict now? (Y/N) __ Enter 'Y' to preload conflict files and temporarily exit to view preview logs and resolve files in conflict. Enter 'N' to continue with installation, and resolve files in conflict after the installation is completed.
To resolve any conflicts after the installation is complete, answer N on the form. The installation will continue as specified in the preview logs for the selected products and the old files will be moved to the <product_name>/oldfiles directories.
To resolve the conflicts now, answer Y on the form. The files in conflict will then be preloaded and the installation will exit. To locate file conflicts, use the View/Edit Preview Logs menu option from the Software Management menu to examine the preview logs. For details about the preview logs and resolving conflicts, refer to Appendix B.
If conflicts were found, the following form will specify where the files in conflict will be preloaded. You can change the locations for preloading new conflict files and saving the currently installed version (the old version) of conflict files.
The default locations for new and old versions of conflict files are /usr/options/<product>/newfiles.<installation_date-time> and /usr/options/<product>/oldfiles.<installation_date-time>.
Conflict File Parent Directories Enter the parent directory for ____________ preloading new versions of files in conflict (For each product selected, a subdirectory of the form 'PRODUCT_NAME/ newfiles.<installation_date_time>' will be created) Enter parent directory for saving ____________ old versions of files in conflict (For each product selected, a subdirectory of the form 'PRODUCT_NAME/ oldfiles.<installation_date_time>' will be created)
If you exited the installation to resolve conflicts, you can resume the installation by selecting the Install Software Package option from the Software Management menu.
ptx/INSTALL now determines whether the kernel needs to be recompiled after the installation is complete. Typically, this is needed only when the products to be installed contain kernel components. You can override the value specified on the form.
We recommend that you answer Y to compile the kernel after installing the operating system Volume 1 CD. ptx/INSTALL will then build a default kernel that includes the layered products you have installed. This kernel is needed to boot the operating system properly. You do not need to compile the kernel after installing the Volume 2 CD; the products on this CD do not contain kernel components.
The default kernel will not include any local kernel modifications that you have made. After booting the system, you can build your custom kernel and then reboot with that kernel.
If your system is currently running DYNIX/ptx V4.6, enter Y at the prompt Use currently running kernel build parameters? to use the current kernel build parameters, environment type, and audit configuration type when the kernel is built. (You will not need to specify these values on the next screen.) If you are upgrading from a version earlier than V4.6, answer N at the prompt and then enter the appropriate values on the next screen.
Configure and compile a kernel with default parameters Configure and compile a default kernel ____ following installation? (Y/N) Use currently running kernel ____ build parameters? (Y/N)
If you chose to have ptx/INSTALL compile the default kernel, the following form appears. The name you specify at the first prompt cannot be std, mfg, or mod.
Configure a kernel with default parameters Enter a unique name to associate with default this kernel and all its associated configuration files Choose a kernel environment type ___ T for TIMESHARE P for PARALLEL C for COMMERCIAL Configure for audit? (Y/N) ___ Enter a short description of this kernel _______ The starting machine type _______ The starting architecture type _______ The starting configuration type _______
If the following items apply to your installation, the Crosstools Source Type form shown next will appear: you have installed the base operating system on an alternate disk; you are now installing a layered product from another CD on the alternate disk; the layered product includes kernel components but the CD it is on does not include the V4.6.0 kernel compilation tools; you specified that the default kernel should be compiled.
Crosstools Source Type
Enter crosstools source type ______
Supported types: CD-ROM, nfs, directory, or NONE
(crosstools source only)
Because the tools needed to compile the V4.6.0 kernel are not available, the form allows you to specify an alternate source for the tools. If you have another CD-ROM drive, insert the CD containing DYNIX/ptx V4.6.0 into that drive and enter CD-ROM as the crosstools source type on the form. You will then be asked to specify the name of the CD device, such as cd1.
If you do not have another CD drive, use Cancel to exit the installation; then start the installation again. The "Configure and compile a kernel with default parameters" form will be displayed. Enter N at the prompt and compile the default kernel manually when the installation is complete.
Specify whether you want to rebuild the man pages database. Rebuilding the man pages takes several minutes. You can also build the man pages at a later time using one of the methods described in the ptx/INSTALL Software Installation Guide.
ATTENTION Do not have ptx/INSTALL reboot the kernel. Enter N at the "Reboot on installation disk after installation" prompt.
Installation Options Rebuild manpages following installation? (Y/N) __ Reboot on installation disk after __ installation? (Y/N) This is the last screen for installation Entering "Run" from this screen will start the installation of files for all selected products.
ptx/INSTALL will now perform the software installation.
If the installation was performed on a shareable device and the system's Fibre Channel topology is arbitrated loop, the -t AL option must be added to the bootpath. (This is required even if the primary swap partition is on a shareable disk.)
Run the following command to determine the n0 string:
/etc/bootflags | grep ^n0
Then set the bootpath as follows:
/etc/bootflags -p -c n0="n0_string" -t AL
ATTENTION The installation procedure sets both the permanent and the temporary bootpaths to point to the new root disk. If you installed software on an alternate disk, the ptx/ADMIN Set Boot Strings and Flags menu option will not report the updated permanent bootpath until after the system is rebooted. To check the updated bootflags, use the /etc/bootflags command.
If you want to install the Volume 2 CD before rebooting the system, run the devdestroy command on the CD-ROM device and then remove the Volume 1 CD. The following example is for the cd0 device:
# /etc/devdestroy /dev/rdsk/cd0
Then use the ALT DISK DELTA procedure to install the Volume 2 CD. You do not need to run devdestroy before removing the Volume 2 CD, as it is in ISO-9660 format.
Before rebooting the system, you should create a /etc/devlabel file. (Because you have not yet booted on V4.6, create the file at /mnt/etc/devlabel.) This file contains labels that specify whether the disks on the system are node-owned or cluster-owned. The operating system uses the labels to control access to the disks.
Typically local disks can be node-owned and shareable disks can be cluster-owned. However, if a shareable disk contains the root, primary or secondary swap, or dump partitions, it must be node-owned. We recommend that all other shareable disks be labeled as cluster-owned, even on single-node systems. This labeling method will limit the number of disks that are displayed if you should need to boot with the -b option.
ATTENTION All disks must have a label. If a disk does not have a label, it cannot be opened.
On a single-node system, the /etc/devlabel file is read the first time the operating system is booted on V4.6. Local disks are labeled when the system reaches single-user mode, shareable disks are labeled when the system reaches multiuser mode. If a disk has been previously labeled with the diskown command, it will not be relabeled.
On a clustered system, /etc/devlabel is read each time you boot the system until the rolling_upgrade_complete script is run. Labeling occurs as follows: local disks are labeled when the node reaches single-user mode during the first boot of V4.6; shareable disks are labeled after you boot all nodes of the cluster to multiuser mode and run the rolling_upgrade_complete script.
After all disks have been labeled, the /etc/devlabel file will be renamed to devlabel.prev. If you should need to recreate the file at a later time, it can be executed with the /etc/labeldisks utility.
See devlabel(4) for more information about the /etc/devlabel file and the /etc/labeldisks utility.
The entries in the /etc/devlabel file have this format:
disk_name label
The disk_name is the configuration name of the disk, such as sd0. The label is either node-owned or cluster-owned. We recommend that you label shareable disks not used for root, primary swap, or dump partitions as cluster-owned even if ptx/CLUSTERS is not installed on your system.
Two special tokens ALL_UNLABELED_LOCAL and ALL_UNLABELED_SHAREABLE can be used in the file. These tokens select all unlabeled local or shareable disks and assign the corresponding label to them.
Following is a sample file:
sd0 node-owned sd1 cluster-owned sd2 node-owned ALL_UNLABELED_LOCAL node-owned ALL_UNLABELED_SHAREABLE cluster-owned
Before rebooting the system, the device where the installation was performed must be returned to the rootdg:
Unmount the alternate disk partition.
# umount /mnt
Reinitialize the private area for the new boot partition:
ATTENTION Skip this step for a NUMA-Q system with a single boot disk in the bootbay. This step needs to be done only when the alternate partition is on another disk.
# vxdisk -f init sd3s0
Add the boot partition as a media record in the rootdg:
# vxdg adddisk sd3s0
Determine the bootpath of the partition containing the newly installed software. If your system is currently booted on V4.4/V4.5, use this command:
# dumpconf -b sd3s0
If it is booted on V4.6, use this command:
# mapdev -o sd3s0
Check the bootflags. In the output from the bootflags command, the n0= value should point to the bootpath determined in the previous step.
# /etc/bootflags
If the bootpath is not correct, use the following command to change it:
# /etc/bootflags -p -c n0='bootpath'
Shut down the operating system.
#shutdown -i0 -g grace_period
If you have a new version of the console software, install it as described in the NUMA-Q Console Software Release Notes.
Reboot the operating system. You will see a message such as the following when ptx/SVM starts:
SVM starting in boot mode... Jul 9 17:21:50 vxvm:vxconfigd: Group rootdg: Duplicate virtual device number(s) : Jul 9 17:21:50 vxvm:vxconfigd: Volume ROOTVOLremapped from 121,5 to 121 ,4194302
Return to the "Upgrade Checklist" in Chapter 1 and complete the installation.
After upgrading all nodes of a clustered system and booting the nodes to multiuser mode, run the script /etc/rolling_upgrade_complete on each node. This script completes these tasks:
Takes the node out of the pre-V4.6 environment, which used the /etc/devtab file. Before running the rolling_upgrade_complete script, add any devices that are currently devbuilt to the /etc/devtab file. When you run the rolling_upgrade_complete script, the devtab file is obsoleted and the devices listed in the file are transferred to the naming database and become cluster-wide devbuilt devices.
Takes the node into the V4.6 environment. The script adds the flag set rolling_upgrade = false to the /etc/system/boot file, indicating that device labeling is now enabled on this node. Before you run the script, the flag is not present in the file and has a default value of true, which indicates that device labeling is not in effect on the node.
The script also processes the /etc/devlabel file, which assigns disk labels to disks that have not been previously labeled.
If you do not run this script, the disks cannot be labeled and you will not be able to access them.
By default, disk labels are assigned to the root and swap disks the first time the system is booted on V4.6. After booting on the V4.6 kernel, you should add a unique user-defined name and a unique comment such as "hostname root disk" to the label.
When the label includes a user-defined name, the following simple syntax can be used in the bootpath:
nm(user_defined_name)disk()
The comment enables you to easily identify the root disk if you boot with the -b option. This option lists the node-owned disks, including the comment from each disk label.
To add a user-defined name and comment to the disk label on the root disk, use the following command:
# diskown -w -N user_defined_name -C comment disk_name
The user_defined name can contain alpha, numeric, and the underscore characters only.
ATTENTION If you increased the size of the root partition, do not attempt to mirror the original ROOTVOL plex with the new ROOTVOL. The old plex is now smaller than the new ROOTVOL. You will need to install a new VTOC on the old root disk before creating the ROOTVOL mirror.
When you have completed the installation, you can reestablish the root mirror and then reboot on the original boot plex. Complete the following steps:
Remove the old root volume, which is now known as ROOTVOL%1. (If you have multiple boot partitions, this can be a number other than %1, for example ROOTVOL%2.)
Create the new half of the root mirror. The following example assumes sd0s0 was the original root partition; be sure to specify the correct name. (This name was returned by the bfget -r command in the earlier section "Prepare for the Installation.")
Systems having the original root partition and the alternate disk partition on separate disks:
# vxassist mirror ROOTVOL sd0s0
Wait for vxassist to complete before rebooting in step 4.
Systems having the original root partition and the alternate disk partition on the same disk:
# vxmake sd sd0s0-01 disk=sd0s0 offset=0 len=5120000
# vxmake plex ROOTVOL-01 sd=sd0s0-01
# vxplex att ROOTVOL ROOTVOL-01
If the following message appears, it can be ignored.
vxbootsetup: NOTE: Root file system is not defined on a volume.
Use ptx/ADMIN to set the bootflags to point to the original root disk. Be sure to specify the correct partition name.
Use System Administration -> System Setup -> Set Boot Flags and Strings
Reboot the system.
If you performed the installation on a NUMA-Q system with a single bootbay, you should break the mirror as shown in the following commands.
For other NUMA-Q systems, we strongly recommend that you mirror the root volume at all times. However, if the root volume was previously unmirrored and you want to continue with that method of operation, use the following procedure to break the mirror.
To break the mirror, enter the following commands. In the commands, plex is the plex associated with the partition that is not being used to boot the system. In the third command, specify the media record associated with that partition.
# vxplex -o norestr dis plex
# vxedit -r rm plex
# vxdg rmdisk media_record