- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- cmgetconf problem
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
06-17-2006 05:53 PM
06-17-2006 05:53 PM
cmgetconf problem
When i am applying cmgetconf command for getting information about cluster of 2 nodes an error shows on screen which is
cmgetconf
Warning: Volume group /dev/vgdb01 is configured differently on node node1 than on node node2
Error: Volume group /dev/vgdb01 on node node1 does not appear to have a physical volume corresponding to /dev/dsk/c12t2d0 on node node2 (12022610041134158529).
What could be the reason.
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-17-2006 07:06 PM
06-17-2006 07:06 PM
Re: cmgetconf problem
You don't have the same configuration on both nodes in /etc/cmcluster
You need to figure out which one is correct and have the same configuration files on both nodes of the cluster.
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
06-17-2006 08:57 PM
06-17-2006 08:57 PM
Re: cmgetconf problem
Do a "strings" on your /etc/lvmtab file on both nodes and look for the physical vols that belong to vgdb01. From your post it looks like node1 is either missing a physical volume or node2 has an extraneous one. Run the following commands on both nodes and post them here:
# strings /etc/lvmtab
# vgdisplay -v vgdb01
This is usually caused by adding or removing a physical vol from a clustered VG on the configuration node but NOT doing a vgexport on that node and a vgimport on the other node(s).
~cheers
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-17-2006 09:11 PM
06-17-2006 09:11 PM
Re: cmgetconf problem
Is the device (/dev/dsk/c12t2d0 ) on both nodes.
On which node was the VG created?
When the creation was done did you perform a vgexport and distributed the exported config file to the other node and imported it on the node?
Darrel
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-17-2006 11:36 PM
06-17-2006 11:36 PM
Re: cmgetconf problem
I had checked in /etc/lvmtab on both node. on database node only one entry shows /dev/dsk/c12t1d4 and on application node two entry shows /dev/dsk/c12t1d4 and /dev/dsk/c12t2d1 . On both node error device file entry i.e /dev/dsk/c12t2d0 is not found .
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-17-2006 11:56 PM
06-17-2006 11:56 PM
Re: cmgetconf problem
Does the device file exists?
If yes perform the following:
pvdisplay -v /dev/dsk/c12t2d0
To check to which VG the device belongs to.
Darrel
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-18-2006 02:46 AM
06-18-2006 02:46 AM
Re: cmgetconf problem
According to SG rules, a shared volume group should be built similarly on all nodes, which means that you build such a group on one machine and import it on all other cluster nodes with the same stuff, i.e. on one node:
vgcreate vgshared /dev/dsk/XXXX /dev/dsk/YYYY
on all other nodes:
vgimport vgshared /dev/dsk/XXXX /dev/dsk/YYYY
As you understand, disk names on different nodes may differ.
HTH
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-18-2006 05:41 PM
06-18-2006 05:41 PM
Re: cmgetconf problem
If it's the database node, then simply vgexport there, copy mapfile to the app node; remove exisiting vgdb01 there followed by a fresh vgcreate of vgdb01 and finally vgimport the mapfile on the app node. The steps are below:
1) on database node...
# vgexport -pvs -m /tmp/vgdb01.map
2) copy mapfile to the app node...
# rcp dbnode:/tmp/vgdb01.map appnode:/tmp/vgdb01.map
3) on app node note the major and minor number of vgdb01...
# ll /dev/vgdb01/group
4) remove vgdb01 on the app node...
# vgexport vgdb01
5) create vgdb01 using the major and minor numbers from step 3...
# mkdir /dev/vgdb01
# mknod /dev/vgdb01 c
6) vgimport the mapfile...
# vgimport -vs -m /tmp/vgdb01.map
7) verify if the VG is consistent on both nodes...
# strings /etc/lvmtab
~hope it helps
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-19-2006 12:34 AM
06-19-2006 12:34 AM
Re: cmgetconf problem
2) If this is an 11.23 cluster, make certain that /etc/nsswitch.conf contains the line:
ipnodes: hosts
This permits proper name resolution through the /etc/hosts file (which should be designated as the first hostname lookup path in nsswitch.conf:
hosts files [notfound] dns