Repairing the damage.

I am beginning to wonder if everybody is talking and nobody is listening. ************************************************************************ *************** * The target machine is not running anything except low level firmware !!! * * No DECNet No Tcpip No VMS - Nothing !!!! (It can't-disk drives inoperable) * ************************************************************************ *************** However after wading around in sea of online manuals I think am beginning to find out the things they don't tell you. Given that there has to be some form of communication between the Boot server and the target. Then what's left is this MOP thing. As you can specify that the boot device is the ethernet adaptor (EZA0: in this case) when you try to boot from the target system it must be sending out some kind of request packet with an ID attached. It can't be a node name or an IP address. There's no way tell it what they are!! What it does know, is its MAC address which is hard encoded into the interface. The server has to respond to the request (Remember No Decnet and No Tcpip available) somehow or other. So what is it that runs on the server does not use Decnet or Tcpip and can load images into the target machine? We can rule out @SYS$MANAGER:CLUSTER_CONFIG_LAN which expects Decnet and screw's up TCPWARE. I'm out of ideas at this point. Rod Smallwood -----Original Message----- From: cctech-bounces at classiccmp.org [mailto:cctech-bounces at classiccmp.org] On Behalf Of Dave McGuire Sent: 03 June 2007 00:44 To: General Discussion: On-Topic Posts Only Subject: Re: Repairing the damage. Importance: High On Jun 2, 2007, at 3:22 PM, Rod Smallwood wrote: You can't be serious...? Cluster-booting of VAXen is something that has been happening in thousands of multiple-VAX installations for two decades. I did it myself when I was still a teenager. It is nothing unusual. I am sorry to hear that the attempt hosed your machine. -Dave -- Dave McGuire Port Charlotte, FL