- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: ServiceGuard
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
04-30-2004 05:25 PM
04-30-2004 05:25 PM
ServiceGuard
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-30-2004 06:08 PM
04-30-2004 06:08 PM
Re: ServiceGuard
0. Shutdown the cluster first.
#cmhaltcl
1. Take backup of cmclconf.ascii,cmclconfig,packageconfiguration file,package control script file for safer side.
2. Edit cmclconf.ascii to add necessary additional node information. File is self explanatory and it will explain you about every parameter you enter. You can refer to your existing node entries as well.
3. Now depending on how u r configuring the packages to run on new node, you need to make the rewuired changes in Packages configuration files.
4. Once you are done with modifying the ascii and control script as per your requirement and ensured that you have completed all tasks that your setup demands do the following:
#cmcheckconf
see man cmcheckconf "This will verify your configuration files"
5. Once you done with that without any error then :
#cmapplyconf
see man cmapplyconf " This will recreate cluster binary file for you"
6. Finally distribute this binary file and ascii configuration files to other nodes in the cluster.
7. Reboot the nodes and check for proper functioning of Cluster.
All the best.
THis is what i can tell you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-30-2004 11:53 PM
04-30-2004 11:53 PM
Re: ServiceGuard
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-01-2004 06:47 PM
05-01-2004 06:47 PM
Re: ServiceGuard
Since you are making changes in cluster configuration files and later on, you need to apply it.
In my opinion, we need to halt the cluster.
Prior to that make any changes, ensure to have good make recovery tape and getconfig output of both servers.
Cheers ..
NAVID
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-01-2004 07:51 PM
05-01-2004 07:51 PM
Re: ServiceGuard
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
05-03-2004 01:00 AM
05-03-2004 01:00 AM
Re: ServiceGuard
Use the following procedure to add a node with HP-UX commands. For this example, nodes ftsys8 and ftsys9 are already configured in a running cluster named cluster1, and you are adding node ftsys10.
Use the following command to store a current copy of the existing cluster configuration in a temporary file:
# cmgetconf -C temp.ascii
Specify a new set of nodes to be configured and generate a template of the new configuration. Specify the node name without its full domain name; for example, specify ftsys8 and not ftsys8.cup.hp.com:
# cmquerycl -C clconfig.ascii -c cluster1 \
-n ftsys8 -n ftsys9 -n ftsys10
Edit the file clconfig.ascii to check the information about the new node.
Verify the new configuration:
# cmcheckconf -C clconfig.ascii
Apply the changes to the configuration and send the new binary configuration file to all cluster nodes:
# cmapplyconf -C clconfig.ascii
Use cmrunnode to start the new node, and, if desired, set the AUTOSTART_CMCLD parameter to 1 in the /etc/rc.config.d/cmcluster file to enable the new node to join the cluster automatically each time it reboots.
Rgds...Geoff