5 May
2020
5 May
'20
8:17 a.m.
Hello,
It worked i did
configuration by means of
@SYS$MANAGER:NET$CONFIGURE.COM
then started decnet Plus
all licenses is valid and loaded
Decnet started but
@DECNET-CIRCUITS.COM
gives error here is what it says
%NCP-W-UNRCMP, Unrecognized component , Line
%NCP-W-UNRCMP, Unrecognized component , Circuit
$ multinet show
Multinet Active Connections at? 4-MAY-2020 17:48:01.65:
Proto Rcv-Q Snd-Q? Local Address (Port)?????????????????????????????
Foreign Address (Port)??????????????????????????? State
----- ----- ----- --------------------------------------------
--------------------------------------------????? -----
TCP?????? 0???? 0 OMEGA(1439)
80.89.204.47(700)???????????????????????????????? ESTABLISHED
TCP?????? 0???? 0 *(953)
*(*)????????????????????????????????????????????? LISTEN
TCP?????? 0???? 0 OMEGA(NAMESERVICE)
*(*)????????????????????????????????????????????? LISTEN
TCP?????? 0???? 0 LOCALHOST(NAMESERVICE)
*(*)????????????????????????????????????????????? LISTEN
TCP?????? 0???? 0 *(NETCONTROL)
*(*)????????????????????????????????????????????? LISTEN
TCP?????? 0???? 0 *(ISO-TSAP-C2)
*(*)????????????????????????????????????????????? LISTEN
TCP?????? 0???? 0 *(ISO-TSAP)
*(*)????????????????????????????????????????????? LISTEN
UDP?????? 0???? 0 *(*)????????????????????????????????????????????? *(*)
UDP?????? 0???? 0 OMEGA(NAMESERVICE)??????????????????????????????? *(*)
UDP?????? 0???? 0 LOCALHOST(NAMESERVICE)??????????????????????????? *(*)
UDP?????? 0???? 0 *(SNMP)?????????????????????????????????????????? *(*)
but connection to node seems active
so seems this things
set line TCP-0-0 state on
set circuit TCP-0-0 state on cost 1 hello timer 15
not working in DECNET-CIRCUITS.COM
and 'show known lines and circuits' give this
$ mcr ncp
NCP>show known lines
Known Line Volatile Summary as of? 5-MAY-2020 09:15:49
No information in database
NCP>show know circ
Known Circuit Volatile Summary as of? 5-MAY-2020 09:15:54
?? Circuit????????? State?????????????????? Loopback???? Adjacent
? QNA-0???????????? on
NCP>
04.05.2020 19:18, Keith Halewood ?????:
When I helped Ales set up his DECnet over a multinet
TCP/IP connection, I gave him an additional .COM file to be executed (by systartup_vms)
after the @....multinet...startup.com line. This was to bypass the
multinet:decnet-circuits.com file which overwrites circuits configured by multinet
commands and whose defaults are useless.
Within that procedure, I had commented out the loading of the tcpdriver because that is
done by multinet:decnet-circuits.com but ONLY when you have previously had some circuits
defined. So, if you're using the separate command procedure solution and have never
defined any tcp circuits with multitnet commands, you will have to uncomment the line that
loads the driver. I think I probably caused more trouble than solving anything though I
find it more difficult to describe how multinet overwrites config files when it does so.
So, the second line is only commented out if multnet already loads tcpdriver.
$ SysGen:=$SysGen
$ SysGen Load Multinet:TCPDriver
$ sysgen connect tcpa0:/noadapter/driver=tcpdriver $ multinet
set/decnet/device=tcpa0:/tcp=connect/buffers=24 /remote=xx.xx.xx.xx/port=60012/connect
$!
$ if F$GetDVI("_NET0:","EXISTS") Then Goto DECnet_Ok
$ Write Sys$Output "MultiNet: DECnet not started; not starting DECnet over IP
circuits"
$ Exit
$DECnet_Ok:
$ mcr ncp
set line TCP-0-0 state on
set circuit TCP-0-0 state on cost 3 hello timer 300
$ exit
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf Of
Robert Armstrong
Sent: 04 May 2020 15:53
To: hecnet at Update.UU.SE
Subject: RE: [HECnet] MULTINET + DECnet over ip
--
??? ????????? ????????? ?? ?????? ??????????? Avast.
https://www.avast.com/antivirus
Serguei <melehov at sypp.ru> wrote:
seems like multinet set/decnet/remote=X.X.X.X /device=tcpa0: /connect
/tcp=connect /buffers=24 not creates _NET0: device. but no errors is
displayed. Anyone knows what could be problem?
The NET0 device is created when
you start DECnet - it has nothing to do with Multinet. You need to make sure the
"START/NETWORK DECNET" line in your SYSTARTUP_VMS.COM file comes before you try
to start up Multinet.
Bob