<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
</head>
<body dir="ltr">
<div id="divtagdefaultwrapper" style="font-size:12pt;color:#000000;background-color:#FFFFFF;font-family:Calibri,Arial,Helvetica,sans-serif;">
<p>Wilm,</p>
<p><br>
</p>
<p>Very good ideas.</p>
<p><br>
</p>
<p>Using a fresh disk image I did a cluster_config this morning following AUTOGEN and netconfig. My steps were:</p>
<p><br>
</p>
<p>1) Run AUTOGEN</p>
<p>2) Run netconfig</p>
<p>3) Run AUTOGEN again just to be sure<br>
</p>
<p>4) Run cluster_config</p>
<p><br>
</p>
<p>Before I ran cluster_config, I backed up the sys14 directory because in order to remove node GUINAN, the script was going to delete sys14, which has some vital files in it. So when I added the node back in, I let it go ahead and create a default (mostly
empty) sys14. Then I deleted the sys14 it created and copied over the one that I backed up. And since I was not sure about permissions issue, I ran the following:</p>
<p><br>
</p>
<p>$ set protection=(S:RWED,O:RWED,G:RWED,W:RWED) dua0:[sys14...]*.*;* /log</p>
<br>
<p>Unfortunately, I still get the same error, unable to locate boot file.</p>
<br>
<p>Maybe there is a way to get more diagnostic information out of the VAX 4000-300 when it tries to do a network boot?</p>
<p><br>
</p>
<p>Thanks,</p>
<p>Daniel</p>
<p><br>
</p>
<div style="color: rgb(0, 0, 0);">
<div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font style="font-size:11pt" color="#000000" face="Calibri, sans-serif"><b>From:</b> Simh <simh-bounces@trailing-edge.com> on behalf of Wilm Boerhout <wboerhout@gmail.com><br>
<b>Sent:</b> Tuesday, June 21, 2016 1:42 AM<br>
<b>To:</b> simh@trailing-edge.com<br>
<b>Subject:</b> Re: [Simh] Unable to locate boot file</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">Trying to outsmart AUTOGEN and CLUSTER_CONFIG is never a good idea.
<br>
After the disk image transfer, you are no longer running a 6220, but a <br>
3900. After the disk image transfer and first (minimal) boot, you should <br>
AUTOGEN and, as you found out, NETCONFIG. Then your cluster boot master <br>
should be OK.<br>
<br>
Next, remove the VAX4000 from the cluster using CLUSTER_CONFIG, and <br>
re-add it using the same procedure. This ensures all (device) pointer <br>
and names are OK. DSVCONFIG should not be needed for the cluster <br>
satellite loads, only for serving DECserver image loads.<br>
<br>
*Wilm*<br>
<br>
<br>
Daniel Parrott schreef op 20-6-2016 om 22:16:<br>
><br>
> I have two physical systems, a VAX 6220 and a VAX 4000-300. The latter <br>
> system is set up to do a network bootstrap off the 6220 using an EZA0 <br>
> network device.<br>
><br>
><br>
> First, using vddriver and backup/image, I generated and retrieved disk <br>
> images of the RA92 drives from the 6220. With these disk images, and <br>
> specifying MicroVAX 3900 on the SimH simulator, I am able to boot up <br>
> an emulated version of the 6220 on my laptop. So far so good.<br>
><br>
><br>
> My first goal is to get the physical VAX 4000-300 to do its network <br>
> bootstrap off the emulated 6220 rather than the physical 6220. By the <br>
> way, I am running SimH 4.0 on Windows 8, it seems to work OK.<br>
><br>
><br>
> The first problem I ran into was that the simulator presents a <br>
> different network adapter to the emulated 6220 than it is accustomed <br>
> to seeing. It typically sees a "BNA-0" interface, but the simulator <br>
> uses "QNA-0", as derived from the XQA0 device. So, I found out that I <br>
> needed to run netconfig.com. When I ran that script, it brought the <br>
> circuit online.<br>
><br>
><br>
> But when I tried to do network boot of the physical VAX 4000-300 off <br>
> the emulated 6220, it kept saying 'retrying network bootstrap'. So <br>
> evidently that was not sufficient. Then I came to discover that the <br>
> 6220 uses DECserver, and there is a dsvconfig.com script. Once again, <br>
> because the simulator presented a different network device than the <br>
> 6220 was accustomed to seeing, the configuration had to be updated. <br>
> So okay, I ran the dsvconfig.com script, and made it aware of the fact <br>
> that it is now a "QNA-0" device rather than a "BNA-0" device.<br>
><br>
><br>
> So after running both netconfig.com and dsvconfig.com on the emulated <br>
> 6220, the physical 4000-300 no longer says "retrying network <br>
> bootstrap". Instead it now appears to be able to communicate, but it <br>
> says "unable to locate boot file":<br>
><br>
><br>
> >>> b eza0<br>
><br>
> (BOOT/R5:0 EZA0)<br>
><br>
><br>
> 2..<br>
><br>
> -EZA0<br>
><br>
> 1..0..<br>
><br>
><br>
> %VAXcluster-I-SYSLOAD, system loaded from node ORION (AA-00-04-00-B6-11)<br>
><br>
><br>
> %VAXcluster-F-BADOPEN, unable to locate BOOT file<br>
><br>
> ?06 HLT INST<br>
><br>
> PC = 00007395<br>
><br>
> >>><br>
><br>
><br>
> Using Wireshark, I captured some of the packets to try to glean some <br>
> more details, and I see messages like "VAXcluster-F-NOSUCHDEV, <br>
> nonexistent drive" and "VAXcluster-F-READERR, I/O error reading boot <br>
> file".<br>
><br>
><br>
> I am really stumped on this one because basically the disk images <br>
> should be one-to-one copies of what is on the physical VAX 6220, so <br>
> other than having to tell it that it has a different network adapter <br>
> (QNA-0 rather than BNA-0), why shouldn't it just work? Does SimH not <br>
> support MOP or DECserver? I did check, and the sysboot.exe file is <br>
> present in dua0:[sys14.syscommon.sysexe], and sys14 is the directory <br>
> for the VAX 4000-300 to use for its network boot. So I believe the <br>
> boot file is available.<br>
><br>
><br>
> By the way, the VAX 6220 is running VMS 5.5-2H. And I have set <br>
> VAXCLUSTER to 2.<br>
><br>
><br>
> Oh and one more thing, when the 4000-300 fails to boot, on the <br>
> simulator side of things I see the following:<br>
><br>
><br>
> %%%%%%%%%%%% OPCOM 20-JUN-2016 15:10:06.58 %%%%%%%%<br>
><br>
> Message from user DECNET on ORION<br>
><br>
> DECnet event 0.3, automatic line service<br>
><br>
> From node 4.438 (ORION), 20-JUN-2016 15:10:06.58<br>
><br>
> Circuit QNA-0, Load, Requested, Node = 4.764 (GUINAN)<br>
><br>
> File = DISK$VMSRL5:<SYS14.>, Operating system, Ethernet address = <br>
> 08-00-2B-23-9A-F4<br>
><br>
><br>
> %%%%%%%%%%%% OPCOM 20-JUN-2016 15:10:11.58 %%%%%%%%<br>
><br>
> Message from user DECNET on ORION<br>
><br>
> DECnet event 0.3, automatic line service<br>
><br>
> From node 4.438 (ORION), 20-JUN-2016 15:10:06.75<br>
><br>
> Circuit QNA-0, Load, Successful, Node = 4.764 (GUINAN)<br>
><br>
> File = DISK$VMSRL5:<SYS14.>, Operating system, Ethernet address = <br>
> 08-00-2B-23-9A-F4<br>
><br>
><br>
> %PEA0, Port has Closed Virtual Circuit - REMOTE NODE GUINAN<br>
><br>
> So it almost looks like it has done a successful load of the system <br>
> software to the 4000-300, but then the port closes presumably due to <br>
> not being able to locate the boot file.<br>
><br>
><br>
> My thoughts are that maybe:<br>
><br>
> 1) there is some other config script that needs to be run when using <br>
> disk images from one VAX system (physical 6220) to another (simulated <br>
> MicroVAX 3900)<br>
><br>
> 2) SimH on Windows 8 does not really support MOP or DECserver stuff?<br>
><br>
> 3) there is some permissions issue with the boot file (sysboot.exe?), <br>
> but since it is off a disk image (which should be a one-to-one exact <br>
> copy), how so?<br>
><br>
><br>
> Any ideas? Thanks in advance.<br>
><br>
><br>
><br>
> _______________________________________________<br>
> Simh mailing list<br>
> Simh@trailing-edge.com<br>
> <a id="LPlnk498691" href="http://mailman.trailing-edge.com/mailman/listinfo/simh">
http://mailman.trailing-edge.com/mailman/listinfo/simh</a>
<div style="margin-bottom: 20px; overflow: auto; width: 100%; text-indent: 0px;" id="LPBorder_GT_14665221200980.7923179147406461">
<table style="width: 90%; background-color: rgb(255, 255, 255); position: relative; overflow: auto; padding-top: 20px; padding-bottom: 20px; margin-top: 20px; border-top: 1px dotted rgb(200, 200, 200); border-bottom: 1px dotted rgb(200, 200, 200);" id="LPContainer_14665221200940.009999525645763119" cellspacing="0">
<tbody>
<tr style="border-spacing: 0px;" valign="top">
<td colspan="2" style="vertical-align: top; position: relative; padding: 0px; display: table-cell;" id="TextCell_14665221200950.8380592604860356">
<div id="LPRemovePreviewContainer_14665221200950.9224807099216747"></div>
<div style="top: 0px; color: rgb(0, 120, 215); font-weight: 400; font-size: 21px; font-family: "wf_segoe-ui_light","Segoe UI Light","Segoe WP Light","Segoe UI","Segoe WP",Tahoma,Arial,sans-serif; line-height: 21px;" id="LPTitle_14665221200950.4474509375536526">
<a target="_blank" href="http://mailman.trailing-edge.com/mailman/listinfo/simh" style="text-decoration: none;" id="LPUrlAnchor_14665221200960.4750342369870212">Simh Info Page - mailman.trailing-edge.com</a></div>
<div style="margin: 10px 0px 16px; color: rgb(102, 102, 102); font-weight: 400; font-family: "wf_segoe-ui_normal","Segoe UI","Segoe WP",Tahoma,Arial,sans-serif; font-size: 14px; line-height: 14px;" id="LPMetadata_14665221200960.5129091439956027">
mailman.trailing-edge.com</div>
<div style="display: block; color: rgb(102, 102, 102); font-weight: 400; font-family: "wf_segoe-ui_normal","Segoe UI","Segoe WP",Tahoma,Arial,sans-serif; font-size: 14px; line-height: 20px; max-height: 100px; overflow: hidden;" id="LPDescription_14665221200970.04303220075588399">
This list is for user discussion of issues related to simh. To see the collection of prior postings to the list, visit the Simh Archives.</div>
</td>
</tr>
</tbody>
</table>
</div>
<br>
<br>
<br>
_______________________________________________<br>
Simh mailing list<br>
Simh@trailing-edge.com<br>
<a href="http://mailman.trailing-edge.com/mailman/listinfo/simh">http://mailman.trailing-edge.com/mailman/listinfo/simh</a></div>
</span></font></div>
</div>
</body>
</html>