newbook.document.writeln(''); newbook.document.close(); newbook.frames[2].location.href = targetFile; } // -->

5 Preparing to Install the Software

This chapter covers the steps you must complete before installing the Tru64 UNIX and TruCluster Server software.

Before you can install the base operating system, you must:

Set the device unit number of the disk where you will install the base operating system software. Setting the device unit number allows the installation scripts to recognize the disk.

Set the device unit number for the first cluster member boot disk.

Verify that the console recognizes these disks as valid boot devices.

After installing the base operating system, reset the bootdef_dev console environment variable to ensure that there is a path to the boot disk if the HSV110 controllers have failed over.

Before you can install the TruCluster Server software, you must:

Determine the dskn to use for cluster installation.

Label the disks to be used for cluster installation.

5.1 Set the Device Unit Number

The device unit number is a subset of the device name as shown in a show device console display. For example, in the device name dga1001.1001.0.7.0, the device unit number is 1001 (as in dga1001). The console uses this device unit number to identify a storage unit. When you set a device unit number, you are really setting an alias for the device worldwide name (WWN). The 64-bit WWN is too large to be used as the device unit number, so an alias is used instead.

This section describes how to use the wwidmgr -quickset command to set the device unit number for the Fibre Channel disks to be used as the Tru64 UNIX Version 5.1B installation disk or cluster member system boot disks. Setting the device unit number allows the installation scripts to recognize a Fibre Channel disk.

To set the device unit number for a Fibre Channel device, follow these steps:

From Table 4-1, obtain the OS unit ID for the virtual disk to be used as the Tru64 UNIX Version 5.1B installation disk or cluster member system boot disks. The OS unit ID is referred to as the user-defined identifier (UDID) by the console software.
For instance, in Table 4-1, the Tru64 UNIX disk has an OS unit ID of 1001. The OS unit ID for the cluster member 1 boot disk is 1005, and the cluster member 2 boot disk is 1006.

From the AlphaServer console, use the wwidmgr -clear all command to clear the stored Fibre Channel wwid1, wwid2, wwid3, wwid4, N1, N2, N3, and N4 console environment variables. You want to start with all wwidn and Nn variables clear.
A console initialization is generally required before you can use the wwidmgr command. For example:
```
P00>>> init
    
.
.
.
P00>>> wwidmgr -clear all
P00>>> show wwid*
wwid0                                   
wwid1                                   
wwid2                                   
wwid3
P00>>> show n*
N1                                      
N2                                      
N3                                      
N4
 
```
Note

The console only creates devices for which the wwidn console environment variable has been set, and are accessible through an HSV110 N_Port as specified by the Nn console environment variable also being set. These console environment variables are set with the wwidmgr -quickset or wwidmgr -set wwid commands. The use of the wwidmgr -quickset command is shown in the next step.

Use the wwidmgr command with the -quickset option to set a device unit number for the Tru64 UNIX Version 5.1B installation disk and the first cluster member system boot disk.

The wwidmgr command with the -quickset option is used to define a device unit number, based on the OS unit ID (also known as the UDID at the console), as an alias for the WWN for the Tru64 UNIX installation disk and the first cluster member system boot disk. The wwidmgr -quickset utility sets the device unit number and also provides a display of the device names and how the disk is reachable (reachability display).

The wwidmgr -quickset command may generate multiple device names for a given device unit number, because each possible path to a storage unit is given its own device name.

Set the device unit number for the Tru64 UNIX Version 5.1B installation disk and the first cluster member system boot disk as follows:

Set the device unit number for the Tru64 UNIX Version 5.1B installation disk to 1001 as shown in Example 5-1.

Example 5-1: Setting the Device Unit Number for the BOS Installation Disk

P00>>> wwidmgr -quickset -udid 1001
 
Disk assignment and reachability after next initialization:
 
6005-08b4-0001-00b2-0000-c000-025f-0000
                          via adapter:         via fc nport:        connected: 
dga1001.1001.0.7.0       pga0.0.0.7.0         5000-1fe3-0008-de8c      No 
dga1001.1002.0.7.0       pga0.0.0.7.0         5000-1fe3-0008-de89      Yes
dga1001.1003.0.7.0       pga0.0.0.7.0         5000-1fe3-0008-de8d      No 
dga1001.1004.0.7.0       pga0.0.0.7.0         5000-1fe3-0008-de88      Yes
 
