x86 OpenVMS 9.2-2 DHCP client issue in virtualbox

All types of networks, network stacks, and protocols supported by OpenVMS.
Post Reply

Topic author
alexwong
Active Contributor
Posts: 27
Joined: Tue Apr 23, 2024 6:28 am
Reputation: 0
Status: Offline

x86 OpenVMS 9.2-2 DHCP client issue in virtualbox

Post by alexwong » Sat Apr 27, 2024 8:35 pm

DHCP client startup fails with the message in tcpip$dhcp_client_run.log,
Error getting hardware address for: "IE0"

Tried Bridged/NAT/Host-only networks, all had the same issue. No ip address is assigned to the lan interface BUT if I restart the DHCP client after a login, it works. Turns out it's a timing issue with EIA0: link state still down when TCPIP$STARTUP.COM in SYSTARTUP_VMS.COM starts. I made a helper procedure to check the link state before starting TCPIP and found a 6 sec delay was needed. Searching thru the SP issues database and forums, I found nothing related which is odd as I assume most would use TCPIP to connect. Just wondering if someone else has come across this and got a better idea. Does this warrant raising an issue with VSI?

Virtualbox Version 7.0.14 r161095 (Qt5.15.2)
Windows 11
x86 OpenVMS 9.2-2 VMDK
Attachments
CHECK_LINK_STATE.TXT
(933 Bytes) Downloaded 266 times


sms
Master
Posts: 398
Joined: Fri Aug 21, 2020 5:18 pm
Reputation: 0
Status: Offline

Re: x86 OpenVMS 9.2-2 DHCP client issue in virtualbox

Post by sms » Sat Apr 27, 2024 11:35 pm

Code: Select all

   I've never tried a VMS DHCP client, so I know nothing, but is there
any chance of blaming DECnet for fiddling with the MAC address?

> [...] Does this warrant raising an issue with VSI?

   I'd say so, if you have a way to do that other than this posting.

User avatar

cct
Master
Posts: 147
Joined: Sat Aug 15, 2020 9:00 am
Reputation: 0
Location: Cambridge, UK
Status: Offline

Re: x86 OpenVMS 9.2-2 DHCP client issue in virtualbox

Post by cct » Sun Apr 28, 2024 6:43 pm

sms wrote:
Sat Apr 27, 2024 11:35 pm
I've never tried a VMS DHCP client, so I know nothing, but is there
any chance of blaming DECnet for fiddling with the MAC address?

> [...] Does this warrant raising an issue with VSI?

I'd say so, if you have a way to do that other than this posting.
At various times it has worked.
I think it is correct to raise this, as most sysadmins want to control their network using DHCP, rather than have random 'fixed' addresses cropping up

On recent Alphas, I used TCPWare where it does work. No reason for it not to work on X86
--
Chris


Topic author
alexwong
Active Contributor
Posts: 27
Joined: Tue Apr 23, 2024 6:28 am
Reputation: 0
Status: Offline

Re: x86 OpenVMS 9.2-2 DHCP client issue in virtualbox

Post by alexwong » Mon Apr 29, 2024 5:59 am

Thanks for advice, I shall raise an issue in Service Platform.


roberbrooks
VSI Expert
Active Contributor
Posts: 38
Joined: Thu Jun 20, 2019 11:48 am
Reputation: 0
Status: Offline

Re: x86 OpenVMS 9.2-2 DHCP client issue in virtualbox

Post by roberbrooks » Mon Apr 29, 2024 11:13 pm

This will be an interesting problem.

We've seen a similar problem where MSCP-served disks from Alpha/IA64 systems to virtual machines take longer than expected to be visible and mountable. Even after f$getdvi( "<devnam>", "EXISTS" ) returns TRUE, it does *not* mean that the disk will actually mount -- a delay loop is still needed.

As the author of the $GETDVI LAN_* item codes, I'm glad to see at least one of them being put to good use.


-- Rob
--
-- Rob

User avatar

imiller
Master
Posts: 163
Joined: Fri Jun 28, 2019 8:45 am
Reputation: 0
Location: South Tyneside, UK
Status: Offline
Contact:

Re: x86 OpenVMS 9.2-2 DHCP client issue in virtualbox

Post by imiller » Tue Apr 30, 2024 4:52 am

@Alex,
are you running DECnet?
Ian Miller
[ personal opinion only. usual disclaimers apply. Do not taunt happy fun ball ].


Topic author
alexwong
Active Contributor
Posts: 27
Joined: Tue Apr 23, 2024 6:28 am
Reputation: 0
Status: Offline

Re: x86 OpenVMS 9.2-2 DHCP client issue in virtualbox

Post by alexwong » Tue Apr 30, 2024 7:56 am

DECnet-Plus is installed by default in the VMDK but I have not run NET$CONFIGURE at all. Was planning to setup a TCPIP-only network.
Attachments
SHSYS.TXT
(1.59 KiB) Downloaded 246 times


Topic author
alexwong
Active Contributor
Posts: 27
Joined: Tue Apr 23, 2024 6:28 am
Reputation: 0
Status: Offline

Re: x86 OpenVMS 9.2-2 DHCP client issue in virtualbox

Post by alexwong » Wed May 22, 2024 6:27 am

VSI has provided a workaround for this issue, see below. I have tested it and DHCP client startup completes with no error so my CHECK_LINK_STATE procedure in SYSTARTUP_VMS.COM is no longer necessary. Thanks, VSI.

"A fix is being implemented for this situation for V9.2-3. In the meantime,
you can address the situation with the following workaround:

$ MC SYSGEN
SYSGEN> USE CURRENT
SYSGEN>SET LAN_FLAGS %X00004000
SYSGEN>WRITE CURRENT
SYSGEN>EXIT

Reboot

This changes how the LAN driver accomodates the “Link Up” condition,
be actually waiting for it, rather than assuming a second’s delay
between initialization and actual link up state."

Post Reply