- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- Re: Finding the lun0 or boot lun
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-27-2005 01:05 PM
тАО10-27-2005 01:05 PM
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
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-27-2005 02:10 PM
тАО10-27-2005 02:10 PM
Re: Finding the lun0 or boot lun
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-27-2005 06:33 PM
тАО10-27-2005 06:33 PM
SolutionThe 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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-27-2005 07:12 PM
тАО10-27-2005 07:12 PM
Re: Finding the lun0 or boot lun
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 ./
_JB_
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-27-2005 11:53 PM
тАО10-27-2005 11:53 PM
Re: Finding the lun0 or boot lun
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-28-2005 07:20 AM
тАО10-28-2005 07:20 AM
Re: Finding the lun0 or boot lun
One more last question is when should we use
wwidmgr -quickset -udid 40
wwidmgr ├в quickset ├в item
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-28-2005 07:58 AM
тАО10-28-2005 07:58 AM
Re: Finding the lun0 or boot lun
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