|
The Question is:
Wizzard,
I am attempting to replace a VAX 6420 with a VAX 6630 in a 5 node CI cluster.
That is I want to bring the 6630 up as if it was the 6420.
I use the same boot string as the 6420 except I replace the XMI:
6420 boot string
B /R5:B0000000/R3:00000064/XMI:B/NODE:0000090A DU64
6630 BOOT STRING
B /R5:B0000000/R3:0000064/XMI:C/NODE:0000090A DU64
R5= ROOT DIRECTORY, R3=SHADOW MEMBER/NODE=HSJ9
It will boot into the cluster on the 6420 fine
It will hang on the 6630
When I log into the other nodes and type show clus/cont add cir
I see the node as NEW not as member (It just hangs there)
It established a connection to quarum and the other CI nodes.
I can perform a conversational boot. (so I am getting to the disk)
I have tried 2 diffrent 6630's I got the same result.
Any Ideas ?
The Answer is :
There is insufficient detail included here for a certain explanation
of the problem, but the OpenVMS Wizard will hazard a few guesses:
Reboot the whole cluster and try again, or use a completely new
paired SCSSYSTEMID and SCSNODE specification. The OpenVMS Cluster
software remembers this pairing of values and will refuse to accept
overlapping assignments.
Confirm that VOTES and EXPECTED_VOTES are set per the OpenVMS
documentation and the details in the FAQ.
The OpenVMS Wizard will assume that the VAX 6000 model 420 system
is entirely shut down and has been reset (or powered off) when the
attempt is made to bootstrap the VAX 6000 630 system.
The OpenVMS Wizard will further assume that the maximum number of
CI nodes permitted within this cluster (parameter PAMAXPORT) is not
precluding the addition of this new CI node.
Please contact the Compaq Customer Support Center, as additional
information may/will be required to resolve this problem.
|
