I installed v9.2-1 on Virtual Box 7.0.8. on windows 11 with a bridged adaptor (8254OEM) setting to the LAN adaptor.
I followed Raymii's wonderful guide.
TCPIP version x6.0 installed fine and it's connecting to the local network fine through the bridged adaptor.
I can ping and telnet/ssh to other hosts and I'm able to telnet/ssh from other hosts to the VMS host.
The problem is Decnet. I installed Decnet (phase IV) successfully and configured it to the area and node setting for my home network; but it's not communicating to the rest of the network. The other VMS systems don't see via decnet (but TCPIP is fine).
I've tried changing the virtual adaptor to the DECnet MAC address, but that didn't help either.
Anyone have any ideas to get DECnet to communicate as well as TCPIP does from the virtual host to the home network?
I'd greatly appreciate the help.
Mike
Decnet not talking to local network v.9.2-1
-
reinhardtjh
- Active Contributor
- Posts: 39
- Joined: Sun Feb 23, 2020 7:49 am
- Reputation: 0
- Location: Fort Worth, TX USA
- Status: Offline
Re: Decnet not talking to local network v.9.2-1
The first easy thing to check is did you install and configure DECnet after TCP/IP was running?
DECnet needs to be started first in the OpenVMS startup process because it changes the MAC address of the NIC based on the DECnet address you gave the system. You shouldn't need to set the MAC address for DECnet in the emulator.
Though, generally, when you go in reverse order, DECnet works and TCP/IP is broken so maybe that's not it.
Is promiscuous mode enabled for the virtual NIC?
DECnet needs to be started first in the OpenVMS startup process because it changes the MAC address of the NIC based on the DECnet address you gave the system. You shouldn't need to set the MAC address for DECnet in the emulator.
Though, generally, when you go in reverse order, DECnet works and TCP/IP is broken so maybe that's not it.
Is promiscuous mode enabled for the virtual NIC?
John H. Reinhardt
- VMS user since 1981
Re: Decnet not talking to local network v.9.2-1
Yes, promiscuous mode is enabled and DECnet is started prior to TCPIP in systartup_vms.com (see the decnet starting messages prior to the TCPIP startup messages).reinhardtjh wrote: ↑Sun May 14, 2023 2:44 amThe first easy thing to check is did you install and configure DECnet after TCP/IP was running?
DECnet needs to be started first in the OpenVMS startup process because it changes the MAC address of the NIC based on the DECnet address you gave the system. You shouldn't need to set the MAC address for DECnet in the emulator.
Though, generally, when you go in reverse order, DECnet works and TCP/IP is broken so maybe that's not it.
Is promiscuous mode enabled for the virtual NIC?
I even commented out the TCPIP startup line, and DECnet still doesn't talk to other nodes.
Any thoughts greatly appreciated.
Mike
Re: Decnet not talking to local network v.9.2-1
Code: Select all
> [...] it's not communicating to the rest of the network. [...]
As usual, showing what you actually did (actual commands) and what
actually happened when you did it (actual behavior, error messages)
might be more helpful than a vague description of what does _not_
happen.
> [...] Virtual Box [...] Windows [...] Decnet (phase IV) [...] bridged
> adaptor (8254OEM) setting to the LAN adaptor. [...]
Not much like my VMware-on-Mac-DECnet-Plus arrangement, so I know
nothing, but I might look at what VMS says about its network, adapter,
and so on.
Last edited by sms on Mon May 15, 2023 12:19 pm, edited 1 time in total.
Re: Decnet not talking to local network v.9.2-1
It's standard vanilla VMS startup, Decnet startup (via command not batch), followed by TCPIP startup command and then SSH startup command. The virtualbox adapter is bridged to the wired ethernet port and set to promiscuous mode.sms wrote: ↑Mon May 15, 2023 12:18 pmCode: Select all
> [...] it's not communicating to the rest of the network. [...] As usual, showing what you actually did (actual commands) and what actually happened when you did it (actual behavior, error messages) might be more helpful than a vague description of what does _not_ happen. > [...] Virtual Box [...] Windows [...] Decnet (phase IV) [...] bridged > adaptor (8254OEM) setting to the LAN adaptor. [...] Not much like my VMware-on-Mac-DECnet-Plus arrangement, so I know nothing, but I might look at what VMS says about its network, adapter, and so on.
in the startup screen I see the following indicating DECnet has started up and brought the circuit up, followed by TCPIP and SSH startups running.
The only odd thing is a circuit "Line synchronization lost" error message followed by a circuit up message.
/r
Mike
Code: Select all
The OpenVMS system is now executing the site-specific startup commands.
%RUN-S-PROC_ID, identification of created process is 00000412
%%%%%%%%%%% OPCOM 20-MAY-2023 19:51:23.08 %%%%%%%%%%%
Message from user DECNET on BOSCO
DECnet starting
%%%%%%%%%%% OPCOM 20-MAY-2023 19:51:24.10 %%%%%%%%%%%
Message from user DECNET on BOSCO
Error opening permanent proxy database
%NCP-I-NOINFO, No information in database
%RUN-S-PROC_ID, identification of created process is 00000414
%%%%%%%%%%% OPCOM 20-MAY-2023 19:51:25.53 %%%%%%%%%%%
Message from user SYSTEM on BOSCO
%SECSRV-I-PROXYSTARTINGUP, proxy processing now starting up
%%%%%%%%%%% OPCOM 20-MAY-2023 19:51:25.53 %%%%%%%%%%%
Message from user SYSTEM on BOSCO
%SECSRV-E-NOPROXYDB, cannot find proxy database file NET$PROXY.DAT
%RMS-E-FNF, file not found
%EIA0, Link up: 1000 mbit, fdx, flow control (rcv only), 08-00-27-63-07-54
%%%%%%%%%%% OPCOM 20-MAY-2023 19:51:29.13 %%%%%%%%%%%
Message from user DECNET on BOSCO
DECnet event 4.10, circuit up
From node 39.11 (BOSCO), 20-MAY-2023 19:51:24.13
Circuit EIA-0
%%%%%%%%%%% OPCOM 20-MAY-2023 19:51:29.13 %%%%%%%%%%%
Message from user DECNET on BOSCO
DECnet event 4.7, circuit down, circuit fault
From node 39.11 (BOSCO), 20-MAY-2023 19:51:25.11
Circuit EIA-0, Line synchronization lost
%%%%%%%%%%% OPCOM 20-MAY-2023 19:51:34.15 %%%%%%%%%%%
Message from user DECNET on BOSCO
DECnet event 4.10, circuit up
From node 39.11 (BOSCO), 20-MAY-2023 19:51:34.15
Circuit EIA-0
%TCPIP-I-INFO, TCP/IP Services startup beginning at 20-MAY-2023 19:51:39.74
%TCPIP-I-NORMAL, timezone information verified
%RUN-S-PROC_ID, identification of created process is 0000041B
%%%%%%%%%%% OPCOM 20-MAY-2023 19:51:40.01 %%%%%%%%%%%
Message from user INTERnet on BOSCO
INTERnet Loaded
%%%%%%%%%%% OPCOM 20-MAY-2023 19:51:40.02 %%%%%%%%%%%
Message from user INTERnet on BOSCO
Subsystem "inet" configured by process 0001001B
Status: success
%%%%%%%%%%% OPCOM 20-MAY-2023 19:51:40.02 %%%%%%%%%%%
Message from user INTERnet on BOSCO
Subsystem "net" configured by process 0001001B
Status: success
%%%%%%%%%%% OPCOM 20-MAY-2023 19:51:40.02 %%%%%%%%%%%
Message from user INTERnet on BOSCO
Subsystem "socket" configured by process 0001001B
Status: success
%%%%%%%%%%% OPCOM 20-MAY-2023 19:51:40.02 %%%%%%%%%%%
Message from user INTERnet on BOSCO
Subsystem "iptunnel" configured by process 0001001B
Status: success
%%%%%%%%%%% OPCOM 20-MAY-2023 19:51:40.02 %%%%%%%%%%%
Message from user INTERnet on BOSCO
Subsystem "ipv6" configured by process 0001001B
Status: success
%%%%%%%%%%% OPCOM 20-MAY-2023 19:51:40.02 %%%%%%%%%%%
Message from user INTERnet on BOSCO
Subsystem "snmpinfo" configured by process 0001001B
Status: success
%%%%%%%%%%% OPCOM 20-MAY-2023 19:51:40.02 %%%%%%%%%%%
Message from user INTERnet on BOSCO
Subsystem "kvci" configured by process 0001001B
Status: success
%TCPIP-I-SETLOCAL, setting domain and/or local host
%TCPIP-I-STARTCOMM, starting communication
%%%%%%%%%%% OPCOM 20-MAY-2023 19:51:41.09 %%%%%%%%%%%
Message from user INTERnet on BOSCO
INTERnet Started
%TCPIP-I-SETPROTP, setting protocol parameters
%TCPIP-I-DEFINTE, defining interfaces
%%%%%%%%%%% OPCOM 20-MAY-2023 19:51:41.12 %%%%%%%%%%%
Message from user INTERnet on BOSCO
INTERnet ACP Created INTERnet interface: IE0
%%%%%%%%%%% OPCOM 20-MAY-2023 19:51:41.13 %%%%%%%%%%%
Message from user INTERnet on BOSCO
%TCPIP-I-FSIPADDRUP, IE0 192.168.xx.xxx primary active on node BOSCO, interface
IE0
%TCPIP-I-STARTNAME, starting name service
%%%%%%%%%%% OPCOM 20-MAY-2023 19:51:41.18 %%%%%%%%%%%
Message from user INTERnet on BOSCO
Subsystem "proxy" configured by process 00010003
Status: success
%TCPIP-S-STARTDONE, TCP/IP Kernel startup completed
%TCPIP-I-PROXYLOADED, loaded 0 NFS proxy records
%TCPIP-I-LOADSERV, loading TCPIP server proxy information
%TCPIP-I-SERVLOADED, auxiliary server loaded with 0 proxy records
-TCPIP-I-SERVSKIP, skipped 0 communication proxy records
-TCPIP-I-SERVTOTAL, total of 0 proxy records read
%TCPIP-S-STARTDONE, TCPIP$PROXY startup completed
%TCPIP-S-STARTDONE, TCPIP$FTP_CLIENT startup completed
%TCPIP-S-STARTDONE, TCPIP$INET_DRIVER startup completed
%%%%%%%%%%% OPCOM 20-MAY-2023 19:51:41.55 %%%%%%%%%%%
Message from user INTERnet on BOSCO
INTERnet ACP Activate TELNET Server
%TCPIP-S-STARTDONE, TCPIP$TELNET startup completed
%TCPIP-S-STARTDONE, TCP/IP Services startup completed at 20-MAY-2023 19:51:41.58
Enabling service...
Successfully enabled SSHD22 service
-
reinhardtjh
- Active Contributor
- Posts: 39
- Joined: Sun Feb 23, 2020 7:49 am
- Reputation: 0
- Location: Fort Worth, TX USA
- Status: Offline
Re: Decnet not talking to local network v.9.2-1
You might try posting the output of LANCP. Maybe something there will trigger an idea.
Or a SHOW NETWORK/FULL (trimmed to only DECnet)
Do you get anything out of NCP?
SHOW KNOWN LINE CHAR
SHOW KNOWN CIRCUIT CHAR
SHOW ACTIVE NODES CHAR
Code: Select all
$ mcr lancp
LANCP> show config/all
SCALZI LAN Configuration (20-MAY-2023 18:19:54.19):
Parent or
Device PrefCPU Medium/User Version ----LinkState---- BufSize MAC Address Name Description
EIA0 0 Ethernet X-34 Up 1gb Fdx Auto 1500 00-0C-29-41-36-F8 i82545 VMware
EIB0 3 Ethernet X-34 Up 1gb Fdx Auto 1500 AA-00-04-00-07-45 i82545 VMware
00-0C-29-41-36-02 (default)
SCALZI LAN Configuration and Status (20-MAY-2023 18:19:54.20):
Device Link Speed Type Uptime GBytes MPackets XmtErrors RcvErrors CRCErrors AvgPkSize Packets/Error % Xmt
EIA0 Up 1gb UTP i82545 V 133:14:06 0 0 0 0 0 440 - 0%
EIB0 Up 1gb UTP i82545 V 133:14:06 8 6 0 0 0 1348 - 0%
----- ----- ----- ----- -----
8 7 0 0 0
SCALZI LAN Configuration and Bandwidth (20-MAY-2023 18:19:54.20):
Avg | Bandwidth ---- Highest MBaud ----
Device Link Speed Type Uptime GBytes MPackets MBaud | RecordedTime 1Min 10Min 1Hr 4Hr 8Hr 24Hr
EIA0 Up 1000 UTP i82545 V 133:14:06 0 0 0 | 1:16:44 0 0 0
EIB0 Up 1000 UTP i82545 V 133:14:06 8 6 0 | 1:23:05 0 0 0
----- -----
8 7
LANCP>Code: Select all
$ show network/full
The following network services are available at this time:
Product: DECNET Manufacturer: VMS Software Inc.
Node: SCALZI Address(es): 17.263
Network Type: DNA IV Interface(s): net 0
Node Volatile Characteristics as of 20-MAY-2023 18:23:07
Executor node = 17.263 (SCALZI)
Identification = VSI DECnet for OpenVMS x86
Management version = V4.0.0
Incoming timer = 45
Outgoing timer = 60
Incoming Proxy = Enabled
Outgoing Proxy = Enabled
NSP version = V4.1.0
Maximum links = 32
Delay factor = 80
Delay weight = 5
Inactivity timer = 60
Retransmit factor = 10
Routing version = V2.0.0
Type = nonrouting IV
Routing timer = 600
Broadcast routing timer = 180
Maximum address = 1023
Maximum circuits = 16
Maximum cost = 1022
Maximum hops = 30
Maximum visits = 63
Maximum area = 63
Max broadcast nonrouters = 64
Max broadcast routers = 32
Maximum path splits = 1
Area maximum cost = 1022
Area maximum hops = 30
Maximum buffers = 100
Buffer size = 576
Default access = incoming and outgoing
Pipeline quota = 4032
Alias maximum links = 32
Path split policy = Normal
Maximum Declared Objects = 31
Known Link Volatile Summary as of 20-MAY-2023 18:23:07
No information in database
Node Counters as of 20-MAY-2023 18:23:07
Executor node = 17.263 (SCALZI)
0 Maximum 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
SHOW KNOWN LINE CHAR
SHOW KNOWN CIRCUIT CHAR
SHOW ACTIVE NODES CHAR
John H. Reinhardt
- VMS user since 1981
Re: Decnet not talking to local network v.9.2-1
John,
Here is the LANCP output
Doing the Show network/full command gave the following error and logged me out.
after logging in and running the command again I got
I did the NCP commands and they ran well.
It was the first time I received the error, but I've only run the show network command without the /full qualifier.
/r
Mike
Here is the LANCP output
Code: Select all
LANCP> sho config/all
BOSCO LAN Configuration (21-MAY-2023 01:00:44.05):
Parent or
Device PrefCPU Medium/User Version ----LinkState---- BufSize MAC Address Name Description
EIA0 1 Ethernet X-34 Up 1gb Fdx Auto 1500 AA-00-04-00-0B-9C i82540 VBOX
08-00-27-63-07-54 (default)
BOSCO LAN Configuration and Status (21-MAY-2023 01:00:44.08):
Device Link Speed Type Uptime GBytes MPackets XmtErrors RcvErrors CRCErrors AvgPkSize Packets/Error % Xmt
EIA0 Up 1gb UTP i82540 V 0:02:15 0 0 0 0 0 89 - 10%
BOSCO LAN Configuration and Bandwidth (21-MAY-2023 01:00:44.10):
Avg | Bandwidth ---- Highest MBaud ----
Device Link Speed Type Uptime GBytes MPackets MBaud | RecordedTime 1Min 10Min 1Hr 4Hr 8Hr 24Hr
EIA0 Up 1000 UTP i82540 V 0:02:15 0 0 0 | 0:02:21 0
LANCP>
Code: Select all
$ show network/full
Improperly handled condition, bad stack or no handler specified.
Signal arguments: Number = 0000000000000005
Name = 000000000000000C
0000000000000004
0000000000000668
FFFF830006802367
0000000000000012
Register dump:
RAX = 000000007FF9DC80 RDI = 000000007FF9DC80 RSI = 0000000000000668
RDX = 0000000000000000 RCX = 0000000000000668 R8 = 00000000FFFF8F89
R9 = 000000000808080D RBX = 000000007FFABE00 RBP = 000000007FF9E330
R10 = 000000007FFABDB0 R11 = 000000007FFA4D18 R12 = 000000007FF9C648
R13 = 0000000000000018 R14 = 000000007FF916F4 R15 = 0000000000008301
RIP = FFFF830006802367 RSP = 000000007FF9E2D0 SS = 000000000000001B
%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=000000000000
000C, PC=0000000000000002, PS=7AD8B092
Improperly handled condition, bad stack or no handler specified.
Signal arguments: Number = 0000000000000005
Name = 000000000000000C
0000000000000014
0000000000000000
000000007FF9C610
0000000000000012
Register dump:
RAX = 0000000000000001 RDI = 000000007FF7BC20 RSI = 0000000000000001
RDX = 0000000000000000 RCX = FFFFFFFF89409B5E R8 = 000000007ACEF11F
R9 = 0000000000000106 RBX = 000000007FFABE00 RBP = 000000007FF9D478
R10 = 000000007FFA4D18 R11 = 000000007FFA4D18 R12 = 000000007FF9D430
R13 = 000000007FFCDCAC R14 = 0000000000000002 R15 = 0000000021278301
RIP = 000000007FF9C610 RSP = 000000007FF9CA30 SS = 000000000000001B
Code: Select all
$ sho network/full
The following network services are available at this time:
Product: DECNET Manufacturer: VMS Software Inc.
Node: BOSCO Address(es): 39.11
Network Type: DNA IV Interface(s): net 0
Node Volatile Characteristics as of 21-MAY-2023 01:21:37
Executor node = 39.11 (BOSCO)
Identification = VSI DECnet for OpenVMS x86
Management version = V4.0.0
Incoming timer = 45
Outgoing timer = 60
Incoming Proxy = Enabled
Outgoing Proxy = Enabled
NSP version = V4.1.0
Maximum links = 32
Delay factor = 80
Delay weight = 5
Inactivity timer = 60
Retransmit factor = 10
Routing version = V2.0.0
Type = nonrouting IV
Routing timer = 600
Broadcast routing timer = 180
Maximum address = 1023
Maximum circuits = 16
Maximum cost = 1022
Maximum hops = 30
Maximum visits = 63
Maximum area = 63
Max broadcast nonrouters = 64
Max broadcast routers = 32
Maximum path splits = 1
Area maximum cost = 1022
Area maximum hops = 30
Maximum buffers = 100
Buffer size = 576
Nonprivileged user id = DECNET
Nonprivileged password = *********
Default access = incoming and outgoing
Pipeline quota = 4032
Alias maximum links = 32
Path split policy = Normal
Maximum Declared Objects = 31
Known Link Volatile Summary as of 21-MAY-2023 01:21:37
No information in database
Node Counters as of 21-MAY-2023 01:21:37
Executor node = 39.11 (BOSCO)
0 Maximum 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
$
Code: Select all
NCP>sho known line char
Known Line Volatile Characteristics as of 21-MAY-2023 01:25:13
Line = EIA-0
Receive buffers = 10
Controller = normal
Protocol = Ethernet
Service timer = 4000
Hardware address = 08-00-27-63-07-54
Device buffer size = 1498
NCP>sho known circ char
Known Circuit Volatile Characteristics as of 21-MAY-2023 01:25:46
Circuit = EIA-0
State = on
Service = disabled
Cost = 4
Maximum routers allowed = 33
Router priority = 64
Hello timer = 15
Type = Ethernet
NCP>show active nodes char
Active Node Volatile Characteristics as of 21-MAY-2023 01:25:57
Executor node = 39.11 (BOSCO)
Identification = VSI DECnet for OpenVMS x86
Management version = V4.0.0
Incoming timer = 45
Outgoing timer = 60
Incoming Proxy = Enabled
Outgoing Proxy = Enabled
NSP version = V4.1.0
Maximum links = 32
Delay factor = 80
Delay weight = 5
Inactivity timer = 60
Retransmit factor = 10
Routing version = V2.0.0
Type = nonrouting IV
Routing timer = 600
Broadcast routing timer = 180
Maximum address = 1023
Maximum circuits = 16
Maximum cost = 1022
Maximum hops = 30
Maximum visits = 63
Maximum area = 63
Max broadcast nonrouters = 64
Max broadcast routers = 32
Maximum path splits = 1
Area maximum cost = 1022
Area maximum hops = 30
Maximum buffers = 100
Buffer size = 576
Nonprivileged user id = DECNET
Nonprivileged password = **********
Default access = incoming and outgoing
Pipeline quota = 4032
Alias maximum links = 32
Path split policy = Normal
Maximum Declared Objects = 31
NCP>
/r
Mike
-
m_detommaso
- Valued Contributor
- Posts: 73
- Joined: Thu Jun 06, 2019 6:57 am
- Reputation: 0
- Location: Brindisi (Italy)
- Status: Offline
- Contact:
Re: Decnet not talking to local network v.9.2-1
I'm running VMS x86-64 E9.2-1 and Decnet Phase IV without problem on my VB Virtual Machine and, in my environment, I have never observed the opcom event "DECnet event 4.7, circuit down, circuit fault" - "Circuit xxx-0, Line synchronization lost" during the Decnet IV protocol startup.
Please, capture and share the output of the following commands :
$ show license
$ set host 0 ! this will confirm to us that you can access your system using the decnet protocol
$ mc sysgen show scsystemid
$ mc lancp show config /user
$ ana/system
SAD> clue config
$ mc ncp show know line count
- wait 30 seconds -
$ mc ncp show know line count
---
Furthermore, try changing the "Executor Type" from "nonrouting IV" to "routing IV" or '"area" (it is closely related with the licenses you uploaded); hopefully this will generate more useful opcom messages.
/Maurizio
PS: I assume that between your VM and the other Decnet nodes there is no router in between and that all VMS systems are connected to the same network through network switches only.
Last edited by m_detommaso on Sun May 21, 2023 5:28 am, edited 2 times in total.
Re: Decnet not talking to local network v.9.2-1
Code: Select all
> Service = disabled
Knowing nothing, I might try a command like:
NCP SET CIRCUIT EIA-0 SERVICE ENABLED
Perhaps it'll do something, or give an interesting message?
> From node 39.11 (BOSCO), [...]
Safe to assume that no one else uses that address?
> Circuit EIA-0, Line synchronization lost
To me, this suggests a (virtual) hardware problem. (But what do I
know?)
-
volkerhalle
- Master
- Posts: 196
- Joined: Fri Aug 14, 2020 11:31 am
- Reputation: 0
- Status: Offline
Re: Decnet not talking to local network v.9.2-1
Mike,
you might also want to try: MC NCP SHOW KNO CIRC COUNTER
Volker.
you might also want to try: MC NCP SHOW KNO CIRC COUNTER
Volker.