HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Unable to create cluster config file (11.16)
Operating System - HP-UX
1825793
Members
2429
Online
109687
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
Go to solution
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
02-19-2007 04:01 AM
02-19-2007 04:01 AM
I have 2-node SG cluster (11.16). My cmclconfig.ascii file is missing. I do have the binary one. I tried creating ascii file from one node -
node1# cmgetconf -v -c cl_name cmclconfig.ascii
The above cmd gave errors and ascii file was not created. Here are the errors.
Warning: Volume group /dev/vgTUP is configured differently on node node1 than on node node2
Warning: Volume group /dev/vgTUP is configured differently on node node2 than on node node1
Error: Volume group /dev/vgTUP on node node1 does not appear to have a physical volume corresponding to /dev/dsk/c8t11d3 on node node2 (276328611143731522).
Error: Volume group /dev/vgTUP on node node1 does not appear to have a physical volume corresponding to /dev/dsk/c10t11d3 on node node2 (276328611143731522).
Can someone give what problems I am having?
Thank you all for your replies.
Rajos
node1# cmgetconf -v -c cl_name cmclconfig.ascii
The above cmd gave errors and ascii file was not created. Here are the errors.
Warning: Volume group /dev/vgTUP is configured differently on node node1 than on node node2
Warning: Volume group /dev/vgTUP is configured differently on node node2 than on node node1
Error: Volume group /dev/vgTUP on node node1 does not appear to have a physical volume corresponding to /dev/dsk/c8t11d3 on node node2 (276328611143731522).
Error: Volume group /dev/vgTUP on node node1 does not appear to have a physical volume corresponding to /dev/dsk/c10t11d3 on node node2 (276328611143731522).
Can someone give what problems I am having?
Thank you all for your replies.
Rajos
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-19-2007 04:25 AM
02-19-2007 04:25 AM
Solution
The /etc/lvmtab on each node should contain a list of every disk/LUN that is in the volume group. Apparently, c8t11d3 and c10t11d3 are listed in lvmtab on node1 but are not listed in lvmtab on node2.
Perform an ioscan to insure the system creates disk special files for all disks that it discovers. If the disks still do not show up, look at the array or zoning software that might prevent those LUNs/paths from being seen by node2.
If the special files exist, use
# diskinfo /dev/rdsk/c8t11d3 on node2 to verify the disk is accessible. You should see information about the disk/LUN.
When you are confident that the disks are present, re-import the volume group.
If you are not certain of the disk paths that belong to vgTUP on node2, create a map file that contains the VGID at the top thus:
node2:
$ vgexport -pvs -m vgTUP.map /dev/vgTUP
$ ll /dev/vgTUP/group (record the minor number)
$ vgexport vgTUP (it must not be active on node2)
$ mkdir /dev/vgTUP ; mknod /dev/vgTUP/group c 64 0x0N0000 (where N is the minor number)
$ vgimport -vs -m vgTUP.map /dev/vgTUP
Inspect the resulting /etc/lvmtab:
$ strings /etc/lvmtab
Look for c8t11d3 and c10t11d3
When you have determined those paths have been added, do the cmgetconf again.
Perform an ioscan to insure the system creates disk special files for all disks that it discovers. If the disks still do not show up, look at the array or zoning software that might prevent those LUNs/paths from being seen by node2.
If the special files exist, use
# diskinfo /dev/rdsk/c8t11d3 on node2 to verify the disk is accessible. You should see information about the disk/LUN.
When you are confident that the disks are present, re-import the volume group.
If you are not certain of the disk paths that belong to vgTUP on node2, create a map file that contains the VGID at the top thus:
node2:
$ vgexport -pvs -m vgTUP.map /dev/vgTUP
$ ll /dev/vgTUP/group (record the minor number)
$ vgexport vgTUP (it must not be active on node2)
$ mkdir /dev/vgTUP ; mknod /dev/vgTUP/group c 64 0x0N0000 (where N is the minor number)
$ vgimport -vs -m vgTUP.map /dev/vgTUP
Inspect the resulting /etc/lvmtab:
$ strings /etc/lvmtab
Look for c8t11d3 and c10t11d3
When you have determined those paths have been added, do the cmgetconf again.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-19-2007 05:00 AM
02-19-2007 05:00 AM
Re: Unable to create cluster config file (11.16)
Thank you Stephen for your help. As you said, the lvmtab on node1 and node2 are different. One has these devices but the other does not.
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