Decnet not talking to local network v.9.2-1
Decnet not talking to local network v.9.2-1
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
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
Re: Decnet not talking to local network v.9.2-1
m_detommaso wrote: ↑Sun May 21, 2023 4:30 am
Please, capture and share the output of the following commands :
$ show license
Code: Select all
$ show lic
Active licenses on node BOSCO:
------- Product ID -------- ---- Rating ----- -- Version --
Product Producer Units PCL Activ Version Release Termination
ABS-CLIENT-X86 VSI 6 1 0 0.0 (none) 1-APR-2024
ABS-SERVER-X86 VSI 6 1 0 0.0 (none) 1-APR-2024
ACMS VSI 6 1 0 0.0 (none) 1-APR-2024
ACMS-REM VSI 6 1 0 0.0 (none) 1-APR-2024
ACMS-RT VSI 6 1 0 0.0 (none) 1-APR-2024
AVAIL-MAN VSI 6 1 0 0.0 (none) 1-APR-2024
BASIC VSI 6 0 1 0.0 (none) 1-APR-2024
C VSI 6 0 1 0.0 (none) 1-APR-2024
CARTRIDGE-SERVER-V VSI 6 1 0 0.0 (none) 1-APR-2024
CMS VSI 6 1 0 0.0 (none) 1-APR-2024
COBOL VSI 6 0 1 0.0 (none) 1-APR-2024
CXX-V VSI 6 0 1 0.0 (none) 1-APR-2024
DFG VSI 6 1 0 0.0 (none) 1-APR-2024
DFS VSI 6 1 0 0.0 (none) 1-APR-2024
DQS VSI 6 1 0 0.0 (none) 1-APR-2024
DTM VSI 6 1 0 0.0 (none) 1-APR-2024
DTR VSI 6 1 0 0.0 (none) 1-APR-2024
DVNETEXT VSI 6 1 0 0.0 (none) 1-APR-2024
FMS VSI 6 1 0 0.0 (none) 1-APR-2024
FMS-RT VSI 6 1 0 0.0 (none) 1-APR-2024
FORMS VSI 6 1 0 0.0 (none) 1-APR-2024
FORMS-RT VSI 6 1 0 0.0 (none) 1-APR-2024
FORTRAN VSI 6 0 1 0.0 (none) 1-APR-2024
GKS VSI 6 1 0 0.0 (none) 1-APR-2024
GKS-RT VSI 6 1 0 0.0 (none) 1-APR-2024
LSE VSI 6 1 0 0.0 (none) 1-APR-2024
MMS VSI 6 1 0 0.0 (none) 1-APR-2024
OMNI VSI 6 1 0 0.0 (none) 1-APR-2024
OPENVMS-X86-BOE VSI 6 1 0 0.0 (none) 1-APR-2024
OPENVMS-X86-HAOE VSI 6 1 0 0.0 (none) 1-APR-2024
OSAP VSI 6 1 0 0.0 (none) 1-APR-2024
PASCAL VSI 6 0 1 0.0 (none) 1-APR-2024
PCA VSI 6 1 0 0.0 (none) 1-APR-2024
RMSJNL VSI 6 1 0 0.0 (none) 1-APR-2024
RTR-CL VSI 6 1 0 0.0 (none) 1-APR-2024
RTR-SVR VSI 6 1 0 0.0 (none) 1-APR-2024
SAVE-SET-MANAGER VSI 6 1 0 0.0 (none) 1-APR-2024
SW-RAID5 VSI 6 1 0 0.0 (none) 1-APR-2024
TDMS VSI 6 1 0 0.0 (none) 1-APR-2024
TDMS-RT VSI 6 1 0 0.0 (none) 1-APR-2024
VAXSET VSI 6 1 0 0.0 (none) 1-APR-2024
VMSCLUSTER VSI 6 1 0 0.0 (none) 1-APR-2024
VMSCLUSTER-CLIENT VSI 6 1 0 0.0 (none) 1-APR-2024
VOLSHAD VSI 6 1 0 0.0 (none) 1-APR-2024
X25 VSI 6 1 0 0.0 (none) 1-APR-2024
$
m_detommaso wrote: ↑Sun May 21, 2023 4:30 am$ set host 0 ! this will confirm to us that you can access your system using the decnet protocol
- successful logged in via set host 0
$ mc sysgen show scsystemid
Code: Select all
$ mc sysgen show SCSSYSTEMID
Parameter Name Current Default Min. Max. Unit Dynamic
-------------- ------- ------- ------- ------- ---- -------
SCSSYSTEMID 39947 0 0 -1 Pure-numbe
SCSSYSTEMIDH 0 0 0 -1 Pure-numbe
$ mc sysgen show SCSnode
Parameter Name Current Default Min. Max. Unit Dynamic
-------------- ------- ------- ------- ------- ---- -------
SCSNODE "BOSCO " " " " " "ZZZZ" Ascii
$
Code: Select all
$ mc lancp show config /user
BOSCO LAN Configuration (21-MAY-2023 16:10:44.48):
Parent or
Device PrefCPU Medium/User Version ----LinkState---- BufSize MAC Addres
s Name Description
EIA0 1 Ethernet X-34 Up 1gb Fdx Auto 1500 AA-00-04-00-0
B-9C i82540 VBOX
08-00-27-63-0
7-54 (default)
EIA3 60-03 DNA Routing 1498
EIA4 08-00 IP 1500
EIA5 08-06 ARP 1500
EIA6 86-DD IPV6 1500
$
Code: Select all
$ ana/system
OpenVMS system analyzer
SDA> clue config
System Configuration:
---------------------
System Information:
System Type innotek GmbH VirtualBox Primary CPU ID 0.
Cycle Time 0.43 nsec (2304 MHz) Pagesize 8192 Byte
System Management BIOS Information:
BIOS Version VirtualBox Manufacturer innotek GmbH
Release Date 12/01/2006 Product Name VirtualBox
SMBIOS Table 00000000.DAFD5020 Serial Number 0
UUID 4ADF3D72-31EB-4EF8-B40F-AAED8A72B7E9
Press RETURN for more.
SDA>
System Memory Configuration:
----------------------------
Cluster PFN Start PFN Count Range (MByte) Usage
-------- ------------ ------------ ----------------------------- -------
0 2 NXM
#000 2 132 0.0 MB - 0.5 MB System
#001 134 2 0.5 MB - 0.5 MB Console
#002 136 22 0.5 MB - 0.6 MB System
#003 158 2 0.6 MB - 0.6 MB Console
160 96 NXM
#004 256 768 0.6 MB - 3.6 MB Console
#005 1024 512 3.6 MB - 5.6 MB Console
#006 1536 256 5.6 MB - 6.6 MB Console
#007 1792 256 6.6 MB - 7.6 MB System
2048 768 NXM
#008 2816 256 7.6 MB - 8.6 MB System
#009 3072 23552 8.6 MB - 100.6 MB Console
#010 26624 497614 100.6 MB - 2044.4 MB System
#011 524238 26 2044.4 MB - 2044.5 MB Console
#012 524264 294870 2044.5 MB - 3196.4 MB System
819134 65536 NXM
Press RETURN for more.
SDA>
System Memory Configuration:
----------------------------
Cluster PFN Start PFN Count Range (MByte) Usage
-------- ------------ ------------ ----------------------------- -------
#013 884670 32 3196.4 MB - 3196.5 MB Console
#014 884702 1604 3196.5 MB - 3202.8 MB System
#015 886306 2026 3202.8 MB - 3210.7 MB Console
#016 888332 1518 3210.7 MB - 3216.6 MB System
#017 889850 502 3216.6 MB - 3218.6 MB Console
#018 890352 264 3218.6 MB - 3219.6 MB System
#019 890616 80 3219.6 MB - 3219.9 MB Console
#020 890696 404 3219.9 MB - 3221.5 MB Console
#021 891100 8 3221.5 MB - 3221.5 MB Console
#022 891108 6 3221.5 MB - 3221.5 MB System
#023 891114 4 3221.5 MB - 3221.5 MB Console
#024 891118 2222 3221.5 MB - 3230.2 MB Console
#025 893340 74 3230.2 MB - 3230.5 MB Console
#026 893414 2824 3230.5 MB - 3241.5 MB Console
#027 896238 514 3241.5 MB - 3243.6 MB Console
896752 126 NXM
#028 896878 146 3243.6 MB - 3244.1 MB Console
Press RETURN for more.
SDA>
System Memory Configuration:
----------------------------
Cluster PFN Start PFN Count Range (MByte) Usage
-------- ------------ ------------ ----------------------------- -------
#029 897022 514 3244.1 MB - 3246.1 MB Console
#030 897536 230 3246.1 MB - 3247.0 MB System
#031 897766 132 3247.0 MB - 3247.5 MB Console
#032 897898 3206 3247.5 MB - 3260.1 MB Console
901104 146448 NXM
#033 1047552 1024 3260.1 MB - 3264.1 MB Console
#034 1048576 1204224 3264.1 MB - 7968.1 MB System
Press RETURN for more.
SDA>
System Processor Configuration:
-------------------------------
CPU ID 0 CPU State rc,pa,pp,cv,pv,pmv,pl
CPU Type unknown 00000000.00000000
Halt PC 00000000.00000000 Halt PS 00000000.00000000
Halt code Bootstrap or Powerfail Halt Req. Default, No Action
Slot VA FFFFFFFF.8B33F000 CPUDB VA FFFFFFFF.82000000
Package Unknown Core Unknown
Thread id Unknown Cothread id None
FW Usage Unknown CPU die Unknown
ACPI CPU id 00000000.00000000 Serial Num
LID 00000000.00000000 CFG flags Unknown
CPU ID 1 CPU State rc,pa,pp,cv,pv,pmv,pl
CPU Type unknown 00000000.00000000
Halt PC 00000000.00000000 Halt PS 00000000.00000000
Halt code Bootstrap or Powerfail Halt Req. Default, No Action
Slot VA FFFFFFFF.8B33F430 CPUDB VA FFFFFFFF.8B6F4000
Package Unknown Core Unknown
Thread id Unknown Cothread id None
FW Usage Unknown CPU die Unknown
Press RETURN for more.
SDA>
System Processor Configuration:
-------------------------------
ACPI CPU id 00000000.00000001 Serial Num
LID 00000000.00000001 CFG flags Unknown
CPU ID 2 CPU State rc,pa,pp,cv,pv,pmv,pl
CPU Type unknown 00000000.00000000
Halt PC 00000000.00000000 Halt PS 00000000.00000000
Halt code Bootstrap or Powerfail Halt Req. Default, No Action
Slot VA FFFFFFFF.8B33F860 CPUDB VA FFFFFFFF.8B734000
Package Unknown Core Unknown
Thread id Unknown Cothread id None
FW Usage Unknown CPU die Unknown
ACPI CPU id 00000000.00000002 Serial Num
LID 00000000.00000002 CFG flags Unknown
CPU ID 3 CPU State rc,pa,pp,cv,pv,pmv,pl
CPU Type unknown 00000000.00000000
Halt PC 00000000.00000000 Halt PS 00000000.00000000
Halt code Bootstrap or Powerfail Halt Req. Default, No Action
Slot VA FFFFFFFF.8B33FC90 CPUDB VA FFFFFFFF.8B774000
Press RETURN for more.
SDA>
System Processor Configuration:
-------------------------------
Package Unknown Core Unknown
Thread id Unknown Cothread id None
FW Usage Unknown CPU die Unknown
ACPI CPU id 00000000.00000003 Serial Num
LID 00000000.00000003 CFG flags Unknown
Press RETURN for more.
SDA>
System Adapter Configuration:
-----------------------------
TR Adapter ADP Hose Bus BusArrayEntry Node GSIN iVe
c SCB Port Slot Device Name / HW-Id
-- ----------- ----------------- ---- -------------------------- ---- ----------
--------- ---- ---- ---------------------------
1 ACPI_IA64_P FFFFFFFF.8208F340 0 00 IA64_BUS
2 PCI FFFFFFFF.82092C80 0 00 PCI
FFFFFFFF.82093278 10 0012 00
DE 15E0 2 00000000.BEEF80EE (▒.▒)
FFFFFFFF.82093388 18 0013 00
DD 15D0 EIA: 3 Intel i82540 VBOX (Ethernet)
FFFFFFFF.82093498 20 0014 00
DC 15C0 4 00000000.CAFE80EE (▒.▒▒)
FFFFFFFF.820935A8 28 0015 00
DB 15B0 5 00008086.24158086 (...$..)
FFFFFFFF.820937C8 38 FFFF FF
FF 0 7 MFPCI
FFFFFFFF.82095148 F8 FFFF FF
FF 0 31 MFPCI
3 PCI FFFFFFFF.82096200 0 00 PCI
Press RETURN for more.
SDA>
System Adapter Configuration:
-----------------------------
TR Adapter ADP Hose Bus BusArrayEntry Node GSIN iVe
c SCB Port Slot Device Name / HW-Id
-- ----------- ----------------- ---- -------------------------- ---- ----------
--------- ---- ---- ---------------------------
FFFFFFFF.820965D8 38 0017 00
DA 15A0 7 00000000.71138086 (...q)
4 PCI FFFFFFFF.82097280 0 00 PCI
FFFFFFFF.82097658 F8 FFFF 00
00 0 31 72708086.27B98086 (..▒'..pr)
FFFFFFFF.82097878 FA 0017 00
D9 1590 PKA: 31 Intel ICH8 AHCI SATA
FFFFFFFF.82097A98 FC 0017 00
D8 1580 31 00000000.003F106B (k.?)
FFFFFFFF.82097BA8 FD 0017 00
D7 1570 31 00000000.265C8086 (..\&)
5 ISA FFFFFFFF.82098840 0 00 ISA
FFFFFFFF.82016598 0 000C 00
D6 1560 0 MOUSE
Press RETURN for more.
SDA>
System Adapter Configuration:
-----------------------------
TR Adapter ADP Hose Bus BusArrayEntry Node GSIN iVe
c SCB Port Slot Device Name / HW-Id
-- ----------- ----------------- ---- -------------------------- ---- ----------
--------- ---- ---- ---------------------------
FFFFFFFF.820166A8 1 0001 00
D5 1550 1 KBD
6 XBUS FFFFFFFF.82099140 0 00 XBUS
FFFFFFFF.82099518 0 0004 00
DF 15F0 SRA: 0 Console Serial Line Driver
FFFFFFFF.82099628 1 0009 00
D4 1540 1 00383043.30504E50 (PNP0C08)
SDA>
SDA> exit
$
m_detommaso wrote: ↑Sun May 21, 2023 4:30 am$ mc ncp show know line count
- wait 30 seconds -
$ mc ncp show know line count
Code: Select all
$ mcr ncp show known line count
Known Line Counters as of 21-MAY-2023 16:20:39
Line = EIA-0
1379 Seconds since last zeroed
21359 Data blocks received
16277 Multicast blocks received
0 Receive failure
3516518 Bytes received
1150004 Multicast bytes received
0 Data overrun
185 Data blocks sent
97 Multicast blocks sent
0 Blocks sent, multiple collisions
0 Blocks sent, single collision
0 Blocks sent, initially deferred
11548 Bytes sent
5250 Multicast bytes sent
1 Send failure, including:
Carrier check failed
0 Collision detect check failure
5001 Unrecognized frame destination
0 System buffer unavailable
0 User buffer unavailable
$ mcr ncp show known line count
Known Line Counters as of 21-MAY-2023 16:21:26
Line = EIA-0
1425 Seconds since last zeroed
22064 Data blocks received
16869 Multicast blocks received
0 Receive failure
3579363 Bytes received
1191762 Multicast bytes received
0 Data overrun
190 Data blocks sent
100 Multicast blocks sent
0 Blocks sent, multiple collisions
0 Blocks sent, single collision
0 Blocks sent, initially deferred
11838 Bytes sent
5400 Multicast bytes sent
1 Send failure, including:
Carrier check failed
0 Collision detect check failure
5112 Unrecognized frame destination
0 System buffer unavailable
0 User buffer unavailable
--- changed to "ROUTING IV", no change.m_detommaso wrote: ↑Sun May 21, 2023 4:30 amFurthermore, 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.

--- Yes all systems plugged into single switchm_detommaso wrote: ↑Sun May 21, 2023 4:30 am/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.
SMS,
The command MCR NCP SET CIRCUIT EIA-0 SERVICE ENABLED gave the following error message
Code: Select all
%NCP-W-COMSTA, Component in wrong state , Circuit
MCR NCP SHOW KNOWN CIRC COUNTER command gave the following.
Code: Select all
$ mcr ncp show known circ counter
Known Circuit Counters as of 21-MAY-2023 16:33:15
Circuit = EIA-0
2131 Seconds since last zeroed
0 Terminating packets received
0 Originating packets sent
0 Terminating congestion loss
0 Transit packets received
0 Transit packets sent
0 Transit congestion loss
1 Circuit down
0 Initialization failure
0 Adjacency down
0 Peak adjacencies
141 Data blocks sent
7050 Bytes sent
0 Data blocks received
0 Bytes received
0 Unrecognized frame destination
0 User buffer unavailable
$
/r
Mike
-
- Active Contributor
- Posts: 45
- 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
---
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.
--- changed to "ROUTING IV", no change.
Code: Select all
dirac> mc ncp set exec state off
dirac> mc ncp define exec type routing IV
dirac> list exec char
Node Permanent Characteristics as of 22-MAY-2023 12:34:00
Executor node = 39.11 (E921BT)
Management version = V4.0.0
Type = routing IV <--
Maximum address = 1023
Nonprivileged user id = DECNET
Nonprivileged password = ****************
dirac> @sys$startup:startnet
system_e921bt_opa0 >mc ncp sho exec char
Node Volatile Characteristics as of 22-MAY-2023 12:34:25
Executor node = 39.11 (E921BT)
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 = routing 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
A first analysis of your output would confirm that everything is correct

/Maurizio
Last edited by m_detommaso on Tue May 23, 2023 12:56 am, edited 1 time in total.
Re: Decnet not talking to local network v.9.2-1
m_detommaso wrote: ↑Mon May 22, 2023 6:48 amYep the adapter is set to promiscous mode (Allow All) with the cable connected.---
A first analysis of your output would confirm that everything is correct. Please, if possible, share also the output of the "mc ncp sho exec char" command of the other Decnet nodes and verify the promiscuous mode is correctly configured (and "cable connected" is checked) (see attached photo)
/Maurizio
Here is the output from the other three nodes (2 ALPHA's [real hardware] and 1 x86-64 on MacBookPro/VMWare Fusion)Thanks for your assistance.Code: Select all
NCP>sho exec char Node Volatile Characteristics as of 24-MAY-2023 21:28:35 Executor node = 39.1 (MASON) <----- Alpha Server 800 Identification = HP DECnet for OpenVMS Alpha 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 = 32 Delay weight = 5 Inactivity timer = 60 Retransmit factor = 10 Routing version = V2.0.0 Type = area 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 = ******* Nonprivileged password = ********** Default access = incoming and outgoing Pipeline quota = 23040 Alias maximum links = 32 Path split policy = Normal Maximum Declared Objects = 31 NCP>show exec char Node Volatile Characteristics as of 24-MAY-2023 21:33:56 Executor node = 39.10 (ROXY) <------ DEC 3000 Identification = HP DECnet for OpenVMS Alpha 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 = ****** Nonprivileged password = ********** Default access = incoming and outgoing Pipeline quota = 4032 Alias incoming = Disabled Alias maximum links = 32 Path split policy = Normal Maximum Declared Objects = 31 NCP>sho exec char Node Volatile Characteristics as of 24-MAY-2023 22:02:08 Executor node = 39.12 (VMSMAC) <--- new install of x86 on MacBookPro/Fusion 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 = ******* Nonprivileged password = ********* Default access = incoming and outgoing Pipeline quota = 4032 Alias maximum links = 32 Path split policy = Normal Maximum Declared Objects = 31 $ mcr ncp show exec char Node Volatile Characteristics as of 23-MAY-2023 16:26:11 Executor node = 39.11 (BOSCO) <--- the problem node not talking to network 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 = routing 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 = ********* Nonprivileged password = *************** Default access = incoming and outgoing Pipeline quota = 4032 Alias maximum links = 32 Path split policy = Normal Maximum Declared Objects = 31
Mike
-
- Master
- Posts: 155
- Joined: Fri Aug 14, 2020 11:31 am
- Reputation: 0
- Status: Offline
Re: Decnet not talking to local network v.9.2-1
Mike,vamike wrote: ↑Sun May 21, 2023 5:11 pmVolker,
MCR NCP SHOW KNOWN CIRC COUNTER command gave the following.
Code: Select all
$ mcr ncp show known circ counter Known Circuit Counters as of 21-MAY-2023 16:33:15 Circuit = EIA-0 2131 Seconds since last zeroed 0 Terminating packets received 0 Originating packets sent 0 Terminating congestion loss 0 Transit packets received 0 Transit packets sent 0 Transit congestion loss 1 Circuit down 0 Initialization failure 0 Adjacency down 0 Peak adjacencies 141 Data blocks sent 7050 Bytes sent 0 Data blocks received 0 Bytes received 0 Unrecognized frame destination 0 User buffer unavailable $
it's clear (from the CIRCUIT EIA-0 counters), that NO DECnet protocol packets are being received. There was a 'Circuit down' event - most likely associated with the send failure (carrier check failed) on LINE EIA-0. MC LANCP SHOW DEVICE/INTERNAL EIA0 should confirm this (look at the driver messages). And then no further DECnet packets have been received.
You can look at the network interface counters and characteristics for the various protocols with SDA
$ ANALYZE/SYS
SDA> SHOW LAN/DEV=EIA
will present lots of detailled data.
And you can compare this with a working DECnet Phase IV node.
In an end-node only DECnet network on a LAN, an end node just calculates the DECnet MAC address from the DECnet address of the remote node and sends the packet to that address on the LAN. If the remote LAN interface does not listen to that address - maybe due to a problem with the Hypervisor, the packet will never arrive in the VM. If DECnet routing nodes are available on the LAN, the end-nodes will announce their existance with end-node hello multicast messages, so the routers lean about the end-nodes and the routers will send router hello messages, so that the end-nodes learn about the router(s).
If you try to ping this node using IP and then look up the MAC address with $ arp -a , which MAC address is shown for this node ?
Volker.
Last edited by volkerhalle on Thu May 25, 2023 11:35 am, edited 1 time in total.
-
- Visitor
- Posts: 1
- Joined: Thu May 25, 2023 11:11 pm
- Reputation: 0
- Status: Offline
Re: Decnet not talking to local network v.9.2-1
Its not something silly, like having to define as well as set the circuit and line characteristics in ncp ?
$ mcr ncp list known circ char
$ mcr ncp list known line char
$ mcr ncp show known circ char
$ mcr ncp show known line char
checking state and MAC address
Noted on previous config that DNA routing is on EIA3
Paul
$ mcr ncp list known circ char
$ mcr ncp list known line char
$ mcr ncp show known circ char
$ mcr ncp show known line char
checking state and MAC address
Noted on previous config that DNA routing is on EIA3
Paul