dgb1001.1001.0.8.1       pgb0.0.0.8.1         5000-1fe3-0008-de8c      Yes
dgb1001.1002.0.8.1       pgb0.0.0.8.1         5000-1fe3-0008-de89      No
dgb1001.1003.0.8.1       pgb0.0.0.8.1         5000-1fe3-0008-de8d      Yes 
dgb1001.1004.0.8.1       pgb0.0.0.8.1         5000-1fe3-0008-de88      No

The wwidmgr -quickset command provides a reachability display equivalent to issuing the wwidmgr -show reachability command. The reachability part of the display provides the following information:

The WWN for the storage unit that is to be accessed.

The new device name for the storage unit.

The KGPSA adapters through which a connection to the storage unit is potentially available.

The WWID of the HSV110 port(s) (N_Ports) that will be used to access the storage unit.

In the connected column, whether the storage unit is currently available through the KGPSA to HSV110 controller port connection.

Set the device unit number for the first cluster member system boot disk to 1005 as shown in Example 5-2.

Example 5-2: Setting the Device Unit Number for the First Cluster Member Boot Disk

P00>>> wwidmgr -quickset -udid 1005
 
Disk assignment and reachability after next initialization:
 
6005-08b4-0001-00b2-0000-c000-025f-0000
                          via adapter:         via fc nport:        connected: 
dga1001.1001.0.7.0       pga0.0.0.7.0         5000-1fe3-0008-de8c      No 
dga1001.1002.0.7.0       pga0.0.0.7.0         5000-1fe3-0008-de89      Yes
dga1001.1003.0.7.0       pga0.0.0.7.0         5000-1fe3-0008-de8d      No 
dga1001.1004.0.7.0       pga0.0.0.7.0         5000-1fe3-0008-de88      Yes
 
dgb1001.1001.0.8.1       pgb0.0.0.8.1         5000-1fe3-0008-de8c      Yes
dgb1001.1002.0.8.1       pgb0.0.0.8.1         5000-1fe3-0008-de89      No
dgb1001.1003.0.8.1       pgb0.0.0.8.1         5000-1fe3-0008-de8d      Yes 
dgb1001.1004.0.8.1       pgb0.0.0.8.1         5000-1fe3-0008-de88      No
 
6005-08b4-0001-00b2-0000-c000-0277-0000
                          via adapter:         via fc nport:        connected: 
dga1005.1001.0.7.0       pga0.0.0.7.0         5000-1fe3-0008-de8c      No 
dga1005.1002.0.7.0       pga0.0.0.7.0         5000-1fe3-0008-de89      Yes
dga1005.1003.0.7.0       pga0.0.0.7.0         5000-1fe3-0008-de8d      No 
dga1005.1004.0.7.0       pga0.0.0.7.0         5000-1fe3-0008-de88      Yes
 
dgb1005.1001.0.8.1       pgb0.0.0.8.1         5000-1fe3-0008-de8c      Yes
dgb1005.1002.0.8.1       pgb0.0.0.8.1         5000-1fe3-0008-de89      No
dgb1005.1003.0.8.1       pgb0.0.0.8.1         5000-1fe3-0008-de8d      Yes
dgb1005.1004.0.8.1       pgb0.0.0.8.1         5000-1fe3-0008-de88      No

A console initialization is required to exit the wwidmgr, and to make the device names available to the console show dev command:
```
P00>>> init
    
.
.
.
```

The device names have now been set for the Tru64 UNIX disk and first cluster member system boot disks.

In the reachability portion of the display, each storageset is reachable from KGPSA pga through two HSV110 ports and from KGPSA pgb through two HSV110 ports. Also, the device unit number has been set for each KGPSA to HSV110 controller port connection, even if the storage unit is not currently reachable via that connection.

5.2 Displaying Valid Boot Devices

The only Fibre Channel devices that are displayed by the console show dev command are those devices that have been assigned to a wwidn environment variable with the wwidmgr -quickset command.

Any device shown in the reachability display can be used as a boot device. The bootdef_dev console environment variable can be set to any, or several, of these devices. Also, the cluster installation script sets the bootdef_dev console environment variable to up to four of these devices.

If you issue the show wwid* console command now, it will show that the environment variable wwidn is set for two disks. Also, the show n* command shows that the units are accessible through four HSV110 N_Ports as follows:

