At 04:23 PM 6/3/2007, Rod Smallwood wrote:
Your server (the VAX 4000-200) does have to be running DECnet. Er no it
doesn't and isn't. I attended a 1976 DEC engineering meeting where this
was discussed. It just my personal memory has a long access time.
Download and run was around long before Decnet was thought of.
I'm not sure why I'm responding to this troll, but I can't resist.
The server must be running a MOP listener. That's the protocol that the
client uses when you boot the ethernet device. MOP is a DECnet
protocol. For many versions of VMS, the way you get a MOP listener is
to install DECnet. For VMS 7.0 and later, there's a separate MOP
listener that provides just that part of DECnet.
There's no Decnet or any other normal network
involved.
Crap. You MUST have a network to run a Local Area VAXcluster. You know,
a *Local Area Network*?
LAVC booting uses DECnet to boot. You can't make any of this work
without a LAN, without DECnet.
I suppose you'll keep flailing around hoping that something will work,
blaming others for your mistakes. Enjoy yourself.
I am also
beginning to suspect that the whole cluster thing is another GRH (Giant
Red Herring)
Huh? Nope, if you followed the very detailed directions you've been
given, you could diskless boot the server. You could then try to get a
disk set up and booted. Not a red herring at all.
Whats actually happening is an old diagnostic tool is
being
used to download and run a program on a remote system to exclude the
disk drives from the test.
LANCP is not an "old diagnostic tool" it's actually fairly recent.
Using CLUSTER_CONFIG as you're supposed to will use it to set up the
client download. Did you try that? Probably not.
-Rick