breaking a 2 node cluster in V5.1A, and rebooting a single node as a 'standalone'
From: Frank Chu-Cheong (frank_at_digi-data.com)
Date: 12/30/03
- Previous message: Shaun.Racine_at_intier.com: "ps hangs, fuser hangs, and w hangs"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Tue, 30 Dec 2003 10:29:18 -0400 To: tru64-unix-managers@ornl.gov
**************************************************************************************************
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. **
**************************************************************************************************
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/msg0
0385.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
- Previous message: Shaun.Racine_at_intier.com: "ps hangs, fuser hangs, and w hangs"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
