On 07/04/2014 08:17, Johnny Billquist wrote:
On 2014-04-06 23:24, Mark Wickens wrote:
On 06/04/2014 20:54, zonnet wrote:
What do you get on:
$ Mc ncp sho node mim all
$ Mc ncp sho node 1.13 all
$ mcr ncp show node mim
Node Volatile Summary as of 6-APR-2014 21:22:58
%NCP-W-UNRCMP, Unrecognized component , Node
$ mcr ncp show node mim all
%NCP-E-SYNTAX, command syntax error
MIM \ALL\
$
$ mcr ncp show node 1.13
Node Volatile Summary as of 6-APR-2014 21:24:20
Node State Active Delay Circuit Next node
Links
1.13 unreachable
$
Two comments:
1) 1.13 unreachable seems like you have some kind of a connectivity problem.
2) Based on the effect of various commands: are you running phase V?
If so, the NCP command there is just a wrapper, and only supports a subset of NCP, and you are pretty screwed.
Johnny
Hi folks
Well I'm not sure what order of events prevented decnet working yesterday but I booted TSR2 this morning and hecnet connectivity was working.
Yesterday TSR2 was booted before the decnet bridge was up and running, I wonder if that caused any issues?
Regards, Mark.
--
http://www.wickensonline.co.ukhttp://hecnet.euhttp://declegacy.org.ukhttp://retrochallenge.nethttps://twitter.com/urbancamo
On 2014-04-06 23:24, Mark Wickens wrote:
On 06/04/2014 20:54, zonnet wrote:
What do you get on:
$ Mc ncp sho node mim all
$ Mc ncp sho node 1.13 all
$ mcr ncp show node mim
Node Volatile Summary as of 6-APR-2014 21:22:58
%NCP-W-UNRCMP, Unrecognized component , Node
$ mcr ncp show node mim all
%NCP-E-SYNTAX, command syntax error
MIM \ALL\
$
$ mcr ncp show node 1.13
Node Volatile Summary as of 6-APR-2014 21:24:20
Node State Active Delay Circuit Next node
Links
1.13 unreachable
$
Two comments:
1) 1.13 unreachable seems like you have some kind of a connectivity problem.
2) Based on the effect of various commands: are you running phase V?
If so, the NCP command there is just a wrapper, and only supports a subset of NCP, and you are pretty screwed.
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 4/5/2014 5:21 PM, Dave McGuire wrote:
No I don't. The one you're probably thinking of is the 8250...Very
different.
-Dave
You have an 8250? Neat! When I was System Mangler for Depauw University we replaced our VAX-11/780 with a dual 8350 cluster in 1987. Had a HSC50 and two RA81's and an RA60 for storage.
John H. Reinhardt
--
DECtec mailing list
http://dectec.info
To unsubscribe from this list see page at: http://dectec.info/mailman/listinfo/dectec_dectec.info
What?
We didn't hear you.
Also Google Mail has issues with your messages to the other list.
-----
Gregg C Levine gregg.drwho8 at gmail.com
"This signature fought the Time Wars, time and again."
On Sun, Apr 6, 2014 at 9:00 PM, John H. Reinhardt
<johnhreinhardt at yahoo.com> wrote:
test
On 06/04/2014 20:54, zonnet wrote:
What do you get on:
$ Mc ncp sho node mim all
$ Mc ncp sho node 1.13 all
$ mcr ncp show node mim
Node Volatile Summary as of 6-APR-2014 21:22:58
%NCP-W-UNRCMP, Unrecognized component , Node
$ mcr ncp show node mim all
%NCP-E-SYNTAX, command syntax error
MIM \ALL\
$
$ mcr ncp show node 1.13
Node Volatile Summary as of 6-APR-2014 21:24:20
Node State Active Delay Circuit Next node
Links
1.13 unreachable
$
--
http://www.wickensonline.co.ukhttp://hecnet.euhttp://declegacy.org.ukhttp://retrochallenge.nethttps://twitter.com/urbancamo
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On
Behalf Of Mark Wickens
Sent: 06 April 2014 20:46
To: hecnet at Update.UU.SE
Subject: [HECnet] Problems getting decnet configured on IA64 VMS 8.4
Hi folks
I'm missing something here that will probably be obvious when pointed out.
Currently commissioning TSR2 (decnet 4.12) I'm having trouble copying the
known nodes database from MIM.
SIMVAX is also running and reporting good connectivity, so this isn't
bridge
related.
$ SHOW NETWORK
Product: DECNET Node: TSR2 Address(es): 4.12
Product: TCP/IP Node: tsr2.hecnet.eu Address(es):
192.168.1.151
NCP>set node 1.13 name mim
%NCP-W-INVPVA, Invalid parameter value , Address
NCP>list circuit *
Known Circuit Permanent Summary as of 6-APR-2014 19:43:03
Circuit State
EWA-0 on
EWA-1 on
NCP>list executor
Node Permanent Summary as of 6-APR-2014 19:43:54
Executor node = 4.12 (TSR2)
State = on
Thanks, Mark.
--
http://www.wickensonline.co.ukhttp://hecnet.euhttp://declegacy.org.ukhttp://retrochallenge.nethttps://twitter.com/urbancamo
I think it means you already have a node defined at 1.13
Regards
Rob
Btw does the define command do work?
Verzonden vanaf mijn BlackBerry 10-smartphone.
Origineel bericht
Van: Mark Wickens
Verzonden: zondag 6 april 2014 21:46
Aan: hecnet at Update.UU.SE
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: [HECnet] Problems getting decnet configured on IA64 VMS 8.4
Hi folks
I'm missing something here that will probably be obvious when pointed out.
Currently commissioning TSR2 (decnet 4.12) I'm having trouble copying
the known nodes database from MIM.
SIMVAX is also running and reporting good connectivity, so this isn't
bridge related.
$ SHOW NETWORK
Product: DECNET Node: TSR2 Address(es): 4.12
Product: TCP/IP Node: tsr2.hecnet.eu Address(es):
192.168.1.151
NCP>set node 1.13 name mim
%NCP-W-INVPVA, Invalid parameter value , Address
NCP>list circuit *
Known Circuit Permanent Summary as of 6-APR-2014 19:43:03
Circuit State
EWA-0 on
EWA-1 on
NCP>list executor
Node Permanent Summary as of 6-APR-2014 19:43:54
Executor node = 4.12 (TSR2)
State = on
Thanks, Mark.
--
http://www.wickensonline.co.ukhttp://hecnet.euhttp://declegacy.org.ukhttp://retrochallenge.nethttps://twitter.com/urbancamo
What do you get on:
$ Mc ncp sho node mim all
$ Mc ncp sho node 1.13 all
Verzonden vanaf mijn BlackBerry 10-smartphone.
Origineel bericht
Van: Mark Wickens
Verzonden: zondag 6 april 2014 21:46
Aan: hecnet at Update.UU.SE
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: [HECnet] Problems getting decnet configured on IA64 VMS 8.4
Hi folks
I'm missing something here that will probably be obvious when pointed out.
Currently commissioning TSR2 (decnet 4.12) I'm having trouble copying
the known nodes database from MIM.
SIMVAX is also running and reporting good connectivity, so this isn't
bridge related.
$ SHOW NETWORK
Product: DECNET Node: TSR2 Address(es): 4.12
Product: TCP/IP Node: tsr2.hecnet.eu Address(es):
192.168.1.151
NCP>set node 1.13 name mim
%NCP-W-INVPVA, Invalid parameter value , Address
NCP>list circuit *
Known Circuit Permanent Summary as of 6-APR-2014 19:43:03
Circuit State
EWA-0 on
EWA-1 on
NCP>list executor
Node Permanent Summary as of 6-APR-2014 19:43:54
Executor node = 4.12 (TSR2)
State = on
Thanks, Mark.
--
http://www.wickensonline.co.ukhttp://hecnet.euhttp://declegacy.org.ukhttp://retrochallenge.nethttps://twitter.com/urbancamo
Hi folks
I'm missing something here that will probably be obvious when pointed out.
Currently commissioning TSR2 (decnet 4.12) I'm having trouble copying the known nodes database from MIM.
SIMVAX is also running and reporting good connectivity, so this isn't bridge related.
$ SHOW NETWORK
Product: DECNET Node: TSR2 Address(es): 4.12
Product: TCP/IP Node: tsr2.hecnet.eu Address(es): 192.168.1.151
NCP>set node 1.13 name mim
%NCP-W-INVPVA, Invalid parameter value , Address
NCP>list circuit *
Known Circuit Permanent Summary as of 6-APR-2014 19:43:03
Circuit State
EWA-0 on
EWA-1 on
NCP>list executor
Node Permanent Summary as of 6-APR-2014 19:43:54
Executor node = 4.12 (TSR2)
State = on
Thanks, Mark.
--
http://www.wickensonline.co.ukhttp://hecnet.euhttp://declegacy.org.ukhttp://retrochallenge.nethttps://twitter.com/urbancamo