Starting DECnet hanging network connectivity

[jasonmirons]

Hi Everyone.

I'm building a new x86_64 OpenVMS E9.2-1 platform to migrate our application to from an hpe rx2660.

Have done a base deployment and configured DECnet IV and TCPIP. DECnet is required for some internal application communications.

However, I've noticed that when DECnet is started it prevents any network based connectivity to the host. If I disable it in sys$startup:systartup_vms.com then am able to telnet and ssh to the platform.

Has anyone else experienced this. Really appreciate your thoughts.

Thanks

Jason

[m_detommaso]

Which virtualization platform are you using (VirtualBox, KVM, Vmware Workstation, ESXi) ?

My idea is to check that the virtual network adapter is configured in "Promiscuous Mode": the node’s DECnet IV software resets the physical address to a new six-byte value AA-00-04-00-xx-yy, where xx-yy are two low-order bytes, calculated with the following formula: "convert the decimal node address to its hexadecimal equivalent [(area-number * 1024) + node-number, it should correspond to scsystemid kernel parameter] and reverse byte order".

If the virtual network adapter is not configured in "Promiscuous Mode", Decnet API will not be able to make this change and that could cause some trouble.

"Promiscuous Mode" setting is required also when you configure Lan Failover device LLxx.

I hope this helps.
/Maurizio

[debbee.west]

What Maurizio said

But, also, if you are running phase V, you can disable the phase IV addressing in net$configure advanced. pick number 3, devices. For phase IV addressing question, say no.

From my machine:

Code: Select all

    You have the option of enabling Phase-IV addressing on this routing
     circuit.  This should be enabled on only one circuit per LAN.

* Enable Phase-IV Addressing on Routing Circuit 'CSMACD-0'? [YES] : no

I believe this will fix up your issue.

[jasonmirons]

Hi Maurizio and Debbee

Many thanks to you both for the explanation.

We are using VMware ESXi VMware ESXi, 7.0.3.

The application requires DECnet for inter-process communication within the host. We are not using it for comms to the outside world.

Should we opt to use DECnet V, with DECnet IV disabled, would this get around the requirement for Promiscuous Mode?

A quick google indicates this needs to be enabled at the vswitch layer. I'm hoping our virtualisation team won't object to much to making this change.

Thanks again

Jason

[imiller]

Promiscuous mode is only required on the virtual NIC setting not the switch, especially if you are using a host only NIC for DECnet. Not using DECnet IV may also help.

[xenophore]

Code: Select all

* Enable Phase-IV Addressing on Routing Circuit 'CSMACD-0'? [YES] : no

This question no longer exists in 9.2 and I am having this problem. Everything worked fine before I configured DECnet-plus. I am running in VirtualBox and have the network adapter set to promiscuous “for all.” I can see the node in Angry IP Scanner and it shows that the MAC address has been changed to AA:00:04:00:02:04. Other than verifying the system is live on the network, however, I cannot reach the WebUI site on it nor can I SSH to it.

[m_detommaso]

Decnet and TCP/IP protocol work fine in my Virtual Box environment. if you have set up NAT in your network configuration, try with Bridge.

/Maurizio

[volkerhalle]

Code: Select all

* Enable Phase-IV Addressing on Routing Circuit 'CSMACD-0'? [YES] : no

This question no longer exists in 9.2 and I am having this problem.

This questions is only asked in @NET$CONFIGURE ADVANCED mode, when selecting [3]Configure Devices on this machine

If you answer the following question during initial configuration with 0.0, Phase-IV adressing would not be enabled.

* Enter PhaseIV Address [50.1] :

Volker.