The SCRATCH installation procedure does an initial (full) installation of the base operating system and the layered products that you have selected. 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.
ATTENTION SequentLINK cannot be installed with the SCRATCH procedure. Use the ROOT procedure to install this product after DYNIX/ptx V4.5.3 has been installed and the system has been rebooted.
The operating system supports two types of devices: local and shareable. Local devices are connected directly to the PCI/SCSI interface. Devices connected to the Fibre Channel Bridge 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:
The root disk (sd0)
Shareable disks (sd1, sd2, .. sd<n>) on quad0
Local disks (sd<n+1> ..) on quad0
Shareable disks on quad1
Local disks on quad1
This order continues for each remaining Quad.
If you prefer to use another naming scheme for your disks, use the devctl command to change the assigned names. See the DYNIX/ptx System Configuration and Performance Guide for the recommended device naming standard. (Also see devctl(1M).)
To perform the installation, complete the following steps:
[ ] | Take one of the following actions:
If your system is not running the latest versions of the Fibre Channel software, install the FC Switch product (if your system has switched fabric) and the cfwdl-Compatible Firmware Bundle, which contains the FC Bridge and Host Adapter firmware. ptx/SPDRIVERS should also be installed. You will see warnings if this product is not installed before you compile the kernel.
| ||
[ ] | 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.
| ||
[ ] | 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 12, "Build a Custom Kernel." | ||
[ ] | If you installed the Fibre Channel software, download the FC Switch firmware as described in the Fibre Channel Software Release Notesand the FC Bridge and Host Adapter firmware as described in Chapter 13 "Download Firmware with cfwdl" in these release notes. | ||
[ ] | Complete the post-installation steps described in Chapter 14. |
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.
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"
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. (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 8.
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 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:
[standalone]# /etc/devctl -n +tmpname permanent_name
Install a default 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 install the default root VTOC for your disk type.
[standalone]# /etc/mkvtocdisk_name disk_type
If you are unsure of the disk type, run the command /etc/infodev permanent_name. This command will return the vendor's model name of the device. These names correspond to the following VTOCs:
Model |
Capacity |
VTOC |
DFHSS4W/ DFHSS4E |
IBM 4 GB |
ibms4e |
DCHS09X |
IBM 9 GB |
ibms9w |
DGHS18X |
IBM 18 GB |
ibms18w.rootmir for IBM xSeries 430 and NUMA-Q 2000 with single disk in bootbay; ibms18w for other systems |
DRHS36V |
IBM 36 GB |
ibms36w |
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 and the swap device will be named sd0 (unless you assigned a different name in step 6). 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 the DYNIX/ptx System Configuration and Performance Guide.)
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 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 disk used for swap, you must 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.
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
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
ATTENTION To use ptx/ADMIN, your TERM variable must be set correctly. For the console on SCI-based systems, it must be set to vu320. If the menu system does not display properly, suspend or leave the menu system and type the following command: stty -tabs
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.
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 standard vtoc on disk? (Y/N) _ (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 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 ________
The installation procedure now obtains product information from the TOC file on the distribution medium.
ptx/INSTALL is now 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.5.x has not been certified for C2-level security.
Select the software packages to be installed from the window that appears next. 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.5.3 # 1003-xxxxx-xx base_comms ptx/BaseComms V1.2.1 N 1003-xxxxx-xx nfs ptx/NFS V4.7.2
ATTENTION ptx/SPDRIVERS must be installed on IBM xSeries 430 and NUMA-Q 2000 systems. You will see warnings if this product is not installed before you build the kernel. You should also install the cfwdl-Compatible Firmware Bundle. This product includes the FC Bridge and Host Adapter firmware.
We recommend that you also install ptx/Configuration Assistant. This product provides an interface to perform some initial setup of your system.
ATTENTION Do not install the CSM, QCIC, or ptx/Online Diagnostics software. This software is used only on Symmetry systems.
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. 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.5.3 # A 1003-xxxxx-xx base_comms ptx/BaseComms V1.2.1 1003-xxxxx-xx nfs ptx/NFS V4.7.2 A = automatically included. SELECT does not alter product list - use CANCEL
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 on the form. 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.
Configure and compile a kernel with default parameters Configure and compile a default kernel ____ following installation? (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 situation applies to your installation, the Crosstools Source Type form shown next will appear: you are currently running a version of DYNIX/ptx other than V4.5.3, 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.5.3 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.5.3 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 the "Rebuild manpages after installation" prompt. (This 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 the ptx/INSTALL Software Installation Guide.
ATTENTION Do not have ptx/INSTALL reboot the kernel if you have new versions of the stand-alone kernel (sak.dat) or the bootstrap program (ptxldr.elf) that you have not yet installed. This software must be installed before the system is rebooted.
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 If you are performing the installation while booted on DYNIX/ptx V4.4.x, then as layered products are installed, you will see error messages such as the following:
./command.sh[104]: 6255 Memory fault(coredump)As long as you have installed ptx/LIP, you can ignore these messages. With ptx/LIP installed, the failed commands will be rerun automatically when the system is booted.
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.
When the installation is complete, return to the "Installation Checklist" earlier in this chapter.
ATTENTION If you installed ptx/Configuration Assistant, it will run the first time the system is booted on DYNIX/ptx V4.5.3. This product provides an interface for performing some system setup tasks. When you exit the product, you will be asked whether you want it start automatically the next time you boot the system.
If you want to remove the distribution 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, the documentation instructed you to devdestroy the cd device after the software was installed. This is no longer necessary as ptx/INSTALL now executes any devdestory action that may be required as part of the installation.
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.
To correct this problem, use ptx ADMIN to create 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.
The swap partitions must be on local disks, which are indicated by an L in the "Flags" column of the /etc/dumpconf output. (If you are planning to rename the disks that will contain swap partitions, perform the devctl renaming operation before you create the swap partitions.)
When you have completed the installation, be sure to reconfigure your dump and secondary swap devices. Dump devices should be on dedicated local partitions, as described in the DYNIX/ptx System Recovery and Troubleshooting Guide. Secondary swap partitions should be on disks attached to the Fibre Channel.
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