- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Serviceguard configuration issues with PVs
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
Forums
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
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
07-02-2007 04:37 AM
07-02-2007 04:37 AM
Serviceguard configuration issues with PVs
I have three Alternate Link enabled VGs that I have distributed to both nodes and verified that both nodes can activate the VGs mount the fs and access the data. I dont have the VGs activated on both nodes at the same time of course. The issue is that I get a message that one of the VGs called vgcls02 does not have the same PV configuration on both nodes. This is absolutely the case as the actual disks are being assigned to both nodes through a SAN fabric, so there is no way I can control the physical address of the primary and alternate PV in a VG on either node. On the configuration node the PV address are (P)c136t0d2 and (A)c137t0d2 and on the second node the PV address are (P)c86t0d2 and (A)c85t0d2.
I guess the my question would be how can I resolve this issue?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-02-2007 04:40 AM
07-02-2007 04:40 AM
Re: Serviceguard configuration issues with PVs
Please provide the command that is failing and the response/error message.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-02-2007 04:43 AM
07-02-2007 04:43 AM
Re: Serviceguard configuration issues with PVs
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-02-2007 04:44 AM
07-02-2007 04:44 AM
Re: Serviceguard configuration issues with PVs
Thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-02-2007 04:52 AM
07-02-2007 04:52 AM
Re: Serviceguard configuration issues with PVs
Through much trial and error, I learned that I needed to have the same VG names on both nodes with the same minor numbers. I successfully distributed the VGs from one node to the next and been able to import, activate and mount the LVs on the second node.
Its just that when I choose to do the cluster configuration in SAM I got multiple errors. First it complained about the CD device in one of the nodes, so I removed the special file for the CD device and resolved that error. Next it gave me an error that the physical disks for vgcls02 are not configured the same on both nodes. I figured this was referring to the fact that the device paths have different addresses.
I'm not doing PVG-strict mirroring and dont know how to resolve this issue.