Highlighted
Anonymous_User Absent Member.
Absent Member.
1991 views

Removing cluster node what happens to the created pools from thatnode

Hi all,

Reading through the documentation I stumble on:
10.2 Considerations for Working with Shared NSS Pools and Volumes in
the Cluster

To create or modify volumes, home directories, Distributed File
Services junctions, or any other elements that are managed using
eDirectory objects, you must cluster migrate the pool resource back to
the node where it was created before you perform those management tasks.

What does this mean when I removed the node from the cluster? Can I no
longer manage the resource??

regards
KB
Labels (1)
0 Likes
10 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Removing cluster node what happens to the created pools fromthat node

Karel Brenkman schrieb:
> Hi all,
>
> Reading through the documentation I stumble on:
> 10.2 Considerations for Working with Shared NSS Pools and Volumes in
> the Cluster
>
> To create or modify volumes, home directories, Distributed File
> Services junctions, or any other elements that are managed using
> eDirectory objects, you must cluster migrate the pool resource back to
> the node where it was created before you perform those management tasks.
>
> What does this mean when I removed the node from the cluster? Can I no
> longer manage the resource??
>
> regards
> KB


.... and did you always know on what Node you have done this?
It isn't funny..

Thomas
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Removing cluster node what happens to the created pools fromthat node

Exactly I hope someone can explain me ... Otherwise I realy don't like it!


On 04/01/2010 06:35 PM, Thomas Reiß wrote:
> Karel Brenkman schrieb:
>> Hi all,
>>
>> Reading through the documentation I stumble on:
>> 10.2 Considerations for Working with Shared NSS Pools and Volumes in
>> the Cluster
>>
>> To create or modify volumes, home directories, Distributed File
>> Services junctions, or any other elements that are managed using
>> eDirectory objects, you must cluster migrate the pool resource back to
>> the node where it was created before you perform those management tasks.
>>
>> What does this mean when I removed the node from the cluster? Can I no
>> longer manage the resource??
>>
>> regards
>> KB

>
> ... and did you always know on what Node you have done this?
> It isn't funny..
>
> Thomas


0 Likes
Knowledge Partner
Knowledge Partner

Re: Removing cluster node what happens to the created pools

Good grief, has it always been that way?

Either I've been lucky or it doesn't seem to mess stuff up

Keep in mind right now, our cluster is NW 6.5.7/8 (not OES2 yet)

We have expanded volumes/pools on nodes that the item was not originally created on and haven't noticed anything bad.

But not sure if we've ever done anything else.

I do know we had to remove a node from the cluster a while back and "whack" it and then reinstalled it BACK into the cluster with the same name. (there was a TID or something that described how to do it and it went mostly okay).
0 Likes
RBrownCCB Absent Member.
Absent Member.

Re: Removing cluster node what happens to the created pools

Karel, I can say without any shadow of a doubt, that on OES Linux the documentation you quote is not the case. I can also say with a high certainty that it is also not the case for Netware, I just no longer have a NW cluster to test it on.
Each of clustered pool resource has its own eDirectory object which is associated with the NCS virtual NCP servers.
Using iManager you should be able to manage volumes, home directories, etc without any issue.
iManager is not even particular about how you attach it to the 'server' holding the pool, I've successfully managed cluster resources with iManager connecting to RealServerName.OU.Org, VirtualServerName.OU.org, and even ClusterName.OU.org where RealServerName is the name of whatever node the pool happens to be on right now, VirtualServerName is the name of the virtual NCP server for that resource, and ClusterName is the name of the cluster (though, that approach only shows you the pools on whatever node is holding the MasterIP)

In Short, I think the documentation must have been right at some point, but certainly isn't today.

Richard Brown // Systems Engineering Team Leader // City College Brighton and Hove
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Removing cluster node what happens to the created pools fromthatnode

