 |
» |
|
|
|
Ask the Wizard Questions
Cluster: Satellite boot problem
The Question is:
Satellite node will not boot. The message on the satellite
node's console is "Invalid satellite SCSSYSTEMID parameter".
Decnet messages from OPCOM which display on the load host
console show a request for load from the satellite, a
succesful load and less than one second later a
"Line open error, line communication error -
SYSTEM-F-TIMEOUT, device timeout.
MR/MS. WIZARD: Please help.
The Answer is:
From the boot server for this satellite execute the following
$ MCR NCP SHOW NODE {satellite} CHARA
From this you will see it's DECNET address and the system root at which
this system is supposed to boot . It will look something like this
Node Volatile Characteristics as of 6-FEB-1996 16:50:11
Remote node = 28.384 (XXXXXX)
Hardware address = 08-00-2B-0D-05-7D
Tertiary loader = SYS$SYSTEM:TERTIARY_VMB.EXE
Load Assist Agent = SYS$SHARE:NISCS_LAA.EXE
Load Assist Parameter = SYS$SYSDEVICE:
So this node XXXXXX boots from the disk pointed to by the boot servers
SYS$SYSDEVICE logical and root SYS7. The SYSGEN SCSSYSTEMID should be
(28*1024)+384 or 29056. Now see if this is what is really there.
$ SET DEF SYS$SYSDEVICE:[SYS7.SYSEXE]
$ MCR SYSGEN
USE VAXVMSSYS.PAR
SHOW SCSNODE
SHOW SCSSYSTEMID
In the CURRENT column you should have 29056 for SCSSYSTEMID and XXXXXX in
the SCSNODE column. If you don't then continue with the following while
still in SYSGEN
SET SCSNODE "XXXXXX"
SET SCSSYSTEMID 29056
WRITE VAXVMSSYS.PAR
EXIT
Now attempt to reboot the satellite again. Also make sure that no other
system in the cluster is using this nodename or systemid by doing a
$ SHOW CLUSTER/CONT
ADD SYS_ID ! There will be no prompt just type it in
|
