<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 7/18/2018 4:18 PM, Paul Koning
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:2A49C1F8-D337-4489-89CD-30CFE4FF1016@comcast.net"><br>
<pre wrap="">You mentioned that some of this is real hardware and some is simulated. It might be helpful to post a map showing the setup, including interface models, link speeds, and switch models.</pre>
</blockquote>
<br>
I'll have to see about getting that. I think I mentioned that I'm
not physically located with the equipment.<br>
<br>
<blockquote type="cite"
cite="mid:2A49C1F8-D337-4489-89CD-30CFE4FF1016@comcast.net">
<pre wrap="">Are the interface speeds all the same? LAVC was built for 10 Mbps Ethernet, and while running it faster should be ok, running mixed speeds may create more congestion than the protocol is comfortable with.</pre>
</blockquote>
<br>
Good point.<br>
<br>
<blockquote type="cite"
cite="mid:2A49C1F8-D337-4489-89CD-30CFE4FF1016@comcast.net">
<pre wrap="">Is there any way to show packet loss counts? Can you run DECnet, and if you put a significant load on DECnet connections, do the DECnet counters show any errors?</pre>
</blockquote>
The counters I've checked via NCP and LANCP show no errors, no
collisions, no overruns.<br>
<br>
Mark wrote:<br>
<blockquote>
<pre wrap="">It might be better to hard set the Linux simh host system's port to 10Mbit
on the switch. That would help with the potential for overrunning the original
DEC hardware...
</pre>
</blockquote>
I just asked my colleague to try forcing that.<br>
<br>
And I take that back about turning on throttling not making a
difference. It has made a difference---the system is no longer
coming all the way up. I'm not sure why, as the reasons long ago
scrolled away because of all of the "lost connection" messages. I
didn't think to record them.<br>
<br>
Thanks!<br>
<br>
Hunter<br>
<br>
<br>
</body>
</html>