At 1:00 AM +0200 26/5/14, Johnny Billquist wrote:
Well, that is not the full story... :-)
10.1>NCP SHO NOD 10.2 COU
Node counters as of 30-MAR-82 00:21:30
Remote node = 10.2 (SNAKE)
1266 Seconds since last zeroed
272319 Bytes received
1723 Bytes sent
821 Messages received
373 Messages sent
1 Connects received
4 Connects sent
0 Response timeouts
0 Received connect resource errors
2 Node maximum logical links active
10.2>NCP SHO NOD 10.1 COU
Node counters as of 30-MAR-82 01:10:34
Remote node = 10.1 (SHARK)
4212 Seconds since last zeroed
13475 Bytes received
1382813 Bytes sent
2626 Messages received
5177 Messages sent
26 Connects received
2 Connects sent
73 Response timeouts
0 Received connect resource errors
3 Node maximum logical links active
Summary of my last experiments:
Node A & node B inside VirtualBox (Linux) : that's the configuration i am running since the beginning of this discussion.
Node A & node B on a same MacMini (BSD). VirtualBox out of the loop.
=> same problem.
Node A on a MacPro, node B on the MacMini. VirtualBox out of the loop again.
=> same problem.
Node A inside VirtualBox Linux (MacPro), node B on the MacMini (BSD).
=> same problem.
We can rule out VirtualBox.
We can rule out a Linux/BSD/pcap problem.
We can rule out running multiple nodes on the same host (MAC addresses, etc).
Two versions of simh were used, 3.6 and 3.9, in Mac and Linux build.
[ Note: since simh 3.7, set console pchar=37777777777 if you want to use EDT/RMD/NTD at the console, took me an hour to figure. ]
--
Jean-Yves Bernier
On Mon, 26 May 2014, Johnny Billquist wrote:
That is the minimum. I hope you generated an endnode system... :-)
I did.
Well, basically, since your system complains about GEN being too fragmented, you have just managed to start a few things before DECnet tries to start up, and there is not enough contiguous memory left around for DECnet to be happy.
VNP is the third component of DECnet management. NCP and CFE being the other two.
VNP is used to configure networking in the actual system image file, so that it is already installed and in order when you boot. That means no other stuff has yet started, and you have more clear memory to play with, so VNP can probably set you up the same way NETINS do at runtime.
Ahhh.
So, you should go over what NETINS.CMD do, and do the same thing in VNP instead, with the exception that some things cannot be done in VNP. Those steps needs to be left in a modified NETINS.CMD...
But VNP only understands a subset of the NCP commands. For all the installation parts, you instead needs to use VMR.
Now, if you don't feel comfortable with playing around with this stuff, I should warn you that you can render your system unbootable when fooling around with this.
Well, I fiddled with pool:
set /plctl
PLCTL=896.:384.:448.:51.
set /secpol
SECPOL=400.:524.:76%
Then it came up. Closing a LAT connection also doesn't cause a crash now. ;)
Memory utilisation is 78%...but I DO intend to eventually get more memory. I'm just running with half a bad board disabled. ;)
Johnny
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
On 2014-05-26 01:05, Cory Smelosky wrote:
On Mon, 26 May 2014, Johnny Billquist wrote:
Ho hum. Well, how much memory do you have, and what else have you
managed to start before this goes down?
256 Kwords. ;)
That is the minimum. I hope you generated an endnode system... :-)
There are possible solutions as well. But it might require that you
learn a little about VNP...
Well I'm staring at a (correct!) Manager's Guide, so I'm not opposed to
that.
Well, basically, since your system complains about GEN being too fragmented, you have just managed to start a few things before DECnet tries to start up, and there is not enough contiguous memory left around for DECnet to be happy.
VNP is the third component of DECnet management. NCP and CFE being the other two.
VNP is used to configure networking in the actual system image file, so that it is already installed and in order when you boot. That means no other stuff has yet started, and you have more clear memory to play with, so VNP can probably set you up the same way NETINS do at runtime.
So, you should go over what NETINS.CMD do, and do the same thing in VNP instead, with the exception that some things cannot be done in VNP. Those steps needs to be left in a modified NETINS.CMD...
But VNP only understands a subset of the NCP commands. For all the installation parts, you instead needs to use VMR.
Now, if you don't feel comfortable with playing around with this stuff, I should warn you that you can render your system unbootable when fooling around with this.
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
On Mon, 26 May 2014, Johnny Billquist wrote:
Ho hum. Well, how much memory do you have, and what else have you managed to start before this goes down?
256 Kwords. ;)
There are possible solutions as well. But it might require that you learn a little about VNP...
Well I'm staring at a (correct!) Manager's Guide, so I'm not opposed to that.
Johnny
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
On 2014-05-25 22:47, Cory Smelosky wrote:
Okay. Copied!
However...
NTL -- Config File -- Partition GEN Too Fragmented
PAR$DF ,GEN,15.,TOP,2.,12.
NCP -- Set failed, operation failure
Network Initializer function failed
It seems its a big too big. :(
Ho hum. Well, how much memory do you have, and what else have you managed to start before this goes down?
There are possible solutions as well. But it might require that you learn a little about VNP...
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
On 2014-05-25 23:05, Bob Armstrong wrote:
From the VMS log on LEGATO -
%%%%%%%%%%% OPCOM 25-MAY-2014 14:01:52.62 %%%%%%%%%%%
Message from user DECNET on LEGATO
DECnet event 4.18, adjacency down
On 2014-05-25 21:54, Jean-Yves Bernier wrote:
At 8:27 PM +0200 25/5/14, Johnny Billquist wrote:
More interesting would be to see EXEC COUNTERS, as well as counters
for the two nodes, from both sides.
Full story:
-----------------------
NCP SHO EXE COUNT
Node counters as of 30-MAR-82 00:20:53
Executor node = 10.1 (SHARK)
0 Buffer unavailable
0 Peak logical links active
0 Aged packet loss
0 Node unreachable packet loss
0 Node out-of-range packet loss
0 Oversized packet loss
0 Packet format error
0 Partial routing update loss
0 Verification reject
NCP SHO LINE QNA-0 COUNT
Line counters as of 30-MAR-82 00:20:56
Line = QNA-0
1242 Seconds since last zeroed
5309886 Bytes received
270380 Bytes sent
73284 Multicast bytes received
13435 Data blocks received
6356 Data blocks sent
240 Multicast blocks received
0 Blocks sent, single collision
0 Blocks sent, multiple collision
0 Send failure
0 Collision detect check failure
0 Receive failure
1 Unrecognized frame destination
23 Data overrun
0 System buffer unavailable
-----------------------
NCP SHO EXE COUNT
Node counters as of 30-MAR-82 00:20:56
Executor node = 10.2 (SNAKE)
0 Buffer unavailable
0 Peak logical links active
0 Aged packet loss
0 Node unreachable packet loss
0 Node out-of-range packet loss
0 Oversized packet loss
0 Packet format error
0 Partial routing update loss
0 Verification reject
NCP SHO LINE QNA-0 COUNT
Line counters as of 30-MAR-82 00:20:59
Line = QNA-0
1244 Seconds since last zeroed
359441 Bytes received
5259859 Bytes sent
73238 Multicast bytes received
6352 Data blocks received
13533 Data blocks sent
239 Multicast blocks received
0 Blocks sent, single collision
0 Blocks sent, multiple collision
0 Send failure
0 Collision detect check failure
0 Receive failure
0 Unrecognized frame destination
0 Data overrun
0 System buffer unavailable
-----------------------
10.1 runs NFT.
10.2 runs FAL.
Well, that is not the full story... :-)
Now, on 10.1:
NCP SHO NOD 10.2 COU
and on node 10.2:
NCP SHO NOD 10.1 COU
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
On Sun, 25 May 2014, Cory Smelosky wrote:
Okay. Copied!
However...
NTL -- Config File -- Partition GEN Too Fragmented
PAR$DF ,GEN,15.,TOP,2.,12.
NCP -- Set failed, operation failure
Network Initializer function failed
It seems its a big too big. :(
It'd be nice if bigger memory boards on ebay weren't $250. :(
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
Oh, right. Now I remember. Maybe I'll have some time later this week. I'll let you know.
-brian
On May 25, 2014, at 15:21, Cory Smelosky <b4 at gewt.net> wrote:
On Sun, 25 May 2014, Brian Hechinger wrote:
On Sun, May 25, 2014 at 11:56:20PM +0800, Tim Sneddon wrote:
Thanks for the mention Brian. Yes, I am happy to help out. I'm not sure
what is going on with Cory's tunnel to you, but I certainly have mine
working:
a12rtr#show decnet neigh
Net Node Interface MAC address Flags
0 9.1023 Tunnel52 0000.0000.0000 A
I have compared our tunnel configs and they are both the same, so I'm
guessing it is a Cory's end.
Cory, let me know if you want some help fixing this, although it seems your
up to your eyeballs in it with your 11/23+.
The issue isn't tunnels, exactly. It's the fact that I currently can't
contact Cory's router via SNMP to push the new config to. This doesn't
affect people like you who's tunnel config is still correct but does
affect someone like me who's IP has changed so Cory's router can no
longer talk to me. And I can't update it because his router refuses to
talk to me. :)
Oh, SNMP push works. TFTP doesn't.
-brian
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
From the VMS log on LEGATO -
%%%%%%%%%%% OPCOM 25-MAY-2014 14:01:52.62 %%%%%%%%%%%
Message from user DECNET on LEGATO
DECnet event 4.18, adjacency down
