HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Single Node ServiceGuard Cluster
Operating System - HP-UX
1828667
Members
1808
Online
109984
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
07-28-2010 10:07 PM
07-28-2010 10:07 PM
Single Node ServiceGuard Cluster
Hello ServiceGuard Experts !!!
Is it possible to make a single node ServiceGuard Cluster?
There is just one hardware. No VM's.
I just want to test some ServiceGuard functionality like Application monitoring and also learn to use it.
Also I do not want to go into the intracacies of having shared-disks at this moment atleast.
Really do not want to use it for Application Failovers as of now atleast.
Is it possible to make a single node ServiceGuard Cluster?
There is just one hardware. No VM's.
I just want to test some ServiceGuard functionality like Application monitoring and also learn to use it.
Also I do not want to go into the intracacies of having shared-disks at this moment atleast.
Really do not want to use it for Application Failovers as of now atleast.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-28-2010 10:23 PM
07-28-2010 10:23 PM
Re: Single Node ServiceGuard Cluster
Hi there
Yes you can setup one node cluster, there is no problem there.
there are few discussions already on this forum, you can search single node cluster to find them
here is one
http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1185124
Yes you can setup one node cluster, there is no problem there.
there are few discussions already on this forum, you can search single node cluster to find them
here is one
http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1185124
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-29-2010 04:26 AM
07-29-2010 04:26 AM
Re: Single Node ServiceGuard Cluster
Yes. It is possible to create a 1-node cluster.
After the SG software and patch is installed,
# cd /etc/cmcluster
# cmquerycl -C cluster.config -n" to create a cluster configuration file.
If you don't plan to have any storage, you can leave the cluster.config file as-is and perform a cmapplyconf to build the cluster.
Use cmruncl to start the cluster. The only thing a package-less cluster will do is provide standby LAN failover, if any were configured in the cmapplyconf (check the comments in the cluster.config file).
If/when you decide to create a package that uses disks, you can add the LVM VG name to the cluster.config file using a VOLUME_GROUP reference and cmapplyconf the file to "clusterize" the VG.
To create a package, start with
# mkdir /etc/cmcluster/
# cd /etc/cmcluster/
# cmmakepkg -n
Then edit the pkgName.config file, uncommenting those resources that you want the package to use and add values as needed such as
vg /dev/vg02
If you plan on having the package start an application, you will likely need to reference an external start/stop script for the application in the pkgName.config file.
Add a reference to the external prescript. Example:
external_pre_script /etc/cmcluster//
Then copy the external script template and edit it:
# cp ../examples/external_script.template /etc/cmcluster//
Edit the appControl.sh to perform the application startup and shutdown functions needed at package start and stop events.
When you get to this point, add the package to the cluster:
# cmapplyconf -P
NOTE: If you have a complex startup application such as Oracle that has prebuilt start/stop functions in the Enterprise Cluster Master toolkit, don't use the external script method, but install the ECM product and use the README in it (eg. /opt/cmcluster/toolkit/oracle/README) to implement the package.
If all went properly, start the package with
# cmrunpkg
After the SG software and patch is installed,
# cd /etc/cmcluster
# cmquerycl -C cluster.config -n
If you don't plan to have any storage, you can leave the cluster.config file as-is and perform a cmapplyconf to build the cluster.
Use cmruncl to start the cluster. The only thing a package-less cluster will do is provide standby LAN failover, if any were configured in the cmapplyconf (check the comments in the cluster.config file).
If/when you decide to create a package that uses disks, you can add the LVM VG name to the cluster.config file using a VOLUME_GROUP reference and cmapplyconf the file to "clusterize" the VG.
To create a package, start with
# mkdir /etc/cmcluster/
# cd /etc/cmcluster/
# cmmakepkg -n
Then edit the pkgName.config file, uncommenting those resources that you want the package to use and add values as needed such as
vg /dev/vg02
If you plan on having the package start an application, you will likely need to reference an external start/stop script for the application in the pkgName.config file.
Add a reference to the external prescript. Example:
external_pre_script /etc/cmcluster/
Then copy the external script template and edit it:
# cp ../examples/external_script.template /etc/cmcluster/
Edit the appControl.sh to perform the application startup and shutdown functions needed at package start and stop events.
When you get to this point, add the package to the cluster:
# cmapplyconf -P
NOTE: If you have a complex startup application such as Oracle that has prebuilt start/stop functions in the Enterprise Cluster Master toolkit, don't use the external script method, but install the ECM product and use the README in it (eg. /opt/cmcluster/toolkit/oracle/README) to implement the package.
If all went properly, start the package with
# cmrunpkg
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-29-2010 05:22 AM
07-29-2010 05:22 AM
Re: Single Node ServiceGuard Cluster
>>>Is it possible to make a single node ServiceGuard Cluster?
Yes, it's possible to make a single node ServicegGuard cluster.
Have a look at following to find more details about Managing Serviceguard:
http://bizsupport1.austin.hp.com/bc/docs/support/SupportManual/c02057890/c02057890.pdf
Regards,
Bhadresh
Yes, it's possible to make a single node ServicegGuard cluster.
Have a look at following to find more details about Managing Serviceguard:
http://bizsupport1.austin.hp.com/bc/docs/support/SupportManual/c02057890/c02057890.pdf
Regards,
Bhadresh
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