UPDATE! The community will be go into read-only on April 19, 8am Pacific in preparation for migration on April 21. Read more.
UPDATE! The community will be go into read-only on April 19, 8am Pacific in preparation for migration on April 21.Read more.
Absent Member.
Absent Member.
1477 views

OES11 - Recreate the Cluster Object?

Hi to all,

In a test environment I've deleted *all* cluster related objects like
cluster ressources and so on including the cluster object himself.
Now I want to build a new cluster (new sbd partition exists, created
with sbdutil). iManager has no option to create a cluster object, yast
refuses to reconfigure the cluster services.
Shall I just create a cluster object using iManager->create
object->cluster? Or do I have to reinstall ncs entirely?

TIA
Tom


Labels (1)
0 Likes
7 Replies
Absent Member.
Absent Member.

Tom,

I think you need to reinstall NCS entirely.

BTW, you can use '/opt/novell/ncs/bin/ncs_install.py -r' to completely remove a node from a cluster on OES11. You can reinstall the node back if the removal succeeds.

Best regards,

Changju
0 Likes
Absent Member.
Absent Member.

Thank you, changju.


I've tried several times to reinstall.
De-Installed with yast, rebooted, re-installed. No configuration options
where asked during that process. Changed to 'configure enabled' in Yast,
but was told there's no configuration allowed because it's already
configured...

Now I played around with the script you mentioned later, changed some
parameters in /etc/sysconfig/novell/ncs2_oes11, without success.
Now opened a SR with Novell...

I think deleting the cluster himself was a really bad idea...

> /opt/novell/ncs/bin/ncs_install.py -r

Thank you. For OES11 it's
/opt/novell/ncs/install/ncs_install.py -r

Are those switches for ncs_install.py documented?

Tom

0 Likes
Absent Member.
Absent Member.

Tom,

The script with the -r option will delete the cluster object for you if the script is running on the last node.

I don't think the '-r' option is documented. It's mostly used in testing environments.

Regards,

Changju
0 Likes
Absent Member.
Absent Member.

Thank you, Changju. So it's useless for me, because my cluster object
has always been deleted (what seems to be the reason for my problems)

Tom
0 Likes
Absent Member.
Absent Member.

Hello Tom,

did you install the cluster completely new? Meaning that you also
installed a "fresh" SLES/OES sever and the cluster in that turn or...?
I ask because i made a mistake during installation of the cluster and
rolled back only the cluster installation and tried to reinstall only
the cluster with the nodes left installed in the tree but did not come
to an end because the reinstallation failed with the error "cluster
already configured" or unable to create split brain disk (SBD).
I ende up with a complete installation of the nodes SLES/OES.
It may also be that the cluster objects you deleted are still there,
please check with iManager in the respective ou-container for "deleted
objects" on all servers holding a repicas of that partition where the
cluster objects have been before they were deleted. If they are still
"there" please wait until they "go away".

Regards

Burkhard Wiegand
Novell Admin
Debeka-Versicherungen
D-56068 Koblenz

0 Likes
Absent Member.
Absent Member.

Am 17.10.2012 22:42, schrieb wiegandb:
Hello Wiegand,

> did you install the cluster completely new? Meaning that you also
> installed a "fresh" SLES/OES sever and the cluster in that turn or...?

Nope, just tried to remove and reinstall the cluster part via Yast->OES>ncs


> I ask because i made a mistake during installation of the cluster and
> rolled back only the cluster installation and tried to reinstall only
> the cluster with the nodes left installed in the tree but did not come
> to an end because the reinstallation failed with the error "cluster
> already configured" or unable to create split brain disk (SBD).


That's what I did amnd I get the same error. The nodes were the NCP
Server Objects and still exist, just the cluster related objects were
deleted. I created the mirrored SBD Partion before installing the
cluster again using sbdutil.

Later I tried a combination of /opt/novell/ncs/install/ncs_install.py
with a customized /etc/sysconfig/novell/ncs2_oes11 without success.

But, surprising, next morning a cluster object arises while cluster
services on both nodes are removed.

I'm not sure if clstrlib.conf, ncs2_oes11 are part of an standard
installation or were installed during ncs installation. Should those
files be removed before a fresh! cluster installation starts?

Shall I now start cluster installation again, despite there is an
'orphaned' cluster object?


> I ende up with a complete installation of the nodes SLES/OES.
> It may also be that the cluster objects you deleted are still there,
> please check with iManager in the respective ou-container for "deleted
> objects" on all servers holding a repicas of that partition where the
> cluster objects have been before they were deleted. If they are still
> "there" please wait until they "go away".


Don't know how to do so, sorry? Do you mean iMonitor->search->extended
search?
Tom

0 Likes
Absent Member.
Absent Member.

Hello,

> Don't know how to do so, sorry? Do you mean iMonitor->search->extended search?


look for the upper left of iMonitor in blue letters and search your way
through the organisational unit containers where the cluster objects
reside.
I did not get the real cause for this and ended up with a complete new
insallation even after opening a call with NTS.

Regards

Bukrhard
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.