I have a VMS (7.32) cluster consisting of two Alpha 4100 using FC to HSG80 Controller/storage. I tried to add a third Alpha 4100 into the cluster. (It was running standalone VMS previously). I connected the third node all right into HSG80. Then ran cluster_config (as per the manual) on one of the existing nodes. I specified the new root (SYS2) and answered all the relevant questions.
The third node boots all right, joins the cluster and then goes itno NETCONFIG and AUTOGEN. This is where the problems start: These two procedures are trying to execute images not from the shared systems disk and the new root (i.e. $1$DGA10:[sys2....) but from the VERY TOP of the shared system disk ($1$DGA10:[sysexe]) which ofcourse does not exist and the node just hangs.
It looks that AUTOGEN and NETCONFIG did not get the information about the new root (i.e. SYS2) !?
I tried running cluster_config MANY times but always with the same result.
The procedure VMS$INITIAL-050_VMS.COM checks for the logical SYS$TOPSYS to create the correct rooted logicals names. If this logical is not defined, then the logicals e.g. SYS$SPECIFIC point towards the disk alone.
But why is this logical undefined?
Perhaps you can use SYSGEN to set OPA0 as startup file (SYSGEN> SET /STATUP=OPA0) and check (Remember to SET NOON and SPAWN, because any error logs you out).
The procedure VMS$INITIAL-050_VMS.COM checks for the logical SYS$TOPSYS to create the correct rooted logicals names. If this logical is not defined, then the logicals e.g. SYS$SPECIFIC point towards the disk alone.
But why is this logical undefined?
Perhaps you can use SYSGEN to set OPA0 as startup file (SYSGEN> SET /STARTUP=OPA0) and check (Remember to SET NOON and SPAWN, because any error logs you out).
