Deleting A Cluster Resource On A Non-Master Node - Novell OPEN ENTERPRISE SERVER 2 SP 2 - CLUSTER SERVICES 1.8.7 FOR LINUX Manual

4 In eDirectory, look at the Cluster Resource objects in the Cluster container to verify that the
resource has been deleted from the Cluster container.
If necessary, you can delete the Cluster Resource object and its virtual server object manually.
In iManager, go to Directory Administration > Delete Objects, select the objects, then click
OK.

9.11.2 Deleting a Cluster Resource on a Non-Master Node

We strongly recommend that when you need to delete a cluster resource, that you do so only from
the master node in the cluster. If the resource can be migrated, migrate it to the master node and
follow the procedure in Section 9.11.1, "Deleting a Cluster Resource on a Master Node," on
page 128.
You might want to delete a cluster resource on a non-master node when deleting NSS pool and
volume resources (by using NSSMU).
If you must delete a cluster resource while it resides a non-master node, use the following
procedure:
1 Log in as the user to the non-master node where the cluster resource currently resides,
root
then open a terminal console.
2 If the cluster resource is online, offline it by entering
cluster offline resource
3 At the terminal console prompt on the non-master node, enter
/opt/novell/ncs/bin/ncs-configd.py -init
4 Look at the file
/var/opt/novell/ncs/resource-priority.conf
same information (REVISION and NUMRESOURCES) as the file on the master node.
5 Delete the resource on the non-master node by using the appropriate storage management tool:
For shared NSS pools and volumes, use NSSMU or the Storage plug-in to iManager.
For shared Linux POSIX volumes, use evmsgui.
6 In eDirectory, look at the objects in the Cluster container to verify that the resource has been
deleted from the Cluster container.
7 On the master node, log in as the
8 At the terminal console prompt on the master node, enter
/opt/novell/ncs/bin/ncs-configd.py -init
9 Look at the file
/var/opt/novell/ncs/resource-priority.conf
same information (REVISION and NUMRESOURCES) as that of the non-master node where
you deleted the cluster resource.
10 In iManager, select Clusters > Cluster Options, then browse to select the Cluster object.
11 Click Properties, select the Priorities tab, then click Apply on the Priorities page.
12 At the terminal console, enter
cluster view
The cluster view should be consistent.
13 Look at the file
/var/opt/novell/ncs/resource-priority.conf
verify that the revision number increased.
user, then open a terminal console.
root
Configuring and Managing Cluster Resources 129
to verify that it has the
to verify that it has the
on the master node to