Technical data

Example 4-17: Setting the Device Unit Number for the First Cluster Member
Boot Disk (cont.)
6008-05F3-0001-27E0-0000-0000-B98B-007A
via adapter: via fc nport: connected:
dga106.1001.0.7.0 pga0.0.0.7.0 5008-05f3-0001-bd51 Yes
dga106.1002.0.7.0 pga0.0.0.7.0 5008-05f3-0001-bd59 No
dgb106.1001.0.8.0 pgb0.0.0.8.0 5008-05f3-0001-bd51 Yes
dgb106.1002.0.8.0 pgb0.0.0.8.0 5008-05f3-0001-bd59 No
__________________ Note ___________________
After the second member system has been added to the
cluster, you have to set the device unit number on that
system before booting.
c. 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,
although not necessarily connected, from Fibre Channel adapter pga
through two controller ports and from Fibre Channel adapter pgb through
two controller ports. Also, the device unit number has been set for each
Fibre Channel host bus adapter to controller port connection, even if the
storage unit is not currently reachable (connected) through that connection.
4.9.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 enter the show wwid* console command now, it will show that the
environment variable wwidn is set for two logical volumes. Also, the show
Preparing the MSA1000 for TruCluster Server Use 4-25