Repairing the damage.

Hi I probably failed to make my self clear. 1. Yes MOP is part of a whole heap of programs that go to make up DECNET 2. MOP stands for Maintenance Operations Protocol and that what is was for. 3 It pre dates DECnet (Well at lest internally in DEC) 4. It can be run on its own. 5. It's a much lower level system than LAT or LAVC that run at the application (top) level of the OSI Model 6. It runs at the network level (Layer 3) in the seven layer OSI model 7. Of course there is a physical network and enough of a driver in the firmware in the target VAX to exchange frames with the MOP running in the boot server. (I found a list of them) So in that sense it is running a subset of Decnet. However let's not confuse a low level maintenance tool with all the good stuff the full version of Decnet gives you. 8. Its twenty-five years since I was a product manager in DEC SWS. No wonder I'm a bit hazy on this stuff! Regards Rod Smallwood -----Original Message----- From: cctech-bounces at classiccmp.org [mailto:cctech-bounces at classiccmp.org] On Behalf Of Rick Murphy Sent: 04 June 2007 14:14 To: General Discussion: On-Topic and Off-Topic Posts Subject: RE: Repairing the damage. At 04:23 PM 6/3/2007, Rod Smallwood wrote: 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. 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. 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. 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