HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: Common system disk ($1DGAn) boot problem
Operating System - OpenVMS
1828212
Members
2631
Online
109975
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
07-28-2004 05:15 PM
07-28-2004 05:15 PM
Common system disk ($1DGAn) boot problem
Hi,
I have two node cluster which is booted
with common system disk located on
subsystem.
The problem i am facing with device($$DGAn) which are located on subsystem. on both the nodes some of the devices are visible but WWID of devices are visible either of one node only.I want WWId to get visible on both the nodes .
i feel this is parameter setting problem.Any idea/suggestion is appreciated.
Thanks
Deepak
I have two node cluster which is booted
with common system disk located on
subsystem.
The problem i am facing with device($$DGAn) which are located on subsystem. on both the nodes some of the devices are visible but WWID of devices are visible either of one node only.I want WWId to get visible on both the nodes .
i feel this is parameter setting problem.Any idea/suggestion is appreciated.
Thanks
Deepak
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-28-2004 09:01 PM
07-28-2004 09:01 PM
Re: Common system disk ($1DGAn) boot problem
Deepak,
My experience comes from recently setting up my two AS1200's and an RA8000 (dual HSG80) and having a similar problem, so if your configuration differs, please take that into account.
a) Get set up so you can run wwidmgr - certain machines require you to be in diagnostic mode (like my AS1200's), if so type "set mode diag"
b) Do a "wwidmgr -show wwid" and examine the results. Do you see the devices now? If not then you should check your storage subsystem and make sure that the connection from that node is enabled. To do this:
i) First look at the connections ("Show conn") and note what the connection name(s) is for that node.
ii) If an HSG80 then at the prompt type "Show {unit}" where "[unit}" is the device which doesn't show up on the node you are currently working with. Look to see if that device is enabled for the connection from that node. If not then issue a "Set {unit} enable_access {connection(s)}" command.
iii) Execute an "Init" command at the console of your node and start over again at "a" above to check to see if the device shows up now.
c) If the device shows up then look in the listing and see if it has a udid number that is NOT "-1", if so then try executing a quickset command to set up the device like this "wwidmgr -quickset -udid {number}" Do a "show device" and see if the unit shows up. If it does then you should be set and can repeat this on the other node to make all the devices show up there.
i) If the udid is -1 for the device then check at the storage subsystem to make sure the unit has an identifier assigned. VMS requires one. This is accomplished by issuing a "set {unit} id {number}" where {number} is the unit number you want the device to have on your system. If you did have to set an identifier (though if you've booted from this device then you must have already had one set so this is probably not necessary) then issue an "Init" on the node's console and start again at step "a" above.
If this hasn't helped then your problem is beyond my meager experience and hopefully one of the more knowledgeable people here can step in. If you haven't seen it, the wwidmgr commands are documented in the "WWIDMGR User's Guide" which can be found in PDF format on your Alpha Firmware CD I haven't seen a web location for this document but maybe someone else has.
My experience comes from recently setting up my two AS1200's and an RA8000 (dual HSG80) and having a similar problem, so if your configuration differs, please take that into account.
a) Get set up so you can run wwidmgr - certain machines require you to be in diagnostic mode (like my AS1200's), if so type "set mode diag"
b) Do a "wwidmgr -show wwid" and examine the results. Do you see the devices now? If not then you should check your storage subsystem and make sure that the connection from that node is enabled. To do this:
i) First look at the connections ("Show conn") and note what the connection name(s) is for that node.
ii) If an HSG80 then at the prompt type "Show {unit}" where "[unit}" is the device which doesn't show up on the node you are currently working with. Look to see if that device is enabled for the connection from that node. If not then issue a "Set {unit} enable_access {connection(s)}" command.
iii) Execute an "Init" command at the console of your node and start over again at "a" above to check to see if the device shows up now.
c) If the device shows up then look in the listing and see if it has a udid number that is NOT "-1", if so then try executing a quickset command to set up the device like this "wwidmgr -quickset -udid {number}" Do a "show device" and see if the unit shows up. If it does then you should be set and can repeat this on the other node to make all the devices show up there.
i) If the udid is -1 for the device then check at the storage subsystem to make sure the unit has an identifier assigned. VMS requires one. This is accomplished by issuing a "set {unit} id {number}" where {number} is the unit number you want the device to have on your system. If you did have to set an identifier (though if you've booted from this device then you must have already had one set so this is probably not necessary) then issue an "Init" on the node's console and start again at step "a" above.
If this hasn't helped then your problem is beyond my meager experience and hopefully one of the more knowledgeable people here can step in. If you haven't seen it, the wwidmgr commands are documented in the "WWIDMGR User's Guide" which can be found in PDF format on your Alpha Firmware CD I haven't seen a web location for this document but maybe someone else has.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-28-2004 09:25 PM
07-28-2004 09:25 PM
Re: Common system disk ($1DGAn) boot problem
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-28-2004 09:46 PM
07-28-2004 09:46 PM
Re: Common system disk ($1DGAn) boot problem
Uwe,
Doh! Of course! Slipped my mind.
John
Doh! Of course! Slipped my mind.
John
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP