Filter
Top Products
b. Set the bootdef_dev console environment variable to one
reachable path (Yes in the connected column of Example 6–7) to
the member system boot disk:
P00>>> set bootdef_dev dga132.1002.0.1.0
c. Boot genvmunix on the newly added cluster member system. Each
installed subset will be configured and a new kernel will be built
and installed. After the new kernel is built, do not reboot the new
cluster member system.
2. Shut down the system and reset the bootdef_dev console environment
variable to provide multiple boot paths to the member system boot disk
as follows:
a. Obtain the device name and worldwide name for the Fibre Channel
unit from where you will boot (see Table 6–2). Ensure that you
choose the correct device name for the entity you are booting
(cluster member system 2, cluster member system 3, and so on).
b. Check the reachability display (Example 6–7) provided by the
wwidmgr -quickset command for the device names that can
access the storage unit from where you are booting. Check the
show dev command output to ensure the device name may be
assigned to the bootdef_dev console environment variable.
_________________ Notes __________________
You should choose device names that show up as both
Yes and No in the reachability display connected
column. Keep in mind, 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.
If you have multiple Fibre Channel host bus adapters,
you should 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. For example, if you
use the reachability display shown in Example 6–7, you
could choose the following device names when setting
the bootdef_dev console environment variable for the
second cluster member system:
6–56 Using Fibre Channel Storage