SUMMARY:Added cluster member hangs on reboot

From: JC Faul <jfaul_at_mtc.com.na>
Date: Wed, 27 Mar 2002 18:07:05 +0200

Hi all,

I eventually managed to locate the problem:
On the controllers the OS connections was set as WINNT.
So when the 2nd member wanted to reboot off the clusterdisk
it had no access to the disk.
I changed that to Tru64, recreated the cluster and added members.
Cluster and both members are up.

JC Faul

-------------------------------------------
Some suggestions from the list were:

>Have you checked to make sure the cluster interconnect is working? (Lawrie
Smith)
>
>ensure you apply patch kit 1 before you clu_create, second ensure you
configure as many
>components as possible (dns,mail, nfs, ntp ...) before you clu_create.
(Bruce)
>
>This sure looks like a problem with memory channel jumper
>problem(standard/virtual hub).If virtual hub mode is being used, there can
>be only two systems. One system must be virtual hub 0 (VH0) and the other
>must be virtual hub 1 (VH1).The jumpers are right next to the
>factory/maintenance cable connector. If there are only 2 systems and memory

>channel modules are connected back to back then pls short pin 2-3 on one
>module(System A) and leave all the jumpers open on the other module(System
B). (Satheesh.B)
Received on Wed Mar 27 2002 - 16:08:57 NZST

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:43 NZDT