Well I tried it. The two systems were connected together with 50Ohm
co-ax and terminators at both ends. I hooked in a hub that had a BNC
connector to monitor what was going on. After running
@SYS$MANAGER:CLUSTER_CONFIG_LAN on the -200 it became a boot server
and I did a BOOT EZA0: on the -300. Both systems were talking to the
network but ignored each other.
On the console of the -300 it just printed 'Retrying Network Boot' for
ever. Hardly a surprise wth no DecNet or TCP/IP running.
Oh well back to trying to create a bootable tape and put MOP on my list
of fables and fairy stories.
Rod
-----Original Message-----
From: cctech-bounces at
classiccmp.org
[mailto:cctech-bounces at
classiccmp.org] On Behalf Of arcarlini at
iee.org
Sent: 01 June 2007 17:43
To: 'General Discussion: On-Topic and Off-Topic Posts'
Subject: RE: Bringing the VAX 4000-300 back to life.
Rod Smallwood wrote:
Sounds like a good idea. How do I do that?
You configure the 4000-200 into a cluster (of one).
Then you tell it that it will have the VAX 4000-300 as a LAVC cluster
member. Then boot the VAX 4000-300 into the cluster. Then proceed as I
outlined previously.
Antonio