How to Breaking Cluster?

[Cem Tugrul]

Hello Forum,

i have a cluster includes 2 nodes like;
baan01:/etc/cmcluster/BAAN#cmviewcl

CLUSTER STATUS
MANCLUSTER up

NODE STATUS STATE
baan01 up running

PACKAGE STATUS STATE AUTO_RUN NODE
BAAN up running enabled baan01
OMNI up running enabled baan01

NODE STATUS STATE
baan03 down unknown

My 2 nodes hp-ux11i v1 (B.11.11)
i want to break my cluster because when you
compare 2 nodes with each other there are really big difference as Hardware between 2 nodes i mean my baan01 node is superdome and
my baan03 node is L-1000 series so in this case "Clustering" is not so meannigful but once upon a time it was done but now it is not
working efficiently so How can i break this
Cluster?What are the steps?What are the files
do i have to modify?Is there any manual bout this?
Greetings,

[Sundar_7]

You can use the cmquerycl to create the new cluster configuration with only the desired nodes and reapply the cluster conf

# cmquerycl -v -c MANCLUSTER -n baan01 > cluster.conf

On baan03

# cmhaltnode -v

Remove the reference to the baan03 from all the package configuration files

# cmgetconf -p BAAN baan.conf

# cmgetconf -p OMNI omni.conf

vi and remove all the reference to baan03 from baan.conf and omni.conf

# cmcheckconf -v -C cluster.conf -P baan.conf -P omni.conf

Halt the cluster (Not sure if you have to halt the cluster)

# cmhaltcl

# cmapplyconf -v -C cluster.conf -P baan.conf -P omni.conf

# cmviewcl

[Steven E. Protter]

You can halt the nodes and then halt the cluster. Or just halt the cluster.

To stop the cluster from automatically reforming, you have a number of options:

/etc/rc.config.d/cmcluster

Set the first variable, AUTOSTART_CMCLD=0

Now the cluster won't start at boot time.

You are then free to reconfigure, add new hardware and whatnot to rebuild your cluster the way you would like to have it built.

SEP

[Cem Tugrul]

Hi,

Thank's for your replies...
My baan03 is down i mean because of more problems i stopped a mont ago and also
power off :-)
Now i am planned a maintenance next Sunday
so your suggestions are very important for me.
When i power on my baan03 node and how probable cmviewcl command returns???
and what must i do on baan03?which files do i have to modify?etc..
Please try to be more clear..it is very important and i do not want to do wrong...

[Geoff Wild]

Remove MC/SG from baan03:

boot baan03
swremove
Change view:
View -> Change Software View -> Start With Products

Scroll down until you see "ServiceGuard"

Mark it (press space bar), then TAB, Actions -> Remove

Rgds...Geoff

[Rita C Workman · Accepted solution]

Cem,

With baan03 down...
1)reboot into single user mode
2)mount /usr
3)edit /etc/rc.config.d/cmcluster and change AUTOSTART_CMD=0 (as Stephen pointed out)
4) Now let the box come the rest of the way up, by either init 3 or another quick reboot

Now baan03 is up, but not in the cluster. You can then remove baan03 from the cluster :
Since the node (baan03) is not running as part of the cluster, just:
Edit the cluster.ascii file and remove reference to node
cmcheckconf -v -C cluster.ascii
...when clean...
cmapplyconf -v -C cluster.ascii

Now if your point is to get rid of the cluster environment entirely, then do what Stephen mentioned above....and then remove the software entirely.

Rgrds,
Rita

[Cem Tugrul]

Hi,

i do not want to get rid of my cluster
env but just want to take out my node baan03
from my cluster so in the future i want to
put another powerful&well architected hp-ux
box on my cluster near superdome for the purpose HA.
On the Other Hand,
i have EVA and SAN architecture so there are some virtual disks which are presented
to my nodes baan01&baan03 at the same time.
And also how do i modify my "zoning" because
baan03 is still on zoning.i want to use baan03's 2 host bust adapters onto my another hp-ux box.
As you seen,i face to face with "A Heavy Maintenance".
Please also post your advices about my EVA-SAN side maintenance so we can easily finish
my "Sunday Maintenance" theoretically...

Greetings,

[Mohanasundaram_1]

Hi CEM,

If I were you, I would not mix-up so many activities in a single downtime window. Do 1 at a time.

Consider using cmdeleteconf to remove your node from the cluster. Read the "description" part of the cmdeleteconf man pages to understand how you can do it.

I am not giving you the exact syntax as you should read the man page and understand what you are going to do.

The EVA LUNs can be unpresented to your BAAN03 system and that should be enough. Modifying the zone , I am not sure. But I guess this will not affect any of your functioning if you leave the zoning as it is, for the time being. I may be wrong.

With regards,
Mohan.

You can then

[Cem Tugrul]

Mohan,

you are absolutely right...Too many maintenance activities at the same time may increase risks.
Thank's...

[Cem Tugrul]

Cluster broken succesfully...