OK,
Well, I've lots of replies and the major response was:
1) Drop one node of the cluster - clu_delete_member
2) remove the label on the dropped members boot disk
3) build the new DS20
4) add the DS20 to the cluster - clu_add_member
5) fail things over the to new DS20 member
6) repeat for other node
Thanks for all the replies.
I'll post another summery after the work is done
Paul
>Delivered-To: tru64-unix-managers_at_sws1.ctd.ornl.gov
>Sender: tru64-unix-managers-owner_at_ornl.gov
>Followup-To: poster
>X-Sender: madeline_at_postal.lightbridge.com
>X-Mailer: QUALCOMM Windows Eudora Version 5.1
>Date: Mon, 27 Aug 2001 14:21:49 -0400
>To: true 64 mail list <tru64-unix-managers_at_sws1.ctd.ornl.gov>
>From: Paul LaMadeleine <plamadeleine_at_lightbridge.com>
>Subject: downgrading hardware question
>
>Greetings,
>
> We have a two node GS160 True64 5.1 cluster. We have a SAN for
> our attached storage and boot devices. What I need to do with the
> minimum of downtime and rebuilding is convert the hardware from a GS160
> to DS20.
>
> May very basic first pass approach would be:
>
> 1) take down node "A"
> 2) remove node "A" from the SAN
> 3) attach a DS20 to the SAN
> 4) config the DS20 to boot from node "A"'s boot device
> 5) boot the DS20 and it should become node "A"
>
> Co-workers who use ALPHA's for VMS say that this is easily done
> in the vms world and they don't see why to won't work in the True64 world.
>
> Unfortunately, this is a production environment and I don't have
> a non-prod environment to test it out on.
>
> Any comments or suggestions?
>
> thanks,
>
> Paul
>
Received on Tue Aug 28 2001 - 15:21:37 NZST