[Info-vax] Trying to boot a MicroVAX II with VMS 7.3

[JF Mezei]

Robert Jarratt wrote:

> %%%%%%%%%%%  OPCOM  11-APR-2009 22:56:30.14  %%%%%%%%%%%
> Message from user DECNET on VX3900
> DECnet event 0.7, aborted service request
> From node 1.9 (VX3900), 11-APR-2009 22:56:30.13
> Circuit QNA-0, Line open error, File open error, Load file
> %LAA-F-RMTNOTCLS, remote node is not a VAXcluster member
> Node = 1.10 (MICRO1), Ethernet address = 08-00-2B-04-AE-54


I've thought about your case. Standalone backup is not necessary in your
case.

Say node1 is the boot node, and node2 is your all mighty microvax II.

You run cluster config on node1 to make node2 a satellite node, and have
node2's swap/page files created on node1 only.

When you boot node2, its physical disk should remain unused, and you
should be able to dismount it (if mounted) and mount/foreign it.

You can then use full fledged backup to copy the system disk from node1
to node2. (remember to specify /ignore=interlock ). Thereare some
caveats to copying a runnning system, but unless you have other activity
on your system than just the backup, it will work fine.

In the end, standalone backup is just a stripped down version of VMS,
and it may not support clustering.

Also note that for clustering (which may be the problem above), the
SCSNODEID needs to be calculated based on the ethernet address and vice
versa.

In the above case, decnet address 1.10 translates into 1 * 1024 + 10 =
1034 and this is the scsnodeid.





> 
> 
> 
>>
>>> [...]
>>> Load Assist Parameter    = DISK$VAXVMSRL054:<SYS10.>
>>>
>>> Do I need to just change that last parameter to point to SYSE? Or do I 
>>> need
>>> to do something else too? Note that this is now VMS 5.4.
>>
>>   _What_ is VMS V5.4?  (Yup.  I'm lost.)
> 
> The question here is referring to the boot server. The boot server is 
> running VMS 5.4 and I have created a standalone backup kit on this machine 
> (actually a SIMH 3900) which I want to make available for network booting to 
> the MicroVAX II.
> 
> 
>>
>>> PS I am beginning to strongly suspect a hardware problem with the memory.
>>
>>   If I thought that, then I'd still be trying to boot MDM off
>> a TK50.
> 
> I will try again with MDM. My last attempt with it ended thus:
> 
> uVDOS V4.0 built on 21-apr-1992  12:01
> **** Fatal Bugcheck, VAXELN V4.0 INVEXCEPTN, unhandled exception at elevated 
> ipl
>     Current Job = 00020121
> 
> 
>