P00>>> show wwid*
wwid0        1001 1 WWID:01000010:6005-08b4-0001-00b2-0000-c000-025f-0000
wwid1        1005 1 WWID:01000010:6005-08b4-0001-00b2-0000-c000-0277-0000
wwid2
wwid3               	                
P00>>>show n*
N1                  	50001fe30008de8c
N2                  	50001fe30008de89
N3                  	50001fe30008de8d
N4                  	50001fe30008de88

Example 5-3 provides sample device names as displayed by the show dev command after using the wwidmgr -quickset command to set the device unit numbers. These devices are available to use as boot devices.

Example 5-3: Sample Fibre Channel Device Names

 P00>>> show dev
dga1001.1001.0.7.0         $1$DGA1001   COMPAQ HSV110 (C)COMPAQ  1010
dga1001.1002.0.7.0         $1$DGA1001   COMPAQ HSV110 (C)COMPAQ  1010
dga1001.1003.0.7.0         $1$DGA1001   COMPAQ HSV110 (C)COMPAQ  1010
dga1001.1004.0.7.0         $1$DGA1001   COMPAQ HSV110 (C)COMPAQ  1010
dgb1001.1001.0.8.1         $1$DGB1001   COMPAQ HSV110 (C)COMPAQ  1010
dgb1001.1002.0.8.1         $1$DGB1001   COMPAQ HSV110 (C)COMPAQ  1010
dgb1001.1003.0.8.1         $1$DGB1001   COMPAQ HSV110 (C)COMPAQ  1010
dgb1001.1004.0.8.1         $1$DGB1001   COMPAQ HSV110 (C)COMPAQ  1010
dga1005.1001.0.7.0         $1$DGA1005   COMPAQ HSV110 (C)COMPAQ  1010
dga1005.1002.0.7.0         $1$DGA1005   COMPAQ HSV110 (C)COMPAQ  1010
dga1005.1003.0.7.0         $1$DGA1005   COMPAQ HSV110 (C)COMPAQ  1010
dga1005.1004.0.7.0         $1$DGA1005   COMPAQ HSV110 (C)COMPAQ  1010
dgb1005.1001.0.8.1         $1$DGB1005   COMPAQ HSV110 (C)COMPAQ  1010
dgb1005.1002.0.8.1         $1$DGB1005   COMPAQ HSV110 (C)COMPAQ  1010
dgb1005.1003.0.8.1         $1$DGB1005   COMPAQ HSV110 (C)COMPAQ  1010
dgb1005.1004.0.8.1         $1$DGB1005   COMPAQ HSV110 (C)COMPAQ  1010
dka500.5.0.2000.1          DKA500                        RRD47  1206
dkb0.0.0.2001.1            DKB0                       RZ1CD-CS  0306

.
.
.
pga0.0.0.7.0               PGA0        WWN 2000-0000-c928-2c95
pgb0.0.0.8.1               PGB0        WWN 2000-0000-c925-2c50

.
.
.

Note

The only Fibre Channel devices displayed by the console show dev command are those devices that have been assigned to a wwidn environment variable.

At this point you are ready to install the Tru64 UNIX operating system and TruCluster Server software.

5.3 Install the Base Operating System

After you read the TruCluster Server Cluster Installation manual, and using the Tru64 UNIX Installation Guide as a reference, boot from the CD-ROM and perform a full installation of the Tru64 UNIX Version 5.1B operating system.

When the installation procedure displays the list of disks that are available for operating system installation as shown here, look for the identifier in the Location column. Verify the identifier from Table 4-1.

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         4.0  SCSI        RZ1CD-CS        bus-1-targ-0-lun-0
 2)    dsk1         4.0  SCSI        RZ1CD-CS        bus-1-targ-1-lun-0
 3)    dsk2         4.0  SCSI        RZ1CD-CS        bus-1-targ-2-lun-0
 4)    dsk3         8.5  SCSI        HSZ80           bus-2-targ-1-lun-1
 5)    dsk4         8.5  SCSI        HSZ80           bus-2-targ-1-lun-2
 6)    dsk5         8.5  SCSI        HSZ80           bus-2-targ-1-lun-3
 7)    dsk6         8.5  SCSI        HSZ80           bus-2-targ-1-lun-4
 8)    dsk7         8.5  SCSI        HSZ80           bus-2-targ-1-lun-5
 9)    dsk8         8.5  SCSI        HSZ80           bus-2-targ-1-lun-6
