- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: MC/SG newbie question
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
11-26-2003 05:15 AM
11-26-2003 05:15 AM
MC/SG newbie question
Scenario: I've got a 16 proc 8400 split up into 2 8 proc domains, it is apparently running with Clustered Volumes, using disk space from a SAN. The logical volumes are being used raw by Oracle - no filesystems are created.
I have a test whereby I just want to halt the cluster & use one node to build some actual filesystems on these raw logical vols. But when I do a cmhaltcl -f, I get an error message: "Clustered Volume Groups must be deactivated before the cluster can be halted."
1. So, my 1st question is How do I deactivate the Clustered Volume Groups?
2. Do I then have to use vgchange or something to tell the Volume Group (vg_ops) to NOT be cluster aware?
3. There doesn't seem to be any packages configured to start/stop when the cluster get's iniitiated...but is there anything else I'd need to do to the MC/SG config to tell it I don't want it to even start up upon reboot?
That's good for now, Thanks in advance!!
--Gene
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-26-2003 05:35 AM
11-26-2003 05:35 AM
Re: MC/SG newbie question
You don't need to halt the cluster to create filesystems...
To take existing ones out:
vgchange -c n /dev/vgXX
Rgds...Geoff
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-26-2003 05:43 AM
11-26-2003 05:43 AM
Re: MC/SG newbie question
# cmviewcl -v
CLUSTER STATUS
hp_rac1 up
NODE STATUS STATE
athprs01 up running
Network_Parameters:
INTERFACE STATUS PATH NAME
PRIMARY up 0/0/0/1/0 lan0
PRIMARY up 0/0/12/0/0 lan2
PRIMARY up 0/0/14/0/0 lan1
NODE STATUS STATE
athprs02 up running
Network_Parameters:
INTERFACE STATUS PATH NAME
PRIMARY up 1/0/0/1/0 lan0
PRIMARY up 1/0/12/0/0 lan1
PRIMARY up 1/0/14/0/0 lan2
#
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-26-2003 05:53 AM
11-26-2003 05:53 AM
Re: MC/SG newbie question
cmhaltnode athprs01
cmhatnode athprs02
The cmhaltcl -f should do that for you - sounds like maybe there is a volumegroup that is cluster aware - yet not in this cluster.
Check the vg's in the cluster ascii file...
Rgds...Geoff
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-26-2003 06:58 AM
11-26-2003 06:58 AM
Re: MC/SG newbie question
# cmhaltnode -f athprs01
Disabling package switching to all nodes being halted.
Warning: Do not modify or enable packages until the halt operation is completed.
Halting cluster services on node athprs01.
Unable to halt the LVM daemon on athprs01.
Clustered Volume Groups must be deactivated before the cluster can be halted.
Check the syslog file for more detailed information.
# cmhaltnode -f athprs02
Disabling package switching to all nodes being halted.
Warning: Do not modify or enable packages until the halt operation is completed.
Halting cluster services on node athprs02.
Unable to halt the LVM daemon on athprs02.
Clustered Volume Groups must be deactivated before the cluster can be halted.
Check the syslog file for more detailed information.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-26-2003 08:24 AM
11-26-2003 08:24 AM
Re: MC/SG newbie question
/etc/cmcluster
It may be called cluster.conf - but could be anything - depending on who cretaed it.
Better to grab it from the existing "live" binary:
cd /etc/cmcluster
cmquerycl -c hp_rac1 -n athprs01 -n athprs02 -C hp_rac1.ascii
To actually grab the lvm info (which will tell you which vg's are cluster aware):
cmquerycl -v -c hp_rac1 -l lvm
Rgds...Geoff
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-26-2003 07:37 PM
11-26-2003 07:37 PM
Re: MC/SG newbie question
I would suggest doing a cmviewconf, or run cmscancl, and get the info out of the cluster binary to see what is actually configured. If it does list a cluster lock VG, then do vgdisplay
then try to halt the cluster.
If this is a newly created cluster that is being tested, then I can see how this might happen.
Also, are there any processes using any of the raw lvols in hte vg? if so, you would need to stop them first (normally done from within a package).
To stop it starting on reboot, change the 1 to 0 in /etc/rc.config.d/cmcluster