On 04/01/2010 11:26 PM, RBrownCCB wrote:
>
> Karel, I can say without any shadow of a doubt, that on OES Linux the
> documentation you quote is not the case. I can also say with a high
> certainty that it is also not the case for Netware, I just no longer
> have a NW cluster to test it on.
> Each of clustered pool resource has its own eDirectory object which is
> associated with the NCS virtual NCP servers.
> Using iManager you should be able to manage volumes, home directories,
> etc without any issue.
> iManager is not even particular about how you attach it to the 'server'
> holding the pool, I've successfully managed cluster resources with
> iManager connecting to RealServerName.OU.Org, VirtualServerName.OU.org,
> and even ClusterName.OU.org where RealServerName is the name of whatever
> node the pool happens to be on right now, VirtualServerName is the name
> of the virtual NCP server for that resource, and ClusterName is the name
> of the cluster (though, that approach only shows you the pools on
> whatever node is holding the MasterIP)
>
> In Short, I think the documentation must have been right at some point,
> but certainly isn't today.
>
>

Ok,
I hope you're right. I can say that on Netware this ws not the case.
If you're so absolutely sure on OES Linux then I'm relieved!

I'will put in a note on the online documentation (!) about this

Thanx
Karel
0 Likes
gmarsh Absent Member.
Absent Member.

Re: Removing cluster node what happens to the created pools

And as a general point what I hate about the docs in many instances, where it say "do not do this or that", very often it does not say WHY one should not do it...what is the impact...I'm OK with being told to "do something" without too much explanation because it usually makes sense to "do something"...but when told to "do NOT do something", one wants to know why. And this is a perfect example.

The docs have occasionally, from time to time, been shown to be wrong, or inadequate...hopefully this is a mistake.
0 Likes
ataubman Absent Member.
Absent Member.

Re: Removing cluster node what happens to the created pools

I suggest you click on the Add Comment link on that page Novell Documentation and request it be clarified or corrected.

Andrew C Taubman (Sorry, support is not provided via e-mail) Opinions expressed above are not necessarily those of Micro Focus.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Removing cluster node what happens to the created pools

I have researched the issue with testing and have an update for you.

There were at least three bugs filed in the past where this problem was reported:

- Bug 77248 - Split/Move / NW65SP3 FCS / NCS - Vol Split only works when the target volume is on the original serv
- Bug 413213 - after migrated NSS pool, getting error when creating volume on that pool
- Bug 444644 - OES2 SP1 BUILD GMC3: Not able to create the user home directory on the cluster enabled volume


What I have learned from working with testing is that the problem occurs only if the server, pool, volume, and cluster objects are in different contexts. The recommended configuration is that they be in the same context, which is why most admins never see the problem. If the objects are in different contexts, eDirectory might not be able to find the information needed to perform the operation and you get an eDirectory error. Whether or not you might run in to this issue depends on how you have set up a cluster and whether you attempt to modify or perform management actions on the pool or volume later that involve an eDirectory object in a different context.

In light of this new information, I am updating the Novell Cluster Services Administration Guide with the following statement. This guide will be re-published the week of August 2, 2010.

10.2 Considerations for Working with Shared NSS Pools and Volumes in the Cluster
http://www.novell.com/documentation/oes2/clus_admin_lx/data/bffygy4.html

The Server, Pool, Volume, Cluster Resource, and Cluster objects should all be all in the same context.

If the objects are in different contexts, you might receive an eDirectory error when you attempt to modify the pool, create or modify the volumes, home directories, Distributed File Services junctions, or any other elements that are managed using eDirectory objects. To resolve the problem, you must cluster migrate the pool cluster resource back to the node where the pool was created in order to perform those management tasks.
0 Likes
Knowledge Partner
Knowledge Partner

Re: Removing cluster node what happens to the created pools

Thank you for updating the documentation! Much appreciated. And also thank you for taking the time to post the information here as well.
0 Likes
gmarsh Absent Member.
Absent Member.

Re: Removing cluster node what happens to the created pools

That's great, thanks for the information, most appreciated.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.