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

[Robert Jarratt]

"JF Mezei" <jfmezei.spamnot at vaxination.ca> wrote in message 
news:002ab826$0$20652$c3e8da3 at news.astraweb.com...
> 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.
>

The reason for standalone backup was to try booting it without using the 
DEQNA. VMS 5.4 as I understand it had only limited support for DEQNA and I 
do not know if this extended to network booting or not. Suffice to say that 
all attempts at booting VMS (7.3 and more recently 5.4) over the network 
have so far failed with a 4F SCBINT error.

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

I am sure it was you who told me that I could boot standalone backup over 
the network. Perhaps I have been doing it wrong. I could not find anything 
specific on how to boot standalone backup over the network and so I have 
been assuming that you use the same method as a satellite boot. If you can 
point me at a resource that tells me how to boot standalone backup over the 
network that would be great.

I am going back to suspecting the hardware again. I had thought that because 
it could read a TK50 and get me to the SYSBOOT prompt in a conversational 
boot that the CPU and memory must be OK. But as I am unable even to load 
MDM without a bugcheck I have to be sceptical of this now. I am going to 
start pulling out as much hardware as I can to see if I can get MDM to load 
off TK50 and run.

Thank to everyone for all your help, time and patience.

> 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.
>
>