HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- single node cluster in mc/service guard
Operating System - HP-UX
1831999
Members
3020
Online
110034
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
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
09-21-2004 03:45 PM
09-21-2004 03:45 PM
single node cluster in mc/service guard
Hi Everyone,
We are planning to test it first our scripts for starting and shutting down the packages before applying into production. Is it possible to configure MC/Service Guard as single node cluster just to check just to test those scripts?
Please provide us procedure considering mc/service guard has already been installed.
Regards,
Ricky
We are planning to test it first our scripts for starting and shutting down the packages before applying into production. Is it possible to configure MC/Service Guard as single node cluster just to check just to test those scripts?
Please provide us procedure considering mc/service guard has already been installed.
Regards,
Ricky
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-21-2004 03:51 PM
09-21-2004 03:51 PM
Re: single node cluster in mc/service guard
Yes. It is possible to have single node cluster.
Please see this document for more details
http://docs.hp.com/hpux/onlinedocs/B3936-90073/B3936-90073.html
Sunil
Please see this document for more details
http://docs.hp.com/hpux/onlinedocs/B3936-90073/B3936-90073.html
Sunil
*** Dream as if you'll live forever. Live as if you'll die today ***
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-21-2004 05:41 PM
09-21-2004 05:41 PM
Re: single node cluster in mc/service guard
Hi Ricky,
Yes it is very much possible to create a single node cluster and I do it to test my serviceguard scripts. You just need to follow the same procedure that you follow for creating multiple node cluster except that you have to ignore heartbeat/cluster lock errors.
-Sri
Yes it is very much possible to create a single node cluster and I do it to test my serviceguard scripts. You just need to follow the same procedure that you follow for creating multiple node cluster except that you have to ignore heartbeat/cluster lock errors.
-Sri
You may be disappointed if you fail, but you are doomed if you don't try
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-22-2004 12:34 AM
09-22-2004 12:34 AM
Re: single node cluster in mc/service guard
Yes it is possible - I run 2 clusters like that - 1 test and one for QA. Great way to test scripts before moving to Production.
Just specify 1 node in the cmquerycl:
Here's how I did it on my test workstation:
Detailed Description :
install mc/sg from disk 5012-7838 with
add sha1, localhost to /etc/cmcluster/cmnodelist
add localhost /.rhost
cmquerycl -v -C /etc/cmcluster/sha1.ascii -n sha1
vi /etc/cmcluster/sha1.ascii
CLUSTER_NAME sha1
HEARTBEAT_INTERVAL 2000000
NODE_TIMEOUT 8000000
VOLUME_GROUP /dev/vg01
cmapplyconf -v -C /etc/cmcluster/sha1.ascii
cmapplyconf -v -P /etc/cmcluster/SOFTWARE/software.cfg
vi /etc/cmcluster/SOFTWARE/software.cfg
PACKAGE_NAME softwarepkg
NODE_NAME sha1
LOCAL_LAN_FAILOVER_ALLOWED NO
RUN_SCRIPT /etc/cmcluster/SOFTWARE/software.cntl
RUN_SCRIPT_TIMEOUT NO_TIMEOUT
HALT_SCRIPT /etc/cmcluster/SOFTWARE/software.cntl
HALT_SCRIPT_TIMEOUT NO_TIMEOUT
cmapplyconf -v -s /etc/cmcluster/SOFTWARE/software.cntl
vi /etc/cmcluster/SOFTWARE/software.cntl
VG[0]=vg01
LV[0]="/dev/vg01/lvswtool"; FS[0]="/var/software/tools"
LV[1]="/dev/vg01/lvswmisc"; FS[1]="/var/software/misc"
LV[2]="/dev/vg01/lvpatch"; FS[2]="/var/software/patch"
vi /etc/lvmrc
AUTO_VG_ACTIVATE=0
custom_vg_activation()
{
# e.g. /sbin/vgchange -a y -s
# parallel_vg_sync "/dev/vg00 /dev/vg01"
# parallel_vg_sync "/dev/vg02 /dev/vg03"
/sbin/vgchange -a y -s /dev/vg00
return 0
}
vgchange -c y vg01
cmrunpkg softwarepkg
Rgds...Geoff
Just specify 1 node in the cmquerycl:
Here's how I did it on my test workstation:
Detailed Description :
install mc/sg from disk 5012-7838 with
add sha1, localhost to /etc/cmcluster/cmnodelist
add localhost /.rhost
cmquerycl -v -C /etc/cmcluster/sha1.ascii -n sha1
vi /etc/cmcluster/sha1.ascii
CLUSTER_NAME sha1
HEARTBEAT_INTERVAL 2000000
NODE_TIMEOUT 8000000
VOLUME_GROUP /dev/vg01
cmapplyconf -v -C /etc/cmcluster/sha1.ascii
cmapplyconf -v -P /etc/cmcluster/SOFTWARE/software.cfg
vi /etc/cmcluster/SOFTWARE/software.cfg
PACKAGE_NAME softwarepkg
NODE_NAME sha1
LOCAL_LAN_FAILOVER_ALLOWED NO
RUN_SCRIPT /etc/cmcluster/SOFTWARE/software.cntl
RUN_SCRIPT_TIMEOUT NO_TIMEOUT
HALT_SCRIPT /etc/cmcluster/SOFTWARE/software.cntl
HALT_SCRIPT_TIMEOUT NO_TIMEOUT
cmapplyconf -v -s /etc/cmcluster/SOFTWARE/software.cntl
vi /etc/cmcluster/SOFTWARE/software.cntl
VG[0]=vg01
LV[0]="/dev/vg01/lvswtool"; FS[0]="/var/software/tools"
LV[1]="/dev/vg01/lvswmisc"; FS[1]="/var/software/misc"
LV[2]="/dev/vg01/lvpatch"; FS[2]="/var/software/patch"
vi /etc/lvmrc
AUTO_VG_ACTIVATE=0
custom_vg_activation()
{
# e.g. /sbin/vgchange -a y -s
# parallel_vg_sync "/dev/vg00 /dev/vg01"
# parallel_vg_sync "/dev/vg02 /dev/vg03"
/sbin/vgchange -a y -s /dev/vg00
return 0
}
vgchange -c y vg01
cmrunpkg softwarepkg
Rgds...Geoff
Proverbs 3:5,6 Trust in the Lord with all your heart and lean not on your own understanding; in all your ways acknowledge him, and he will make all your paths straight.
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
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP