[Simh] Cluster communications errors

[Hunter Goatley]

On 7/20/2018 9:20 AM, Mark Pizzolato wrote:
> I agree with Paul completely here and I wonder, at least for the sake of proving
> the USB device is or is not a factor, why not merely share the host system's
> primary LAN.  Nothing special to get this to work except changing the
> ATTACH XQ argument in the configuration file.  When using that LAN interface,
> without jumping through hoops configuring internal bridging, the host won't
> be able to talk to the simh VAX instance, but I suspect that may not be a high
> priority.

No, it's not, and I hadn't done that at first because I didn't remember 
seeing the host system's primary LAN device when I first started. I must 
have just overlooked it, because it's there now, and I just booted using 
it (attach xq eth0). (I was probably so bent on using the dedicated 
device that I overlooked the primary device when I did SHOW ETHER.)

I was also mistaken about the dedicated device. It's not a USB device. 
It's actually an Intel PCI-X card that it's in the host system. Which 
now makes me even more confused. ;-)

System booted using the system's primary device and is running fine, 
though it still had the drop/re-establish when DECnet was started. But 
everything else is working just fine. No subsequent drops, DECnet, 
TCP/IP, and clustering all working as expected.

We're just going to pull the second card and run off the primary LAN device.

Thanks again for all your help!

Hunter