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
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. :(
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
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.
--
Jean-Yves Bernier
On Sun, 25 May 2014, Brian Hechinger wrote:
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. :)
-brian
I should have Mark in my config now. He shows in a neighbour list.
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
It's fixed, thanks Johnny
Verzonden vanaf mijn BlackBerry 10-smartphone.
Origineel bericht
Van: Johnny Billquist
Verzonden: zondag 25 mei 2014 20:23
Aan: hecnet at Update.UU.SE
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] bridge problem area 44
On 2014-05-25 20:16, Hans Vlems wrote:
My bridge program no longer connects to the other end. Did something change?
I had some issues about a week ago where it seemed your end was going
yo-yo all the time, so I disabled it to test things. Forgot to turn it
back on. Fixed now.
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, Dave McGuire wrote:
On 05/25/2014 10:10 AM, Cory Smelosky wrote:
Got bored of copying stuff using (virtual) serial, eh? ;)
Get an M+ system with split I/D space, and use my TCP/IP instead... :-)
If all goes well whenever Dave heads out this way he'll be dropping off
some -11s that HOPEFULLY have split I&D.
I peeked into the side vents of one of them; it has a J11 of some
sort, so you should be good there!
Sweet!
-Dave
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
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