10)    dsk9         2.0  SCSI        HSV110          IDENTIFIER=1001
11)    dsk13        3.0  SCSI        HSV110          IDENTIFIER=1005

Record the /dev/disk/dskn value (dsk9) for the Tru64 UNIX disk that matches the identifier (1001) (See Table 4-1).

Complete the installation, following the instructions in the Tru64 UNIX Installation Guide.

If you are only installing the base operating system, and not installing TruCluster Server, set the bootdef_dev console environment variable to multiple paths before you boot the operating system (see Section 5.4).

5.4 Reset the bootdef_dev Console Environment Variable

After installing the cluster software, shut down the operating system. Use the console show device command to verify that the bootdef_dev console environment variable is set to select multiple paths to the boot device and not just one path.

If it is set to select only one path to the boot device, set it to select multiple paths as follows:

Examine the reachability display provided by the wwidmgr -show reachability command for the device names that can access the storage unit from which you are booting.

Set the bootdef_dev console environment variable to provide multiple paths to the boot disk.
Notes

Choose device names that show up as both Yes and No in the reachability display connected column. Note, that for multiple-bus failover, only one controller is normally active for a storage unit. You must ensure that the unit is reachable if the controllers have failed over.
Use device names for at least two host bus adapters.
For example, to ensure that you have a connected boot path in case of a failed host bus adapter or controller failover, choose device names for multiple host bus adapters and each controller port. If you use the reachability display for member system 1's boot disk as shown in Example 5-2, you could choose any of the following device names when setting the bootdef_dev console environment variable for the first cluster member system:
```
dga1001.1001.0.7.0
dga1001.1002.0.7.0
dga1001.1003.0.7.0
dga1001.1004.0.7.0
 
dgb1001.1001.0.8.1
dgb1001.1002.0.8.1
dgb1001.1003.0.8.1
dgb1001.1004.0.8.1
 
```
If the bootdef_dev console environment variable ends up with all boot paths in an unconnected state, you can use the ffauto or ffnext console environment variables to force a boot device from a not connected to a connected state.
The ffauto console environment variable is effective only during autoboots (boots other than manual boots). Use the set ffauto on console command to enable ffauto. (The default for ffauto is off.) It is stored in nonvolatile memory so it persists across system resets and power cycles.
During an autoboot, the console attempts to boot from each connected device listed in the bootdef_dev console environment variable. If ffauto is on, and if the end of devices listed in bootdef_dev is reached without successfully booting, the console starts again at the beginning of the devices listed in the bootdef_def console environment variable. This time, devices that are not connected are changed to connected and an attempt is made to boot from that device.
The ffnext console environment variable is a one-time variable. It does not persist across a system reset, power cycle, or reboot. This variable may be used (set ffnext on) to cause the next command to a not connected device to change the state to connected. After the command has been executed, the ffnext variable is automatically set to off, so it has no further effect.
For more information on using the ffauto and ffnext console environment variables, see the Wwidmgr User's Manual.

Set the bootdef_dev console environment variable for the base operating system boot disk to a comma-separated list of several of the boot paths that show up in the reachability display (wwidmgr -show reachability). You must initialize the system to use any of the device names in the bootdef_dev variable as follows:
```
P00>>> set bootdef_dev \
dga1001.1001.0.7.0,dga1001.1002.0.7.0 \
dgb1001.1001.0.8.1,dgb1001.1002.0.8.1
POO>>> init
 
```

Note

The console System Reference Manual (SRM) software guarantees that you can set the bootdef_dev console environment variable to a minimum of four device names. You may be able to set it to five, but only four are guaranteed.

5.5 Determining /dev/disk/dskn to Use for a Cluster Installation

Before installing the TruCluster Server software, you must determine which /dev/disk/dskn to use for the various TruCluster Server disks.

To determine the /dev/disk/dskn to use for the cluster disks, follow these steps:

With the Tru64 UNIX Version 5.1B operating system at single-user or multi-user mode, use the hardware manager utility (hwmgr) with the -view devices option to display all devices on the system. Pipe the command through the grep utility to search for any items with the IDENTIFIER qualifier:

