- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: New Cluser Member doesn't see EVA devices corr...
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
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
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
01-24-2007 08:11 AM
01-24-2007 08:11 AM
New Cluser Member doesn't see EVA devices correctly
First of all - there are 2 entires for each device. I had him present DGA1, and DGA3 to the new server - here is what i see - is this correct?
dga14720.14.0.10.0 $0$DGA14720 COMPAQ HSV110 (C)COMPAQ 30
dga14720.15.0.10.0 $0$DGA14720 COMPAQ HSV110 (C)COMPAQ 3028
dga25763.14.0.10.0 $0$DGA25763 COMPAQ HSV110 (C)COMPAQ 3028
dga25763.15.0.10.0 $0$DGA25763 COMPAQ HSV110 (C)COMPAQ 3028
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-24-2007 09:29 AM
01-24-2007 09:29 AM
Re: New Cluser Member doesn't see EVA devices correctly
Art
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-24-2007 09:33 AM
01-24-2007 09:33 AM
Re: New Cluser Member doesn't see EVA devices correctly
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-24-2007 09:44 AM
01-24-2007 09:44 AM
Re: New Cluser Member doesn't see EVA devices correctly
Good bedtime reading if you're having trouble sleeping ;-)
Art
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-24-2007 01:47 PM
01-24-2007 01:47 PM
Re: New Cluser Member doesn't see EVA devices correctly
for the bootdef_dev you need to list both paths if you expect it to boot from either, after the boot the OS will use both paths so it will work mostly if you put one, I highly recomend you put both though.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-24-2007 05:52 PM
01-24-2007 05:52 PM
Re: New Cluser Member doesn't see EVA devices correctly
could these 'unusual' unit ids be the result of using '- item n' instead of '-udid n' when configuring the disks with WWIDMGR ?
Normally you would do:
>>> wwidmgr -show wwid
>>> wwidmgr -quickset -udid n
(where n is the unit numer of your system disk).
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-25-2007 01:12 AM
01-25-2007 01:12 AM
Re: New Cluser Member doesn't see EVA devices correctly
There are 2 devices presented to both the existing cluster member(AVMS) and the new cluster member(BVMS).
AVMS see "DGA1", and "DGA3" at the >>> prompt; BVMS shows what you see above.
I had the EVA config. tech check the OSID and they both point to "VMS". I have powered off and on several times.
This is really baffling.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-25-2007 01:16 AM
01-25-2007 01:16 AM
Re: New Cluser Member doesn't see EVA devices correctly
Art
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-25-2007 09:09 AM
01-25-2007 09:09 AM
Re: New Cluser Member doesn't see EVA devices correctly
Assuming your switch zones and EVA hosts are defined correctly, to be able to boot from DGA1, the sequence would be:
>>> init
... wait ...
>>> wwidmgr -clear all !! clean out any previous settings
>>> wwidmgr -quickset -udid 1 !! set up for Unit ID 1
>>> wwidmgr -show ev !! to see what got set up in wwidmgr
>>> show dev !!! will look very strange here
>>> init
... wait ...
>>> show dev !!! will look normal now
>>> set bootdef_dev dg*1.*.*.*.*
>>> show bootdef_dev
>>> boot dga1
Also, if during your initialization you see "PGan: Nvram read failed", you need to init the adapters ONCE:
>>> wwidmgr -set adapter -item 9999 -topo fabric
Note: While I am an HPE Employee, all of my comments (whether noted or not), are my own and are not any official representation of the company
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-29-2007 10:01 AM
01-29-2007 10:01 AM
Re: New Cluser Member doesn't see EVA devices correctly
I have talked to HP about this and the only way we have found to make the SRM console show the vms identifier is to do a wwidmgr -quickset on each disk you need to boot from.
If you have a single system disk then you just need to do the one quickset.
I.e. $1$dga1000 is the system disk
>wwidmgr -quickset -udid 1000
If you have a shadowed systems disk dga1000, and dga1100 then
>wwidmgr -quickset -udid 1000
>wwidmgr -quickset -udid 1100
If you have these disks on different disk subsystems then use the wwidmgr -set -port command to set the correct ports (N* console variables)
Cass