Finding the lun0 or boot lun

[kkdurrani]

Hi,

is there any way to find out the boot lun for a node in a cluster. is this the disk corresponding to root3_domain#root? I need to check, compare and if needed have to create the boot_def from console.

Regards,
Karim

[Venkatesh BL]

root3_domain provided you are referring to member '3'. But, 'clu_add_member' would have set the appropriate variables, you need not do that manually.

[Han Pilmeyer · Accepted solution]

Actually, that isn't true. clu_add_member creates the boot member disk for a new node in the cluster. It doesn't run on that node, so it can not set the console variables. It will do that after you have booted from the new boot member disk, but then (by definition) you have already booted from the disk.

The easiest way to identify a disk from the console, is to set up a universal identifier. How that is done is defined by the storage you use. You can see this for instance with the command "hwmgr -v dev -dsf dsk3". The universal identifier will be under the column "location". Then at the console prompt (SRM), you can do "wwidmgr -show wwid -udid 103". Assuming the universal identifier for disk "dsk3" turns out to be "103".

If you don't have universal identifiers, then you have to use the WWID. You can get this by doing the following command "hwmgr -show scsi -full -id 253" (assuming "253" is the "hwid" for the device you found above). Then at the SRM level, you do something like "wwidmgr -show wwid | grep 0029", where you hope that "0029" is some part of the WWID that is unique for the device.

In the output of the "wwidmgr" command at the beginning of the line you see the item number between brackets, e.g. "[13]". You then define the boot device by doing "wwidmgr -clear all" and "wwidmgr -quickset -item 13". Then you can do a "wwidmgr -show reach" and use the device paths you get in the command that defines the boot device. Be sure to use paths through both adapters and from both storage controllers (depending on the array in use).

Hope this helps.

[Johan Brusche]

To suplement Han's excellent answer please also check the console wwidmgr manual WWIDMGR_Vxx.PDF on the AlphaServer firmware CDrom.

The Tru64 command "consvar -g bootdef_dev", will give you an OS-translation of the SRM entry.

Rgds,
___ Johan ./

[Ivan Ferreira]

After you find out the LUN ID as described before, you may have multiples paths to the device, specially if you have more than one HBA.

To setup the boot device for all paths use:

wwidmgr â quickset â udid 3004

Assuming ID is 3004. You will see the device names after that command, then you should run:

set bootdef_dev device_name1,device_name2,device_name3,device_name4

Or you may have problems booting if one of the paths is not available.

[kkdurrani]

Greatful to all of you for ur time. So I found the boot lun information. Rigt now we are connected to the clarion. When we boot from the console it say's "dgc24.1001.0.1 not connected" That is why we need to do clear the information and create the boot configuration again. I am attaching a text file with the information.

One more last question is when should we use

wwidmgr -quickset -udid 40

wwidmgr â quickset â item -unit

[Ivan Ferreira]

I think that you get the "not connected" message because that is not the active path, and that's why you should set all paths to the device in bootdef_def. I always use -udid:

wwidmgr -clear all

wwidmgr -quickset -udid 26

Check the output, and as there are 8 paths, run:

set bootdef_dev device1,device2,device3,device4,device5,device6,device7,device8