This chapter describes how to upgrade DYNIX/ptx and/or layered products on systems that are not running ptx/SVM.
You should be aware of the following before performing 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.
/usr/ssw cannot be a separate filesystem.
If your root partition is smaller than 2 GB, you will need to expand it as described in Appendix C and then perform an ALT DISK DELTA installation.
For NUMA-Q systems with a single boot bay, you must perform an alternate disk 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.
/usr can no longer be a separate filesystem. If you currently have separate root and /usr filesystems, you must use the INIT ALT DISK DELTA installation procedure to upgrade to V4.6.0. This procedure will combine root and usr into a single root filesystem.
Choose the appropriate installation scenario:
Install on an alternate disk and copy an image of the root filesystem automatically. See "INIT ALT DISK DELTA Installation."
Install on an alternate disk and copy filesystem images manually. See "ALT DISK DELTA Installation."
Install DYNIX/ptx and layered products on the current root disk. See "ALT DISK DELTA Installation."
Install on an alternate disk and change the root filesystem to EFS, when ptx/EFS is not currently installed. See "ALT DISK DELTA Installation."
When you use these procedures, have ptx/INSTALL build the default kernel, but do not reboot.
The INIT ALT DISK DELTA procedure updates DYNIX/ptx and layered products on an alternate disk. It installs a VTOC on the alternate disk (if necessary), copies an image of the current root filesystem (and /usr if it is a separate filesystem) to the alternate disk, and then updates the specified products on that disk.
This procedure is supported only for the root and /usr filesystems; it cannot create an image of other filesystems. Products that install software in other filesystems cannot use the INIT ALT DISK DELTA procedure. See the section "INIT ALT DISK DELTA Installation Type" in Chapter 3 for a list of the affected products.
You can install only the Volume 1 operating system CD with the INIT ALT DISK DELTA procedure. Use the ALT DISK DELTA procedure to install the Volume 2 CD. You need to compile the kernel only after the Volume 1 installation. Do not have ptx/INSTALL reboot on the new kernel.
ATTENTION Do not use the INIT ALT DISK DELTA procedure to install the DYNIX/ptx V4.6.0 Layered Products Software, Volume 2 CD. Use either the ALT DISK DELTA or the ROOT procedure to install this CD.
The SequentLINK and NUMA-Q Online Diagnostics products cannot be installed with the INIT ALT DISK DELTA procedure. Use the ROOT procedure to install these products after updating the base operating system.
ATTENTION The INIT ALT DISK DELTA procedure will place an image of root and /usr on the same partition on the alternate disk. Although root and /usr may currently be on different partitions, the INIT ALT DISK DELTA copy procedure will create a single root filesystem containing your current root and /usr filesystems. When the installation is complete, there will no longer be a separate /usr filesystem.
When you use the INIT ALT DISK DELTA procedure, have ptx/INSTALL build the default kernel, but do not reboot the system.
ATTENTION Be sure to delete any unsupported products before starting the installation. See Table 2-3, "Software to Deinstall."
To install software packages, use the following procedure. You must be root to perform the installation.
Select an alternate disk. Review "Alternate Disk Requirements" in Chapter 3.
Insert the distribution CD into the CD-ROM 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 INIT ALT DISK DELTA.
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 #
Specify information about the alternate disk on the Disk Locations 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. At the prompt "Enter alternate primary swap disk and partition," specify the primary swap partition on the root disk.
At the prompts "Enter alternate root disk and partition" and "Enter alternate primary swap disk and partition," use the format /dev/dsk/sd0s0 to specify the appropriate location. The alternate root disk must contain a VTOC and the root partition must be at least 2 GB. If necessary, install a VTOC on the alternate disk:
If the disk has a standard boot VTOC and geom file and you want to use the standard VTOC, enter S at the prompt "Install a standard or custom VTOC on disk?"
If you want to install a custom VTOC, or if a standard boot VTOC and geom file are not available for the disk, enter C at the prompt. Note that this feature is available only if your system is currently running DYNIX/ptx V4.6.
ATTENTION The primary swap partition specified on the following form must be on a disk containing a VTOC. If you specify a partition on the root disk, the disk will have a VTOC. If you want to specify a swap partition on another disk that does not have a VTOC, you will need to temporarily exit the installation and assign the VTOC.
Disk Locations Enter alternate root disk and partition ______ Enter filesystem type ____ Warning: efs requires ptx/EFS, a licensed product, be installed or selected for installation on new root Should the filesystems support ACLs? _ (Y/N) Install a standard or custom VTOC on _ disk? (N/S/C; Answer N only if vtoc already exists on device) Enter alternate primary swap disk and ______ partition
If you chose to have a VTOC installed on the alternate disk, ptx/INSTALL will attempt to determine the disk type for that disk. If it is unable to locate this information, you will be asked to specify the disk type on the following form. Use SELECT to see a list of valid disk types.
Disk Type Enter type of disk _________
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.
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 product 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 products 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 Select Software Packages 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 Select Software Packages 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 will now create the temporary directories needed for the 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 interrupts 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.
ATTENTION If the alternate disk partition is the same size as the current root partition, ptx/INSTALL may incorrectly report that there is not enough room to do the install. If this message occurs, you will need to do an ALT DISK DELTA install and copy the image to the alternate disk partition manually.
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 V4.6.0 and ptx/TCP/IP V4.7.0. 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>.
The following form will specify the parent directory as /tmp/<temporary /usr/options directory>. Because the alternate disk has not yet been initialized, this temporary directory contains the /usr/options directory for the alternate disk. Later in the installation, the files will be moved to the appropriate /usr/options/<product> directory on the alternate disk.
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 build the kernel for 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.
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-ROM device, such as cd1.
If you do not have another CD-ROM 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
Do not use INIT ALT DISK DELTA to install the Volume 2 CD. Instead, use ALT DISK DELTA, or perform a ROOT install after the system is booted on V4.6.
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 /installmnt/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 the 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
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.
The ALT DISK DELTA installation procedure can be used in three different ways. Choose the method that is appropriate for your site.
Update the base operating system and layered products on an unused alternate disk partition. You must manually copy an image of the root filesystem to the alternate disk.
If you will be installing software in any other filesystems (see Chapter 3 for a list of the affected products), you must also copy an image of those filesystems to the alternate disk.
ATTENTION Be sure to use dump/restore to copy the filesystem image. Other utilities such as rdcp and dd are not aware of filesystem formats and cannot be guaranteed to copy a mounted read/write filesystem correctly.
To use this procedure, complete these steps:
Review "Alternate Disk Requirements" in Chapter 3.
Copy the filesystem images. (See "Create Filesystem Images on the Alternate Disk.")
Install software with the ALT DISK DELTA procedure. (See "Install Software with the ALT DISK DELTA Procedure.") Build the kernel but do not reboot.
Update the base operating system and layered products on the current root disk. Complete these steps:
Install on an alternate disk and change the root filesystem to EFS, when ptx/EFS is not currently installed. Complete these steps:
Review "Alternate Disk Requirements" in Chapter 3.
Be sure to delete any unsupported products before starting the installation. See Table 2-3, "Software to Deinstall."
Boot from the distribution CD and install and flash the console software. (See "Boot from the Distribution CD.")
Create EFS filesystem images. (See "Create an Image with a Different Filesystem Type.")
Install software with the ALT DISK DELTA procedure. (See "Install Software with the ALT DISK DELTA Procedure.") Build the kernel but do not reboot.
You will need to boot from the distribution CD under the following circumstances:
ptx/EFS is not currently installed on your system and you want to make the root filesystem an EFS filesystem.
You want to update DYNIX/ptx on the current root disk.
ATTENTION This procedure cannot be used if ptx/SVM is currently installed on the root disk.
To boot from the CD, complete the following steps:
Take the system to run-level 0:
# shutdown -gseconds -y -i0
Install and flash the console software, including the stand-alone kernel (sak.dat) and the bootstrap program (ptxldr.elf) as described in the NUMA-Q Console Software Release Notes.
ATTENTION The sak.dat and ptxldr.elf programs must not be installed while the operating system is running. Severe console I/O operation problems will occur if this is attempted.
Insert the distribution CD into the system CD-ROM drive.
From the CLI window, use the cd command to move to the system_name directory; then move to the boot quad_name directory. For example:
-> cd /node0/quad0
From the CLI window, set the bootpath to point to the CD-ROM device. In the following example, the CD-ROM device is at SCSI ID 4 on the PCI controller. Primary swap is on partition 1 of the disk at SCSI ID 1. The example is shown on two lines for readability.
-> bootflags bootpath "2 quad(0)pci(0)scsi(4)disk(0)sci_unix
-s quad(0)pci(0)scsi(1)disk(1) -I -L -w"
In the command, the location of the root disk and the primary swap partition (the -s option) must be indicated with physical path specifiers because the naming database is not available on the CD. The -I option creates a naming database. The -L option labels the swap partition and is needed only if this partition has not been previously used for swap. The -w option places a disk label on the swap disk.
Click the Boot button on the PTX Console window to boot the operating system from the CD.
ATTENTION During the boot, you may see messages that the system cannot read or write to certain files. These messages can be ignored.
When the operating system is booted, only the root device (the CD-ROM device in this case) and the swap device will have permanent names in the naming database. All other devices will have temporary names. During the software installation, the devctl -N command will be run automatically to give the devices default permanent names and add them to the naming database. (For details about the naming database, refer to DYNIX/ptx System Configuration and Performance.)
The temporary name that was assigned to the original root disk might not match its original name. To restore the original name, run one of the following commands.
If you know the temporary name that was assigned to the original root disk, issue a command as follows:
# devctl -n +temporary_name original_name
The following example changes the temporary name +sd24 to the original name, sd0:
# devctl -n +sd24 sd0
If you do not know the temporary name that was assigned to the original root disk, use the following command to change the name.
# /sbin/ptxinstall/create_dev physical_path original_name
The following example changes the name of the device at the specified physical path to sd3:
# /sbin/ptxinstall/create_dev quad(0)pci(1)scsi(5) sd3
If you will be installing on an alternate disk, use the procedure "Create an Image with a Different Filesystem Type," later in this chapter, to create EFS filesystems on the alternate disk partition and then copy the current filesystems to that partition.
If you will be installing on the original root disk, build a VTOC and mount the root filesystem on that disk. (In the following example, the root filesystem is sd0s0):
# devbuild vtoc /dev/rdsk/sd0
# mount /dev/dsk/sd0s0 /mnt
Go to "Install Software With the ALT DISK DELTA Procedure" later in this chapter.
Before starting the installation, you must create an image of the root filesystem (and any other filesystems in which software will be installed) on the alternate disk. Although the following examples copy the current root filesystem, the image you create does not need to match the current root filesystem.
Also, the image can have the same filesystem type (for example, UFS or EFS) as the original filesystem, or you can change the filesystem type.
This procedure describes how to create an image that will have the same filesystem type as the original root filesystem. In the example, the original root disk is sd0 and the alternate disk is sd1.
The examples in the procedure create a UFS filesystem; however, you can use the same procedure to create an EFS filesystem (check the newfs(1M) man page for the appropriate flags.)
ATTENTION Be sure to use dump/restore to copy the filesystem image. Other utilities such as rdcp and dd are not aware of filesystem formats and cannot be guaranteed to copy a mounted read/write filesystem correctly.
ATTENTION Do not boot from the copied image on the alternate disk partition. The system must be booted from the original root partition and the software must be installed on the alternate disk partition.
To create the image, complete the following steps:
Ensure that the VTOC on the alternate disk has the same (or larger) partition sizes as the original root disk. (The root partition must be at least 2 GB.) If necessary, install the VTOC on the disk. (You can use the prtvtoc command to display the VTOCs). The commands have the following syntax.
# /etc/mkvtoc -g -s vtoc_name disk_name disk_type
# /etc/devbuild vtoc /dev/rdsk/disk_name
The following example installs a custom root VTOC on disk sd1:
# /etc/mkvtoc -g -s /etc/vtoc/root.vtoc sd1 hp97560
# /etc/devbuild vtoc /dev/rdsk/sd1
Create a filesystem for root on the alternate disk (sd1s0 in the following example):
# /etc/newfs /dev/rdsk/sd1s0
Copy the current root filesystem to the alternate disk. (The dump command is shown on two lines for readability). Be sure to specify the dump flags shown here. The commands have this syntax:
# /etc/mount /dev/dsk/alt_root_partition mountpoint
# sync
# /etc/dump 0bdsf 32 54000 10000 - /dev/rdsk/current_root_partition
| (cd alt_root_mountpoint; /etc/restore xbf 32 -)
The following example mounts the alternate root partition sd1s0 as /mnt and copies the current root filesystem to that partition.
# /etc/mount /dev/dsk/sd1s0 /mnt
# sync
# /etc/dump 0bdsf 32 54000 10000 - /dev/rdsk/sd0s0 | (cd /mnt;
/etc/restore xbf 32 -)
When the dump is complete, the following prompt appears:
set owner/mode for '.'? [yn]
Enter y at the prompt.
Unmount the alternate root partition (/mnt in this example):
# /etc/umount /mnt
Run labelit on the root filesystem on the alternate disk:
# /etc/labelit -F filesystem_type /dev/rdsk/alt_root_partition label
alt_root_partition
The filesystem_type can be either ufs or efs.
The following example assigns the label root to the alternate root partition.
# /etc/labelit -F ufs /dev/rdsk/sd1s0 root sd1s0
Run fsck on the root filesystem. Be sure to specify the appropriate filesystem type (ufs or efs). In the following example the filesystem on the alternate disk (sd1) is ufs.
# /etc/fsck -F ufs /dev/rdsk/sd1s0
If fsck should fail, use the -o full option of fsck to recover.
Mount the root filesystem on the alternate disk:
# /etc/mount -f filesystem_type /dev/dsk/sd1s0 /mnt
Issue a df command to confirm that the root filesystem is mounted.
# df
/ (/dev/dsk/sd0s0 ): 38760 blocks 25107 i-nodes
/mnt (/dev/dsk/sd1s0 ): 38812 blocks 25110 i-nodes
You now have an image of the current root filesystem on the alternate disk.
This procedure describes how to create an image that will have a different filesystem type from the original root filesystem. In the example, the original root disk is sd0 and the alternate disk is sd1.
The examples in the procedure are to create an EFS filesystem; however, you can use the same procedure to create a UFS filesystem.
ATTENTION Be sure to use dump/restore to copy the filesystem image. Other utilities such as rdcp and dd are not aware of filesystem formats and cannot be guaranteed to copy a mounted read/write filesystem correctly.
ATTENTION Do not boot from the copied image on the alternate disk partition. The system must be booted from the original root partition and the software must be installed on the alternate disk partition.
ATTENTION To create an EFS filesystem, ptx/EFS must be currently installed on your system or you must have booted the operating system from the distribution CD.
To create the image, complete the following steps:
Ensure that the VTOC on the alternate disk has the same partition sizes as the original root disk. (The root partition must be at least 2 GB.) If necessary, install the VTOC on the disk. (You can use the prtvtoc command to display the VTOCs.)
The following example installs a custom root VTOC on disk qd1:
# /etc/mkvtoc -g -s /etc/vtoc/root.vtoc sd1 hp97560
# /etc/devbuild vtoc /dev/rdsk/sd1
Create a filesystem for root on the alternate disk. Use the appropriate newfs flag to create either an EFS or UFS filesystem. The following example creates an EFS filesystem.
# /etc/newfs -F efs /dev/rdsk/sd1s0
Copy the current root filesystem to the alternate disk, creating an EFS filesystem. Be sure to specify the dump command flags shown here. (The command is shown on two lines for readability.) The commands have this syntax:
# /etc/mount -F efs /dev/dsk/alt_root_partition mountpoint
# sync
# /etc/dump 0bdsf 32 54000 10000 - /dev/rdsk/current_root_partition
| (cd alt_root_mountpoint; /etc/restore xbf 32 -)
The following example mounts the alternate root partition sd1s0 as /mnt and copies the current root filesystem to that partition.
# /etc/mount -F efs /dev/dsk/sd1s0 /mnt
# sync
# /etc/dump 0bdsf 32 54000 10000 - /dev/rdsk/sd0s0 | (cd /mnt;
/etc/restore xbf 32 -)
When the dump is complete, the following prompt appears:
set owner/mode for '.'? [yn]
Enter y at the prompt.
Unmount /mnt:
# /etc/umount /mnt
Run labelit on the root filesystem on the alternate disk:
# /etc/labelit -F filesystem_type /dev/rdsk/sd1s0 root sd1s0
Run fsck on the root filesystem on the alternate disk:
# /etc/fsck -F filesystem_type /dev/rdsk/sd1s0
If fsck should fail, use the -o full option to fsck to recover.
Mount the root filesystem on the alternate disk:
# /etc/mount /dev/dsk/sd1s0 /mnt
Issue a df command to confirm that the root filesystem is mounted.
# df
/ (/dev/dsk/sd0s0 ): 38760 blocks 25107 i-nodes
/mnt (/dev/dsk/sd1s0 ): 38812 blocks 25110 i-nodes
You now have an image of the current root filesystem on the alternate disk.
Change the filesystem type specified for the root filesystem in the /etc/vfstab file.
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.
If you have not done so already, insert the distribution CD into the CD-ROM 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. (The ROOT and INIT ALT DISK DELTA options will not appear if you booted from CD.)
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. The disk containing that 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 Select Software Packages window. 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 product 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 products 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 Select Software Packages 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 Select Software Packages 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. 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 or you booted from the distribution CD, 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-ROM device, such as cd1.
If you do not have another CD-ROM 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 and reboot the operating system on the installation disk after the software installation is complete.
ATTENTION Do not have ptx/INSTALL reboot the kernel.
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.
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
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 the 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
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.