NCP volume with Heartbeat

[aanthonisse]

I tried to use an NCP volume in a Heartbeat2 cluster
using the instructions in the blog (Leo’s Log » Make your NCP volume highly available with heartbeat) and
Make your NCP volume highly available with heartbeat | Novell User Communities.

However, the NCP server object I have created in iManager or ConsoleOne will not get an ipaddress assigned. As a result, I can not create a corresponding Volume object in eDirectory that is linked to the clusteripadres.
A volume object is necessary to fill the attribute %home_directory with the pointer to the cluster rather than the individual server.

Can someone give me more information if and how to get this to work?

The solution was plain and simple....
Just ignore the fact that the NCP server object is invalid when you want to edit its properties.

Steps:
Create NCP server object
- Create NCP server object with the DNS name of the clusterresource

Create volume object
- Choose the NCP server object
- Choose one of the volumes (they show up if mounted on one of the clusternodes)
- Type a name for the object

Now you can use the volumeobject as a reference in other NDS objects.