- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Error while executing cmgetconf
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-04-2005 10:57 PM
07-04-2005 10:57 PM
Error: Found two volume groups with the same name /dev/vg_p01_ss01.bcv1 but different ids:
Error: One of the two VGs is configured on nodes:
john james
Error: The other VG is configured on nodes:
abraham
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-05-2005 12:16 AM
07-05-2005 12:16 AM
SolutionThe VGID is located in the /etc/lvmtab file on each server and on each disk in an LVM volume group.
Since the VG has the same name across servers, cmgetconf was probably finding an old VGID in one or more of the /etc/lvmtab files, or you in truth have two different VG's with the same name, but different VGIDs.
To see if this is true, on each of the servers in the cluster execute:
# vgexport -pvs -m
vg_p01_ss01.bcv1.map /dev/vg_p01_ss01.bcv1
At the top of the resulting file (vg_p01_ss01.bcv1.map), notice the VGID line... which contains a unique identifier for that VG.
On one of the servers, the VGID will probably be different. If it is not, then /etc/lvmtab may be out of sync across nodes. To remedy this, vgexport the VG, and re-import it (after insuring the map file is newly created)
If necessary,
# cmhaltpkg (package controlling the VG)
# strings /etc/lvmtab > lvmtab.now
# ll /dev/vg_p01_ss01.bcv1/group (record the minor number of the 'group' file - 0xNN0000)
# vgexport -vs /dev/vg_p01_ss01.bcv1
# mkdir /dev/vg_p01_ss01.bcv1
# cd /dev/vg_p01_ss01.bcv1
# mknod group c 64 0xNN0000 (use the NN recorded just above)
# vgimport -vs -m vg_p01_ss01.bcv1.map /dev/vg_p01_ss01.bcv1
Since the name of the VG includes the term 'bcv', I assume that this is an EMC BCV volume group which at one time was split off from it's primary data VG, and perhaps a vgchgid was performed to give the split-off VG a unique VGID - which is a good thing. However, I think some maintenance wasn't performed properly on some of the nodes, because either 'john' and 'james' or 'abraham' have an old VGID. Best to inspect your procedures involving this BCV to see if the VG needs to be exported on one or more machines after
re-merging it back with the primary data VG.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-05-2005 01:20 AM
07-05-2005 01:20 AM
Re: Error while executing cmgetconf
1. what will be the impact if i leave it as it is?
2. do i need to correct this before i make changes to the cluster?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-05-2005 01:53 AM
07-05-2005 01:53 AM
Re: Error while executing cmgetconf
You will not be able to make any changes to the cluster until you correct the condition because all of the cluster configuration commands will stumble on the problem.
Why is the BCV VG listed in lvmtabs where it is not activated? If it is a BCV VG, then won't it be re-merged into vg_p01_ss01 at some time?
If you don't want to permanently remove the BCV vg from the other 2 nodes, do the following:
On the node where the VG is active, create the map file per my previous steps.
Then copy the map file to the other two nodes.
Per the steps I described previously, vgexport the vg_p01_ss01.bcv1 VG from the other two nodes, and re-import it.
After this, cmgetconf should work - as well as the other cluster configuration commands.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-05-2005 02:29 AM
07-05-2005 02:29 AM
Re: Error while executing cmgetconf
I hope there is no restart of package or cluster is required for the mentioned activity?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-05-2005 03:11 AM
07-05-2005 03:11 AM
Re: Error while executing cmgetconf
vgexport/vgimport does not affect and cluster information on the LVM structures on the disk - so this should be all that you have to do to correct the problem.