**************************************************************************************************
The contents of this email and any attachments are confidential.
They are intended for the named recipient(s) only.
If you have received this email in error please notify the system manager or the
sender immediately and do not disclose the contents to anyone or make copies.
** eSafe scanned this email for viruses, vandals and malicious content. **
**************************************************************************************************
Thanks to the following:
Martin Rønde Andersen
Dr. Thomas P. Blinn
Parkin Frank
Manish Vashi
The general consensus is that I will have to boot the original lead member (the one on which V5.1A was initially installed) from the original installation disk.
Martin pointed out that "you cannot boot a cluster member disk in a NONcluster manner", and Dr. Thomas Blinn noted "The older V4.0x based "TruCluster" was a totally different beast than what is in V5.x, so what might have worked in a V4.0x based cluster is different in V5.x."
Following is the original post:
Dear Managers,
I have a two node cluster (GS80's) running T64 V5.1A. I would like to
break this cluster for one day, and run one node as a 'standalone'
system ( ie. I do not want it running as a one member cluster. The
other node would be shutdown and powered off). After this one day
period, I would like to reform the cluster. For the moment,
clu_delete_member is not an option. The following link offers a
suggestion for TruCluster 1.5
http://www.ornl.gov/lists/mailing-lists/tru64-unix-managers/2000/02/ms
g00385.html
clubase:
cluster_disable=1
This disables the cluster from coming up once rebooted.
In 5.1A, cluster_disabel does not seem to be an attribute in the
clubase subsystem. Does 5.1A have any such attributes that will allow
me to accomplish what I want? If not, is there any way to accomplish
what I want? Thanks. frank
Received on Tue Dec 30 2003 - 17:56:54 NZDT