5.4 Installation of Tru64 UNIX
5.4 Installation of Tru64 UNIX
In this section, we will cover an actual installation of Tru64 UNIX. For our example of this installation, we will use Tru64 UNIX version 5.1A on one node of what will be a two-node cluster.
As we stated earlier in this chapter, as we will be installing Tru64 UNIX in preparation for building a TruCluster Server environment, we will need to install the operating system only once – no matter how many cluster nodes we may eventually have[2].
The following is a list of individual tasks that we will go over to perform the installation of Tru64 UNIX:
| Section | |
|---|---|
|
| 5.4.1 5.4.2 5.4.3 5.4.4 5.4.4.1 5.4.4.2 5.4.5 5.4.6 5.4.6.1 5.4.7 5.4.8 5.4.9 5.4.10 |
Well, now that we know what we are going to do, let's get on with it!
5.4.1 Boot from the Installation CD
Before we actually boot from the Tru64 UNIX Installation CD (that's the CD entitled Compaq Tru64 UNIX Version 5.1A Operating System Volume 1), let's first initialize the system. At the console prompt, use the init command.
P00>>> init
Let's identify the CDROM from which we will be booting by using the "show device" command at the console prompt.
P00>>> show device dga62.1001.0.7.1 $1$DGA62 HSG80 V86F dkc0.0.0.7.0 DKC0 COMPAQ BD009635CB BDC4 dqa0.0.0.105.0 DQA0 CD-224E 9.5B ←CDROM dva0.0.0.0.0 DVA0 eia0.0.0.9.1 EIA0 00-50-8B-AE-FE-DC pga0.0.0.7.1 PGA0 WWN 2000-0000-c924-3514 pka0.7.0.6.0 PKA0 SCSI Bus ID 7 pkb0.7.0.106.0 PKB0 SCSI Bus ID 7 pkc0.7.0.7.0 PKC0 SCSI Bus ID 7 Now that we have identified the CDROM, let's boot the Tru64 UNIX Operating CD and start our installation.
| Caution | Before proceeding, make sure that you have performed the necessary preparatory steps in Chapter 4 such as setting environment variables and installing the latest firmware. |
P00>>> boot dqa0 ... *** Performing CDROM Installation
5.4.2 Start the Installation
The first decision you must make after booting the Tru64 UNIX operating system installation CD is as follows:
Remember, you can always get extra information by typing help. 1) U.S. English Installation 2) Installation with Worldwide Language Support 3) Exit Installation Enter your choice: 1
By selecting "1", we choose to perform a "U.S. English Installation" of Tru64 UNIX.
| Note | If you are using the non-GUI installation procedure and need a customized disk label on your installation disk, you would select option "3" and proceed to label the disk as described in section 4.2.1. |
5.4.3 Setup Information for a Full Installation
The Installation program prompts for information needed to build our system as you'll see in the output that follows.
Enter a password to use as the root (superuser) password. Be sure to remember this password, because it is needed to log in as the user "root" following installation. The password must be at least six characters long, and at least one of the first eight characters must be a number, special character or uppercase letter (A-Z). Enter root password: xxxxxxxx Retype root password: xxxxxxxx
One of the first things the Installation software does, aside from asking what type of installation you want, is to prompt for the root password. While we encourage the use of "good and strong passwords"[3] for any user on any computer system, it is especially imperative for the root user. And please, please do not put your password on a sticky note and attach it to your monitor!
Choose a hostname for this system. The hostname identifies the system on the network. The hostname must start with a letter, and may include letters, numbers, periods and hyphens. Enter the hostname for this system: molari
Next, we are prompted for the hostname of the system that we are installing.
The next few prompts are for selecting the location and area (or time zone) the system is in.
Select the location that best describes your site. This is to determine what time zone your site is in. If your location includes multiple time zones (for example, Asia), the next question will ask you which of those you want. 1) Africa 7) Australia 13) Etc 19) MST 2) America 8) CET 14) Europe 20) MST7MDT 3) Antarctica 9) CST6CDT 15) Factory 21) PST8PDT 4) Arctic 10) EET 16) HST 22) Pacific 5) Asia 11) EST 17) Indian 23) SystemV 6) Atlantic 12) EST5EDT 18) MET 24) WET
Enter your choice:12
Next, you will be prompted to enter the date and time.
Enter the current date (as mm/dd/[cc]yy): 08/17/2002
Enter the current time in 24-hour format (as hh:mm): 23:22
The date and time has been set to: Sat Aug 17 23:22:00 EDT 2002 Is this correct (y/n) ? y
5.4.4 Select the Software to Install
In this section of the Installation, we are prompted for the software subsets that we will be installing.
*** Software Selection *** ** Reviewing available software for: Tru64 UNIX V5.1A Operating System ( Rev 1885 ) Please wait ... The following options are available: o Select "All Software" to install all mandatory and all optional software for the operating system. You will be given the opportunity to view all software after selecting this option and to confirm your choice. o Select "Mandatory Only" to install the minimum required software. No optional software will be installed. You will be given the opportunity to view the mandatory software after selecting this option and to confirm your choice. o Select "Customize" to interactively select software from a numbered list of software subsets. You will then be given the opportunity to confirm your choices. 1) All Software 2) Mandatory Only 3) Customize
Enter your choice:3
We chose "3" or "Customize" because we want to select the software subset that will be installed.
5.4.4.1 Select Mandatory Software Subsets
The following output shows the mandatory software components that are installed as the result of a customized installation:
The following base operating system subsets are mandatory and will be installed automatically unless you choose to exit without installing any subsets: * AdvFS Kernel Modules * Base System * Base System - Hardware Support * Base System Management Applications and Utilities * Basic Networking Configuration Applications * Basic Networking Services * Basic X Environment * CDE Desktop Environment * CDE Mail Interface * CDE Minimum Runtime Environment * Compaq Management Agents Version 2.1b * Compiler Back End * DECwindows 100dpi Fonts * DECwindows 75dpi Fonts * Doc. Preparation Tools * Graphical Base System Management Utilities * Graphical Print Configuration Application * Graphical System Administration Utilities * Hardware Kernel Header and Common Files * Hardware Kernel Modules * Java 1.1.8-10 Environment * Kernel Header and Common Files * Local Printer Support * Logical Storage Manager Kernel Modules * NFS(tm) Configuration Application * NFS(tm) Utilities * Netscape Communicator V4.76 * PCXAL Keyboard Support * Service Tools * Standard Kernel Modules * Tcl Commands * Tk Toolkit Commands * Tru64 UNIX Base System * X Fonts * X Servers Base * X Servers for PCbus Space used after mandatory subsets (root/usr/var): 81.3 MB/307 MB/4.9 MB
5.4.4.2 Select Only Some of the Optional Software Subsets
In this section of the Installation, we are prompted for the software subsets that are considered optional to the operation of Tru64 UNIX.
As we want our cluster to be able to grow and scale to meet our computer needs now and into the future, we recommend that all hardware-related subsets be installed so that if you add a system with a different hardware configuration, it will automatically be recognized without the need for installing additional software subsets. We also recommend that you use your best judgment to determine which software subsets to install by reading the description of the subsets in Appendix C of the Tru64 UNIX Installation Guide. In other words, take the time and plan what you are going to install before you do the installation. You should really know and understand what software will be installed on your system and why it is there.
| Note | The output shown is from a V5.1A installation. The number of subsets will differ from version to version. |
Optional Tru64 UNIX software subsets are grouped into the following categories:
-
General Applications
-
Kernel Build Environment
-
Kernel Software Development[4]
-
Mail Applications
-
Network-Server/Communications
-
Obsolete Components
-
Printing Environment
-
Reference Pages
-
Software Development
-
Supplemental Documentation
-
System Administration
-
Text Processing
-
Windowing Environment
-
Windows Applications
The following output is trimmed to save a tree or two. Each category will contain one or more subsets to choose.
Optional software subsets are listed below. There may be more optional subsets than can be presented on a single screen. If this is the case, you can choose subsets one screen at a time. At any prompt, you can enter "a" to install all of the subsets, "m" to install only the mandatory subsets, or "c" to cancel your selections and redisplay this menu. All of the choices you make will be collected for your confirmation before continuing the installation. Refer to the "Installation Guide" for descriptions of individual subsets. - General Applications: 1) Additional Terminfo databases 2) Computer Aided System Tutor 3) DOS tools 4) Java 1.2.2-8 Environment 5) Local Area Transport (LAT) 6) UNIX(tm) SVID2 Compatibility 7) UNIX(tm) to UNIX(tm) Copy Facility 8) perl 5.6.0 Runtime 9) xemacs Runtime - Kernel Build Environment: - Mail Applications: - Network-Server/Communications: - Obsolete Components: - Printing Environment: - Reference Pages: - Software Development: - Supplemental Documentation: - System Administration: - Text Processing: - Windowing Environment: - Windows Applications: ... 64) Virtual X Frame Buffer
Space used (root/usr/var): 93.6 MB/589 MB/10.1 MB Add to your choices, or press RETURN to confirm choices. Enter "c" to cancel your choices and redisplay this menu. Choices (for example, 1 2 4-6): 1 3-4 6 8-9 12 14 18-39 41-49 51-55 57-59 62 63
5.4.4.3 Verification of Optional Software Subsets
The installation software asks that we verify that we want to install all the selected software subsets and that these software subsets will be loaded for the installation.
The following subsets will be loaded:
At this point, the selected (and mandatory) subsets will be displayed followed by the disk space required and a prompt to verify that the selection is correct. (The output has been trimmed.)
Space required in (root/usr/var): 93.6 MB/600 MB/10.3 MB Are these the software subsets that should be loaded (y/n) ? y
Now that we have selected everything that we want to have installed, we should be all set. Right? Well, not quite yet.
5.4.5 Select the Kernel Options to Build into the UNIX Kernel
Now that we have told the installation software what software subsets we want to install, we next have to tell it how to build the UNIX kernel once it completes the installation and configuration of all the software subsets. There are three choices as shown in the following output.
*** Kernel Options Selection *** The following options are available: o Select "All Options" to automatically build all mandatory and all optional kernel components into the tailored kernel. o Select "Mandatory Only" to automatically build only the mandatory kernel components into the tailored kernel. o Select "Customize" to manually select the optional kernel components. You will be prompted for your selection later in the installation process after all software subsets have been loaded and the system has been rebooted from the new system disk. The mandatory kernel components will be automatically included in the custom-built kernel. 1) All Options 2) Mandatory Only 3) Customize
Enter your choice: 3
We will choose option "3" to select the kernel options that we know we will use. Selecting only the kernel options that we need will produce a smaller UNIX kernel that can potentially perform better and more efficiently than if the kernel is built with all kernel options.
| Note | By choosing option "1" or "2," the installation program will build the kernel without any further input from you. In other words, once the installation process begins, it will continue unattended. By choosing option "3," the installation process will stop prior to building the kernel to request the options to add to the kernel. |
5.4.6 Choose a File System Type to Use for the Operating System's File Systems
These next few prompts have to do with whether or not we will be using the Logical Storage Manager (LSM), what type of file system we will be using, and the file system layout for the local system disk. The prompt for LSM is for encapsulating the operating system disk. As this is not propagated to the cluster disks during the creation of the cluster, we recommend you answer "no" when prompted.
*** File System Selection *** The Logical Storage Manager (LSM) is a disk storage management tool that can help protect against data loss through the use of disk mirroring, can improve disk I/O performance through the use of disk striping, and can dynamically extend available disk storage through the use of disk concatenation. Mirroring and striping through LSM require a separate license PAK. By choosing LSM, all file systems and swap areas created by the installation process will be under LSM control. Enter "help" for more information about LSM.
Would you like to use LSM (y/n) ? n
5.4.6.1 Determine the File System Layout
In Chapter 4, we partitioned the local disk in preparation for the Tru64 UNIX installation. You can do this by either:
-
Escaping to the shell and using the disklabel(8) command, or
-
Using the diskconfig(8) command (part of the GUI installation).
The disk partition layout used for the system disk was based on the space needed for our chosen subsets, expected configuration, and future growth. Note the specific layout later in this section.
In this section of the installation, we will be prompted to choose both the device onto which we will install the operating system and the partition layout for each of file systems. By choosing the custom file system layout instead of the default file system layout, we can leverage the disk partitions that were created earlier.
For the standalone operating system disk, you must use the Advanced File System (AdvFS) for all file systems – this is a requirement for creating a cluster.
Choose your file system layout: o The default file system layout installs the operating system onto a single disk, and provides the most typical file system configuration: * root file system on the "a" partition * swapping area on the "b" partition * /usr file system on the "g" partition * /var in the /usr file system This option also provides a recommended disk partition table that is calculated based on existing software selections and future growth considerations. Additionally, you may select either the UFS or AdvFS file system type. o The custom file system layout lets you choose the partition and file system type individually for each of the file systems created by the installation process. You should choose this option if: * You want to place the file systems across multiple disks. * You want to place the file systems on a single disk, but there is existing data on that disk that must be protected. * You do not want the same file system type for each file system. * You want to create more than one swap area. 1) Default file system layout 2) Custom file system layout
Enter your choice: 2
In this section, we select the hard drive onto which we will install root (/). By default, this is installed on the "a" partition of the drive. We also elect to use AdvFS as the file system that will be used for root (/).
Select a disk for the root file system. The root file system will be placed on the "a" partition of the disk you choose. To visually locate a disk, enter "ping <disk>", where <disk> is the device name (for example, dsk0) of the disk you want to locate. If that disk has a visible indicator light, it will blink until you are ready to continue. Device Size Controller Disk Name in GB Type Model Location 1) dsk0 18.2 SCSI BD018635C4 bus-5-targ-0-lun-0 ...
Enter your choice: 1
Select the file system type for the root file system. 1) UFS -- UNIX File System 2) AdvFS -- Advanced File System
Enter your choice: 2
For the /usr file system, we select the "g" partition of the same device on which root (/) is installed. We use AdvFS for the file system type for /usr.
Select the disk where the /usr file system will reside, or enter "ping <disk>" where <disk> is the device name (for example, dsk0) to physically identify a particular disk. Device Size Controller Disk Name in GB Type Model Location 1) dsk0 18.2 SCSI BD018635C4 bus-5-targ-0-lun-0 ...
Enter your choice: 1
Select the dsk0 partition where the /usr file system will reside. This partition must be at least 482MB in order to fit the software that you have selected. However, a size of 700 MB or greater is recommended to allow for additional layered software and future upgrade considerations. Start End Partition Size Block Block Overlaps 1) b 4.5GB 1048576 10485760 c 2) e 3.9GB 10485760 18787864 c 3) f 2.0GB 18787864 22982168 c 4) g 4.0GB 22982168 31370776 c 5) h 2.0GB 31370776 35565080 c
Enter your choice: 4
Select the file system type for the /usr file system. 1) UFS -- UNIX File System 2) AdvFS -- Advanced File System
Enter your choice: 2
The swap partition will also go on the same device as root (/). This time we will use the "b" partition for swap as this is approximately three times the size of memory.
Select the disk where the first swapping area (swap1) will reside, or enter "ping <disk>" where <disk> is the device name (for example, dsk0) to physically identify a particular disk. Device Size Controller Disk Name in GB Type Model Location 1) dsk0 18.2 SCSI BD018635C4 bus-5-targ-0-lun-0 ...
Enter your choice: 1
Select the dsk0 partition where the first swapping area (swap1) will reside. Start End Partition Size Block Block Overlaps 1) b 4.5GB 1048576 10485760 c 2) e 3.9GB 10485760 18787864 c 3) f 2.0GB 18787864 22982168 c 4) h 2.0GB 31370776 35565080 c
Enter your choice: 1
As we have chosen not to have a secondary swap partition, we answer "no" when prompted.
You may choose to have a second swapping area (swap2). Do you want a second swapping area (y/n) ? n
In this section, we are prompted if we want to have a separate /var from /usr. In our case, we normally do keep /usr and /var as separate file systems. In keeping with tradition, we keep /var on the "h" partition. The /var file system is also on an AdvFS file system.
You can make /var a separate file system, or you can have it share space on the /usr file system.
Should /var be a separate file system (y/n) ? y
Select the disk where the /var file system will reside, or enter "ping <disk>" where <disk> is the device name (for example, dsk0) to physically identify a particular disk. Device Size Controller Disk Name in GB Type Model Location 1) dsk0 18.2 SCSI BD018635C4 bus-5-targ-0-lun-0 ...
Enter your choice: 1
Select the dsk0 partition where the /var file system will reside. Start End Partition Size Block Block Overlaps 1) e 3.9GB 10485760 18787864 c 2) f 2.0GB 18787864 22982168 c 3) h 2.0GB 31370776 35565080 c
Enter your choice: 3
Select the file system type for the /var file system. 1) UFS -- UNIX File System 2) AdvFS -- Advanced File System
Enter your choice: 2
Finally, we verify our disk partition selections for our Tru64 UNIX system disk's file systems.
You have requested this file system layout: * root file system on dsk0a, type AdvFS * /usr file system on dsk0h, type AdvFS * /var file system on dsk0h, type AdvFS * first swapping area (swap1) will be on dsk0b * no second swapping area (swap2)
Is this the correct file system layout (y/n) ? y
Table 5-1 contains the partition layout for the system disk that we just configured.
| Tru64 UNIX Operating System Disk Layout | |||
|---|---|---|---|
| Mount Point | File System | Partition Size | Partition |
| root(/) | root_domain#root | 512 MB | dsk0a |
| /use | usr_domain#usr | 4.0GB | dsk0g |
| /var | var_domain#var | 2.0GB | dsk0h |
| swap | swap | 4.5 GB | dsk0b |
It should be noted that while we were using an 18.2 GB hard disk drive for the system disk, we were not using the guidelines from HP for the layout of the system disk. HP recommends that for a system disk over 3 GB, the system's root (/) should be 384 MB and the swap should be 384 MB (if not larger)[5]. It has been our experience that for the original system disk of a system that will be used as the basis for building a cluster, the system's root (/) should be at least 512 MB and the swap should be two to three times the size of memory. As this system has 1.5 GB of memory, swap is created to be 4.5 GB in size. For this system disk, though, we won't get too concerned about the swap size. It's likely to be used only long enough to build the cluster, or if we need a standalone operating system disk to troubleshoot a cluster problem.
So should you follow our example or use what HP recommends? What HP has published in their documentation are guidelines based on input from the designers, developers, and customers of Tru64 UNIX and TruCluster Server. What we present is based mostly on experience. We believe that you should start with HP's recommendations, deviating when necessary based on what you know about your system's expected workload.
5.4.7 Confirm the Selections Before Starting the Installation
This next section will allow you to verify or modify any earlier selections made for the installation.
You have now answered all questions needed to install the operating system. Press CTRL/C to cancel the installation; or type "history" to modify your earlier answers; or press RETURN to proceed with installation:
In our case, we were satisfied with all our selections so we continue with the installation.
5.4.8 Create the File Systems and Install the Software Subsets
There really isn't much for us to do except monitor the creation of all the file systems and the loading of the software subsets that we had selected. So grab lunch or enjoy a long coffee break…
Continuing installation... Restoring the existing disk label on device dsk0 Creating the root file system on device dsk0a Creating the usr file system on device dsk0h Creating the var file system on device dsk0g Creating the swap1 file system on device dsk0b The installation procedure will now load a total of 85 software subsets on your disk partitions. This total includes the following products: * 85 Base Operating System subsets This process will take from 45 to 120 minutes to complete depending on your distribution media and processor type. LOADING THE BASE OPERATING SYSTEM SOFTWARE SUBSETS Checking file system space required to install specified subsets: File system space checked OK. 85 subsets will be installed. Loading subset 1 of 85 Base System Copying from /ALPHA/BASE (disk) Working....Tue Jan 22 20:16:15 PST 2002 Verifying ... 85 of 85 subsets installed successfully.
To spare you the repetition of seeing 84 additional software subset loads, we have provided one software subset load as representative of the other 84.
5.4.9 Configure the Software Subsets
Now that all the operating system software subsets are loaded, we start the configuration phase of these same software subsets. This phase is typically started by a reboot of the system in which instead of booting off the CDROM, it boots off the newly created system disk.
After the reboot is complete, the system starts configuring the previously loaded software subsets.
Checking for Installation Tasks... ... Executing Installation Tasks... *** SYSTEM CONFIGURATION *** Configuring "Base System" (OSFBASE520) ... Configuring "AdvFS Daemon" (OSFADVFSDAEMON520) The Advanced File System Daemon includes support for the License Management Facility (LMF). A Product Authorization Key (PAK) is required to use the file-system utilities. See the AdvFS Installation Guide for information on registering and activating the PAK. ... The system name assigned to your machine is 'molari'.
Again, to save you from the repetition of seeing all the additional software subset configurations, we have provided two software subset configurations. The first is representative of the others. The second software subset configuration, for the "AdvFS" Daemon, is included because it indicates that we must install a License Management Facility (LMF) Product Authorization Key (PAK) in order to use the AdvFS file system utilities.
5.4.10 Configure and Build the UNIX Kernel
Earlier, when we were prompted for kernel configuration options, we selected to do a customized kernel. In this section of the Installation, we are given the opportunity to identify exactly which options are needed for our system's kernel.
If we had selected "All Options" or "Mandatory Only" for the Kernel configuration options, we would not be receiving this dialogue at all. We believe that by selecting only those options that we use, we should have a smaller and better performing kernel.
*** KERNEL CONFIGURATION AND BUILD PROCEDURE *** *** KERNEL OPTION SELECTION *** Selection Kernel Option --------------------------------------------------------------- 1 System V Devices 2 NTP V3 Kernel Phase Lock Loop (NTP_TIME) 3 Kernel Breakpoint Debugger (KDEBUG) 4 Packetfilter driver (PACKETFILTER) 5 IP-in-IP Tunneling (IPTUNNEL) 6 IP Version 6 (IPV6) 7 Point-to-Point Protocol (PPP) 8 STREAMS pckt module (PCKT) 9 Data Link Bridge (DLPI V2.0 Service Class 1) 10 X/Open Transport Interface (XTISO, TIMOD, TIRDWR) 11 Digital Versatile Disk File System (DVDFS) 12 ISO 9660 Compact Disc File System (CDFS) 13 Audit Subsystem 14 All of the above 15 None of the above 16 Help 17 Display all options again -------------------------------------------------------------- Enter your choices, choose an overriding action or press <Return> to confirm previous selections.
Choices (for example, 1 2 4-6): 2 4 8 11 13
You selected the following kernel options: NTP V3 Kernel Phase Lock Loop (NTP_TIME) Packetfilter driver (PACKETFILTER) STREAMS pckt module (PCKT) Digital Versatile Disk File System (DVDFS) Audit Subsystem
Is that correct? (y/n) [y]: y Do you want to edit the configuration file? (y/n) [n]: n
The Tru64 UNIX kernel is then built based on the kernel configuration options selected.
As of this writing, IP Version 6 is not supported on TruCluster Server so please do not select IP Version 6 when you do your own Tru64 UNIX kernel configuration. At a minimum, please review the TruCluster Server Release notes on what is and is not supported when it comes to kernel configuration options.
The system will now automatically build a kernel with the selected options and then reboot. This can take up to 15 minutes, depending on the processor type. When the login prompt appears after the system has rebooted, use 'root' as the login name and the SUPERUSER password that was entered during this procedure, to log into the system. *** PERFORMING KERNEL BUILD *** Working....Tue Jan 22 20:35:41 PST 2002 The new version ID has been successfully set on this system. The entire set of new functionality has been enabled. This message is contained in the file /var/adm/smlogs/it.log for future reference.
At this point, the system will reboot. As soon as the system restarts, it will run on the newly built Tru64 UNIX kernel.
[2]As of this writing, up to eight nodes are supported in a TruCluster Server environment.
[3]A "good and strong password" is a password with mixed case letters and numbers. At this point in the installation, only the base security is supported so just the first eight characters of the password have meaning.
[4]Subsets cannot be chosen in the initial installation.
[5]Table 6-7: Recommended Partition Table by Disk Capacity, Tru64 UNIX Installation Guide.
EAN: 2147483647
Pages: 273