11.3 Booting the New Cluster Member

Let's follow the instructions that were displayed at the completion of the clu_add_membercommand.

First, let's set the boot_osflags console variable.

 P00>>> set boot_osflags 'a'

Next, let's identify the boot device of the new cluster member.^[4]

 P00>>> show device Dga2.1001.0.7.1          $1$DGA2          HSG80 V86F ...

IMPORTANT

If you are using a SCSI device for your member boot disk, the location of the device on the new cluster member may differ from the location of the device as seen by the cluster member that ran the clu_add_member command. Since device naming at the operating system level is independent of the physical device location (i.e., not dependent on bus-target-lun symantics), this may potentially lead to misidentifying the device from the new member's perspective.

For example, if dsk2 (the new member's boot disk) were a SCSI disk, its location would be determined by its bus-target-lun (b-t-l) not a Fibre Channel identifier. However, the b-t-l would not determine the device name (see Chapter 7).

From the current cluster member:

 # hwmgr -v d -dsf dsk2  HWID: Device Name         Mfg         Model                 Location  -----------------------------------------------------------------------------    49: /dev/disk/dsk2c     COMPAQ      BD009635C3            bus-2-targ-0-lun-0

This equates to DKB0 at the current cluster member's console.

 >>> show dev dka0.0.0.14.0      DKA0    COMPAQ BB009235B6 B017 dka100.1.0.14.0    DKA100  COMPAQ BB009235B6 B017 dkb0.0.0.15.0      DKB0    COMPAQ BD009635C3 B017 dkb100.1.0.15.0    DKB100  COMPAQ BD009635C3 B017 dkb200.2.0.15.0    DKB200  COMPAQ BD009635C3 B017 dkb300.3.0.15.0    DKB300  COMPAQ BD009635C3 B017 dkb400.4.0.15.0    DKB400  COMPAQ BD009635C3 B017 dkb500.5.0.15.0    DKB500  COMPAQ BD009635C3 B017

There is no requirement, however, that the new system have the same bus numbering as the current cluster member. Therefore, bus 2 on member1 may be bus 3 on member2 resulting in dsk2 being seen at location DKC0 from member2's console (see Figure 11-1).

click to expand
Figure 11-1: SCSI Device Location vs. Naming

If you are unsure of the location of the device, you can locate the device from the current cluster member using the hwmgr command with "flash" option.

 # hwmgr flash light -dsf dsk2 -seconds 60 -nopause

This command will illuminate the activity light on the disk for 60 seconds (the default is 30 seconds). Note the "-nopause" option will cause the light to not flash but stay on for the duration of the command. Once you locate the device, you can physically trace the cable to the host bus adapter if needed.

It is extremely important that you know your hardware configuration.

Now let's boot the generic kernel from the new cluster member's boot device.

 P00>>> boot -file genvmunix dga2

As the new cluster member continues to boot, it will configure all installed software subsets.

 Executing Installation Tasks... *** SYSTEM CONFIGURATION *** ... [Configure installed software subsets.] [Configure installed patch kit.] ...

After all the installed software subsets are configured, a new UNIX kernel is built for the new cluster member. This new kernel is then copied into place.

 *** KERNEL CONFIGURATION AND BUILD PROCEDURE *** *** PERFORMING KERNEL BUILD *** A log file listing special device files is located in /dev/MAKEDEV.log          Working....Wed Mar 27 16:35:42 PST 2002 The new kernel is /sys/SHERIDAN/vmunix Copying new kernel to /vmunix ...

As soon as this is done, the new cluster member continues to boot to multi-user mode.

^[4]For more information on determining the boot device in a Fibre Channel switched environment and having this device seen at the SRM console, please see section 4.2.5.