# hwmgr -view dev | grep IDENTIFIER
 HWID: Device Name          Mfg      Model            Location
 --------------------------------------------------------------------
   86: /dev/disk/dsk9c      COMPAQ   HSV110 (C)COMPAQ IDENTIFIER=1001
   87: /dev/disk/dsk10c     COMPAQ   HSV110 (C)COMPAQ IDENTIFIER=1002
   88: /dev/disk/dsk11c     COMPAQ   HSV110 (C)COMPAQ IDENTIFIER=1003
   89: /dev/disk/dsk12c     COMPAQ   HSV110 (C)COMPAQ IDENTIFIER=1004
   90: /dev/disk/dsk13c     COMPAQ   HSV110 (C)COMPAQ IDENTIFIER=1005
   91: /dev/disk/dsk14c     COMPAQ   HSV110 (C)COMPAQ IDENTIFIER=1006
   92: /dev/disk/dsk15c     COMPAQ   HSV110 (C)COMPAQ IDENTIFIER=1007

If you know that you have set the UDID for a large number of disks, you can also search for the UDID:

# hwmgr -view dev | grep IDENTIFIER | grep 1002
 HWID: Device Name          Mfg      Model            Location
 --------------------------------------------------------------------
   87: /dev/disk/dsk10c     COMPAQ   HSV110 (C)COMPAQ IDENTIFIER=1002

Search the display for the identifiers (OS unit IDs) for each of the cluster installation disks and record the /dev/disk/dskn values in Table A-1.
If you use the grep utility to search for a specific UDID, for example, hwmgr -view dev | grep IDENTIFIER=1002, repeat the command to determine the /dev/disk/dskn for each of the remaining cluster disks. Record the information for use when you install the cluster software.

You must label the disks before you install cluster software.

5.6 Label the Disks to Be Used to Create the Cluster

Before you run clu_create to create the first cluster member or clu_add_member to add subsequent cluster members, you must label the disks to be used for cluster software.

On the system where you installed the Tru64 UNIX operating system, if you have not already done so, boot the system. Determine the /dev/disk/dskn values to use for cluster installation (See Table 4-1).

Initialize disklabels for all disks needed to create the cluster. The example (See Table 4-1) uses disks dsk10 [cluster root (/)], dsk11 (/usr), dsk12 (/var), and dsk15 (Quorum). For example:

# disklabel -z dsk 10
  disklabel: Disk /dev/rdisk/dsk10c is unlabeled
#disklabel -rw dsk10 HSV110

5.7 Install the TruCluster Server Software and Create the First Cluster Member

After labeling the disks, use the TruCluster Server Cluster Installation procedures and install the TruCluster Server software on the first cluster member (the system where you just installed Tru64 UNIX).

After installing the TruCluster Server software subsets, run the clu_create command to create the first cluster member using the procedures in the TruCluster Server Cluster Installation manual.

5.8 Add Additional Systems to the Cluster

To add additional systems to the cluster, follow this procedure:

On the system where you installed the Tru64 UNIX operating system and TruCluster Server software, boot the system into the cluster as a single-member cluster.

Referring to the TruCluster Server Cluster Installation manual procedures, use clu_add_member to add a cluster member.
Before you boot the system being added to the cluster, on the newly added cluster member:
1. Use the wwidmgr utility with the -quickset option to set the device unit number for the member system boot disk as shown in Example 5-4. For member system 2 in the example configuration, it is the storage unit with OS unit ID 1006 (Table 4-1):
  Example 5-4: Setting Device Unit Number for Additional Member System
```
P00>>> wwidmgr -quickset -udid 1006
 
Disk assignment and reachability after next initialization:
 
6005-08b4-0001-00b2-0000-c000-029d-0000
                          via adapter:         via fc nport:        connected:
dga1006.1001.0.7.0       pga0.0.0.7.0         5000-1fe3-0008-de8c      No
dga1006.1002.0.7.0       pga0.0.0.7.0         5000-1fe3-0008-de89      Yes
 
dgb1006.1001.0.8.1       pgb0.0.0.8.1         5000-1fe3-0008-de8d      No
dgb1006.1002.0.8.1       pgb0.0.0.8.1         5000-1fe3-0008-de88      Yes
 
P00>>> init
 
```
2. Set the bootdef_dev console environment variable to one reachable path (Yes in the connected column of Example 5-4) to the member system boot disk:
```
P00>>> set bootdef_dev dga1006.1002.0.7.0
 
```
3. Boot genvmunix on the newly added cluster member system. Each installed subset will be configured and a new kernel will be built and installed.

Boot the new cluster member system into the cluster and complete the cluster installation.

Repeat steps 2 and 3 for other cluster member systems.