Xref: utzoo comp.os.vms:8389 comp.sys.dec:769
Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!elroy!suned1!efb
From: efb@suned1.UUCP (Everett F. Batey II)
Newsgroups: comp.os.vms,comp.sys.dec
Subject: LATCP Servers (MOM$LOAD)
Summary: To chose the boot host
Keywords: DS200, MV_2, LATCP
Message-ID: <544@suned1.UUCP>
Date: 1 Sep 88 03:19:22 GMT
References: <8808311604.AA01461@ucbvax.Berkeley.EDU>
Reply-To: suned1!efb@elroy.jpl.NASA.Gov (Everett F. Batey II)
Distribution: na
Organization: NSWSES, Port Hueneme, CA
Lines: 20


I have 2 MicroVax 2s (MV2A and MV2B).  Originally MV2A was alone and first
fed my DS200s their boot loads.  Later I added MV2B.  I thought I had made
MV2B the boot host, until today when MV2A was off line from the ethernet. 
I could not reboot a DS200 server till MV2A returned.  All noticeable
conditions and parameters from SYSGEN (conn LTA0/NOADAPT), NCP, LATCP,
the DSVCONFIG.DAT databases in MOM$LOAD and the binaries are alike.  The file
protections look the same.  The servers, afterboot hold the AA-..-..-..-..-..
number of MV2A in the SHOW SERVER STATs or whichever it is that shows where 
the server booted.  The clincher that PROVES I DONT KNOW WHAT I AM DOING is
when in NCP I attempt to TRIGGER or LOAD NODE server_name VIA QNA-0.  When
I do so from MV2A, I get no errors; when I try from MV2B, I get NML... error
messages which I think pertained to line or circuit.

Would greatly appreciate some bright ideas.

-- 
 suned1!efb@elroy.JPL.Nasa.Gov   sun!tsunami!suned1!efb   efbatey@NSWSES.ARPA
    Any statements / opinions made here are mine, alone, not those of the    
    United States, the DoD, the Navy, the Congress, the Judiciary, nor ...