The SCRATCH installation procedure does an initial (full) installation of the base operating system Volume 1 CD. It can be done in two ways:
If DYNIX/ptx is currently installed, boot from the current root disk and install on an alternate disk.
If DYNIX/ptx is not currently installed, boot from the distribution CD and install on the designated disk. You can also use this procedure to install on the current root disk.
For single-node systems, you can install on a shareable disk by first booting from the distribution CD. For clustered systems, the operating system must be installed on a local disk.
The operating system supports two types of devices: local and shareable. Local devices are connected directly to the PCI or SCSI interface. Devices connected to the Fibre Channel are shareable.
When you perform a scratch installation and then boot the system, the autoconfiguration procedure will automatically assign names to the devices on your system.
By default, the names of disks are assigned in the following order:
If you prefer to use another naming scheme for your disks, use the devctl command to change the assigned names. See DYNIX/ptx System Configuration and Performance for the recommended device naming standard. (Also see devctl(1M).)
To perform the installation, complete the following steps:
[ ] | Set the Node ID and Master ID, either from the VCS Console window:
Or from the CLI command line: -> cd /sys_name/quad_name The Node ID is specified in your service contract. On a single-node system, the Master ID should match the Node ID. On a clustered system, each node will have a unique Node ID; however, all nodes must use the same Master ID, which should be set to the lowest-numbered Node ID in the cluster. | ||
[ ] | Install DYNIX/ptx and layered products. Be sure to install ptx/SPDRIVERS, the cfwdl-Compatible Firmware Bundle, and the FC Switch, if your system is not running the current version. Use one of the following procedures:
| ||
[ ] | Create the /etc/devlabel file, which specifies the device labels to be assigned to the disks on your system. | ||
[ ] | If you booted from the distribution CD and set the autoBoot flag to boot the stand-alone kernel before installing a VTOC on the swap disk, reset the flag so that the operating system will boot past the stand-alone kernel: # /etc/bootflags autoBoot=1
| ||
[ ] | If you have not done so already, install and flash the console software, including the stand-alone kernel (sak.dat) and the bootstrap program (ptxldr.elf) from the NUMA Console Software CD. (Installation instructions are in the NUMA Console Software Release Notes.) You must shut down the operating system before installing this software.
| ||
[ ] | If necessary, run the sysdef command in the VCS CLI window to define the system. See the NUMA Console Software Release Notes. | ||
[ ] | Reboot the system.
| ||
[ ] | Add a user-defined name and a comment to the disk label for the root disk. See "Modify the Disk Label on the Root Disk," later in this chapter. If ptx/CLUSTERS is installed, you must run the rolling_upgrade_complete script before modifying the disk label. | ||
[ ] | Perform a ROOT installation of any remaining layered products. Review the installation log files to resolve any errors. | ||
[ ] | Build the kernel and reboot the system. See Chapter 8, "Build a Custom Kernel." | ||
[ ] | If you installed the Fibre Channel software, download the FC Switch firmware as described in the DYNIX/ptx V4.6.x Fibre Channel Software Release Notes and the FC Bridge and Host Adapter firmware as described in Chapter 9 "Download Firmware with cfwdl" in these release notes. | ||
[ ] | Complete the post-installation steps described in Chapter 10. |
If you are doing a scratch installation on the current root disk or on a system that is not currently running DYNIX/ptx, you must boot the operating system from the distribution CD. (You do not need to use this procedure if your system is currently running DYNIX/ptx and you want to install on an alternate disk; go to the next section "Install Software With the SCRATCH Procedure.")
If the swap disk you specify does not currently contain a VTOC, you will need to install one as described later in this procedure.
ATTENTION The default names assigned to devices during bootup may not be the names you expected. We recommend that you explicitly name any devices that will be used as installation targets or primary swap after booting the system from the CD.
To boot from the CD, complete the following steps:
If the system is currently running DYNIX/ptx, take it 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 Console Software Release Notes. If necessary, run the sysdef command in the VCS CLI window to define the system.
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.
-> 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. This is an example only. Be sure to specify the correct SCSI IDs for your system.
ATTENTION For systems with a bootbay, the CD is at SCSI ID 5.
-> 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 CD-ROM device 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 primary swap partition and is needed only if this partition has not been previously used for swap. The -w places a disk label on the swap disk. (For more information, see Appendix A.)
If there is currently a VTOC on the swap disk, click the Boot button on the PTX Console window to boot the operating system and then go to step 9.
ATTENTION During the boot, you may see messages that the system cannot read or write to certain files. In addition, you may see messages that /etc/makedev is terminating abnormally during devctl operations. These messages may be safely ignored.
If there is not a VTOC on the swap disk, complete the following procedure to install the VTOC and then boot the system:
From the CLI window, set the autoBoot flag to 0 to boot to the stand-alone kernel.
-> bootflags autoboot "0"
Click the Boot button to boot to the stand-alone kernel shell.
Mount the /etc/system directory as a mfs filesystem:
[standalone]# /etc/mount -F mfs -o -s=40000 /dev/dsk/mfs1 /etc/system
Run the devctl -S command to flush the in-memory copy of the device naming database to the device naming database file.
[standalone]# devctl -S
When you booted to the stand-alone kernel, the swap disk was assigned a temporary name. Use the following command to determine the temporary name. You must specify the physical path to the swap disk. The physical path must be enclosed in double quotation marks. (For information about the syntax, see "Physical Path Specifiers" in Appendix A.)
[standalone]# /etc/dumpconf -r "physical_path"
Assign a permanent name to the swap disk. If the disk is local, use sd0 as the permanent name; if it is shareable, use sd20.
[standalone]# /etc/devctl -n +tmpname permanent_name
Mount /tmp as a mfs filesystem:
[standalone]# /etc/mount -F mfs -o -s=40000 /dev/dsk/mfs2 /tmp
Install a VTOC on the swap disk, specifying the permanent name and the appropriate disk type. If the operating system will also be installed on the swap disk, we recommend that you use the crvtoc command to create a custom VTOC.
In the following command, the -b option creates a VTOC with boot, primary swap, and dump partitions numbered 0, 1, and 2. The default sizes for these partitions are used (root is 2GB, swap is 500 MB, dump is 4 GB). The -c option divides the remaining space on the disk into partitions of a specified size (2 GB in the example.) If you prefer, use the -n number_of_partitions option to divide the remaining space into a certain number of partitions. The -w option writes the VTOC to the disk specified by -d. The -s option creates an SVM private partition on the disk.
[standalone]# /etc/crvtoc -w -b -c 2G -s -d disk_name
Boot the operating system from the stand-alone kernel:
[standalone]# /stand/sci/standload -b
Rename the installation root disk (and the swap disk if it is a different disk) if necessary.
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. The CD-ROM device will be named cd0. If the swap device is local, it will be named sd0; otherwise, it will be named sd20 (unless you assigned a different name in step 7f). 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.)
ATTENTION The default names assigned to devices during bootup and by devctl -N may not be the names you expected. We recommend that you explicitly name any devices that will be used as installation targets or primary swap before beginning the installation.
If you know the physical path to the disk, use the following command to rename it. (For information about physical paths, see "Physical Path Specifiers" in Appendix A.)
# /sbin/ptxinstall/create_dev physical_path new_name
You can also run the /etc/dumpconf -r "physical_path" command to determine the current name of the device and then use the following devctl command to rename it:
# /etc/devctl -n old_name new_name
Device names must consist of a string of alpha characters followed by a string of numeric characters. The maximum length is 15 characters.
Go to "Install Software With the SCRATCH Procedure" later in this chapter.
ATTENTION If you will be installing the root filesystem on a disk other than the swap disk used in this procedure, there must be a VTOC on the disk. If necessary, you can have ptx/INSTALL place a new VTOC on the root disk.
To install software packages, use the following procedure. You must be root to perform the installation.
ATTENTION The NUMA Online Diagnostics Dispatcher, ptx/AGENT, ptx/PDC, ptx/SYNC, and SequentLINK products cannot be installed with the SCRATCH procedure. Use the ROOT procedure to install these products after DYNIX/ptx V4.6.1 has been installed and the system has been rebooted. Also you must use the ROOT procedure to install the Volume 2 CD, the ptx/LAE CD, or the Backup Toolkit CD.
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
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 SCRATCH 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 #
Specify information about the installation disk on the Disk Locations form.
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 being used for the installation:
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 either a partition on the root disk or the swap partition used to boot from CD, 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 booted from CD, the Install Disk Confirmation form will display the physical path to the installation disk that you specified. Because disks might not be assigned the names you expected when the system is booted from CD, be sure to verify that the installation disk is correct.
Install Disk Confirmation The disk you entered is located at ___ physical path quad(0)pci(0,0)scsi(1,0)disk(0,0,0) Enter 'Y' to confirm disk selection and continue with installation. Enter 'N' to reenter disk selection.
If you chose to have a standard VTOC installed on the installation 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 you chose to install a custom VTOC, enter information about the VTOC on the following screen (the default values are shown here). The root partition must be at least 2 GB in size. After the root, swap, and dump partitions are created, the remaining space on the disk will be divided into partitions.
You can specify either a size (or chunk) for the partitions, or the number of partitions to be created. If you specify a chunk size, the space will be divided into as many partitions as possible of that size. Any remaining space will be added to the last partition. If you specify a number of partitions, that number of equally sized partitions will be created. Any remaining space will be added to the last partition.
Custom VTOC Enter root file system partition size 2g Enter swap partition size 500m Enter dump partition size 4g Create SVM partition? N Specify other partitions by chunk (C) N size or number (N) of parts? Enter chunk size or number of ______ partitions
When you complete this screen, the contents of the VTOC will be displayed for your verification. If necessary, you can recreate the VTOC.
The installation procedure now obtains product information from the TOC file on the distribution medium and ptx/INSTALL is installed automatically.
At the next screen, answer N.
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
Do not answer Y; DYNIX/ptx V4.6.1 has not been certified for C2-level security.
Select the software packages to be installed from the window that appears next. You can select multiple packages. Following is an example.
Select one or more software packages to install/update Part Number Name Description Version ________________________________________________________________ 1003-xxxxx-xx base DYNIX/ptx(R) Base V4.6.1 # 1003-xxxxx-xx base_comms ptx/BaseComms V1.2.0 N 1003-xxxxx-xx nfs ptx/NFS V4.7.0
ATTENTION We recommend that you install ptx/Configuration Assistant. This product provides an interface to perform some initial setup of your system.
Certain software products require that you enter a license key into the system nodelock file before the product can be installed. The letter N appears before these products.
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 product that requires a license password, 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 chose 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.) The license entries you specify are added to the system nodelock file, /var/netls/nodelock.
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 ________
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.1 # 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
When a product requires that another product be installed, ptx/INSTALL verifies that the required product has been selected for installation. If required products have not been selected, the following form will appear. You can either reselect products or exit 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.
The installation procedure now determines whether the kernel needs to be recompiled after the installation is complete. You can override the value specified on the form.
We recommend that you answer Y to build 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.
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 the system is not running DYNIX/ptx V4.6 or you booted from the distribution CD, enter N at the prompt and then specify 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 will appear: you are currently running a version of DYNIX/ptx other than V4.6.1, you are installing the base operating system on an alternate disk, and your distribution media does not include the crosstools source needed to build the kernel.
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.1 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.1 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.
You will now be asked whether you want to build the man pages database and reboot the operating system on the installation disk after the software installation is complete. Answer N to both of these prompts.
The "Rebuild manpages after installation" option does not work for a scratch installation. You can build the man pages at a later time using one of the methods described in ptx/INSTALL Software Installation.
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.
ATTENTION The installation procedure sets both the permanent and the temporary bootpaths to point to the 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.
If you are installing ptx/Configuration Assistant, a problem in V1.1.0 prevents a required file from being properly linked. During the installation, the following errors are displayed about this problem:
cp: cannot access /opt/cfgassist/etc/runonce
To complete the ptx/Configuration Assistant installation, you must manually link the file before the system is rebooted on the new root partition. The following example assumes that the new root partition is /mnt.
# /bin/cp -p /mnt/opt/cfgassist/etc/runonce /mnt/etc/rcinit.d/S29cfgassist
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
When the installation is complete, return to the "Installation Checklist" earlier in this chapter.
If you want to remove the Volume 1 CD from the drive before booting the system, you can. However, the system will boot properly if the distribution CD is left in the drive during the boot operation. (Previously, you had to run the devdestroy command on the CD device so the system would shut down cleanly during the reboot.)
If you are upgrading from DYNIX/ptx V4.4/V4.5, you should create a /etc/devlabel file before rebooting the system. (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.
ATTENTION If you are upgrading from DYNIX/ptx V4.6 and there are unlabeled disks on your system that you want to label on the next reboot, you can create an /etc/devlabel file to assign the labels. Otherwise, you can skip this procedure.
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
The first time you boot the V4.6 system, you may encounter the following problems.
If you installed ptx/Configuration Assistant, it will run the first time the system is booted on DYNIX/ptx V4.6.1. This product provides an interface for performing some system setup tasks. When you exit the product, you will be asked whether you want it to start automatically the next time you boot the system.
If you want to use this product to add swap space, you will first need to perform some configuration steps. Press ! to exit the menu and go to the command line, and then complete the steps described under "Not Enough Swap Space."
When you boot the kernel, you may see a message stating that there is not enough local swap space available to save crash dumps. If this situation occurs, the system will not boot to multiuser mode.
Before adding more swap space, take the following steps.
Single-node systems. Assign a permanent name to any disk (other than the root disk) that will be used for swap, create a disk label, and then push the partitioning driver onto the disk:
# devctl -n +tmpname permanent_name
# diskown -w -n 0 permanent_name
# devbuild permanent_name
The swap partitions must be on node-owned disks, as indicated by the N disk label flag in dumpconf output.
Systems with ptx/CLUSTERS installed. Assign a permanent name to any disk (other than the root disk) that will be used for swap and push the partitioning driver onto the disk:
# devctl -n +tmpname permanent_name
# devbuild permanent_name
Add the disks to the /etc/devtab file:
vtoc /dev/rdsk/permanent_name
If the swap partitions are on shareable disks, edit the /etc/devlabel file to specify that the disks are node-owned.
If you are using ptx/Configuration Assistant, type exit to return to the program and then add the swap partitions.
Otherwise, use ptx ADMIN to create the additional swap partitions. (Use System Administration -> Swap Space Management -> Add a Swap Device.) When you add swap partitions with ptx/ADMIN, they will be maintained across system boots. If you use swap -a to create swap partitions, the swap designation will be lost when the system is rebooted.
If ptx/SVM is installed, you may see the following message when you boot the kernel:
vxvm:vxprint: ERROR: IPC failure: Configuration daemon is not accessible
This message is normal and indicates that the SVM daemon is not currently running. You will not see this message after ptx/SVM has been configured.
If you requested that ptx/INSTALL do an automatic reboot, the reboot will fail if the system was not able to unmount the root filesystem, which is mounted at /installmnt. To correct this problem, exit ptx/ADMIN, unmount the filesystem, and then reboot manually:
# umount /installmnt
# init 6
If the system booted to multiuser mode, it will have assigned permanent names to all devices that had temporary names.
If the system booted to single-user mode, devices (other than the root and swap disk) that have not been explicitly named will have temporary names. If you are planning to keep the system in single-user mode and install additional layered products, you must assign permanent names to any devices that you will need to access. For example, you will need to assign a permanent name to the CD-ROM device:
# devctl -n +cd0 cd0
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 the rolling_upgrade_complete 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.