My Favorites


Please to see your favorites.

  • Bookmark
  • Email Document
  • Printer Friendly
  • Favorite
  • Rating:

Insertion of resources without restart of running resources (HEARTBEAT)

This document (3008353) is provided subject to the disclaimer at the end of this document.


Novell SUSE Linux Enterprise Server 10


You would like to add a resource into an existing heartbeat enviroment. But you do not want the existing resources to restart. This could be the case if a Server resource is running on a cluster and you have to add another resource that you would like to have started before this server process.

If you try to acchieve this with the Heartbeat GUI resources will be restarted, so this is not an option.


General the approach is, that you create the resource and have it running on the cluster where you want it and then add more constraints

So first you make sure that the resource will start where you will have the other resources

cibadmin -o constraints -C -x con1.xml

where con1.xml would be

which would force the new resource to run together with an existing resource "resource_IP1"

then you actually add the new resource

cibadmin -o resources -C -x insert.xml

where insert.xml is

after the insertion the resource will start. And it will start on the same node as "resource_IP1".

Then you add the other constraints

cibadmin -o constraints -C -x con2.xml

where con2.xml would be

which would force the new resource to be started after an existing resource "resource_IP1"

Issue finally a

cibadmin -S

to force a sync of the cib over the cluster.

Please keep in mind, that despite some flashing on the GUI or dis/reappearing on crm_mon you will not see any "stop" of a resource. This is the intented behaviour. All entries will only become "effective" with the next failover, when resource_IP1 will be started first and the two resources started together. This will also work and is tested in an enviroment, where you have already"resource_IP1" and "resource_IP2" and then want to insert an"resource_IP3" between them. In this case you would add another constraint

cibadmin -o constraints -C -x con3.xml

where con3.xml would be

and delete an existing constraint that forces "resource_IP2" to be started after "resource_IP1"

So the result is, that your resources where started originally

"resource_IP1" ->"resource_IP2"

and now the resources will now start in the order

"resource_IP1" ->"resource_IP3" ->"resource_IP2"

You can also do this in an ordered and colocated group. In this group you would first add a new resource to the end of the group.

cibadmin -o resources -R -x myresourcesplusnewentry.xml

where myresourcesplusnewentry.xml is a copy from the group entry from cib where you added the new resource at the end of the group.

Original group:

modified myresourcesplusnewentry.xml

and then you would in a second step change the order by

cibadmin -o resources -R -x myNEWresourcesplusneworder.xml

where myNEWresourcesplusneworder.xml would be:

This would add "resource_IP3" to the group and then move it to the top of the group.


This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.

  • Document ID:3008353
  • Creation Date:23-NOV-07
  • Modified Date:27-APR-12
    • SUSESUSE Linux Enterprise Server

Did this document solve your problem? Provide Feedback

< Back to Support Search

SUSE Support Forums

Get your questions answered by experienced Sys Ops or interact with other SUSE community experts.

Join Our Community

Support Resources

Learn how to get the most from the technical support you receive with your SUSE Subscription, Premium Support, Academic Program, or Partner Program.

SUSE Customer Support Quick Reference Guide SUSE Technical Support Handbook Update Advisories
Support FAQ

Open an Incident

Open an incident with SUSE Technical Support, manage your subscriptions, download patches, or manage user access.

Go to Customer Center