Deploy Eflow Failed with error- Failed to acquire IP address for virtual machine

Question

Deploy Eflow Failed with error- Failed to acquire IP address for virtual machine

saurabh-3395 101

Hi Team,

I have enabled Hyper-V and I have two internal switch.

1- Default Switch

2- nat

When Running Deploy-Eflow on my VM I am getting below Error.

Failed to acquire IP address for virtual machine

User's image

Can You please let me know why this error is coming as Deploy-Eflow should use Default Switch and switch is already present.

LeelaRajeshSayana-MSFT 17,871 Reputation points Moderator

2023-02-03T21:39:37.69+00:00

Hi Saurabh, Greetings! Thank you for posting the question. We believe the issue is caused because the script to deploy Eflow expects to find a switch with an exact name which is Default Switch. The script is failing if the Virtual switch is named anything other than "Default Switch". We are investigating this issue internally and will update this thread with more details once we find the root cause and fix the script. Please look out for this thread for more updates in the next few days.
saurabh-3395 101 Reputation points

2023-02-04T18:11:37.31+00:00

Hi @LeelaRajeshSayana-MSFT ,

I have below two internal switch.

1- Default Switch

2- nat

If we do not specify any switch name while running the Deploy-Eflow command by Default Deploy-Eflow will use Default Switch.

I am not sure why it is failing with "Failed to acquire IP address for virtual machine" as Default Switch is already present.

Is there any other reason which is causing the command to fail?
LeelaRajeshSayana-MSFT 17,871 Reputation points Moderator

2023-02-06T20:13:35.21+00:00

Hi Saurabh, Greetings! You are correct. The script should succeed as you already have a switch named "Default Switch". Have you looked into the document Common issues and resolutions for Azure IoT Edge for Linux on Windows and look under Networking issues.

The article mentions the issue is caused by connectivity issues with the EFLOW virtual machine. The errors are generally related to an IP address change (if using static IP) or failure to assign an IP if using DHCP server. It further states that to resolve the error make sure to use the appropriate networking configuration. If there's a valid DHCP server, you can use DHCP assignation. If using static IP, make sure the IP configuration is correct (all three parameters: ip4Address, ip4GatewayAddress and ip4PrefixLength) and the address isn't being used by another device in the network. For more information about networking configurations, see Azure IoT Edge for Linux on Windows networking.

Can you please review and confirm if any of the above scenario applies to you and see if the fix proposed helps you.
LeelaRajeshSayana-MSFT 17,871 Reputation points Moderator

2023-02-08T17:58:30.21+00:00

Hi Saurabh, Greetings! I am following up to see if you are still stuck with this issue. Please let me know if you got a chance to review the above feedback and see if that helps addressing the error.

Kindly reach out to us with the status if you are still having issues and we would be glad to assist you further on this.
saurabh-3395 101 Reputation points

2023-02-10T07:02:10.8633333+00:00

Hi @LeelaRajeshSayana-MSFT ,

I have tried the solution which you mentioned but still I am facing the same issue.

I have also tried with external switch and assigning static ip and it got successful but while provisioning the edge device using dps it is falling.
QuantumCache 20,681 Reputation points Moderator

2023-02-13T23:30:35.7933333+00:00

We are looking into this
QuantumCache 20,681 Reputation points Moderator

2023-02-13T23:56:50.0633333+00:00

Hi Saurabh Shukla The Product team has responded to your query in the below section, please provide further details!
AshokPeddakotla-MSFT 36,021 Reputation points Moderator

2023-03-01T13:05:51.9566667+00:00

Saurabh Shukla Did you get a chance to see below response from Francisco?

Please share the requested details to help you further.
LeelaRajeshSayana-MSFT 17,871 Reputation points Moderator

2023-03-13T22:02:01.5666667+00:00

@Anonymous We still have not heard back from you. Just wanted to check if the information provided below was helpful? If it answers your query, please do click Accept Answer and Yes for this answer, as it might be beneficial to other community members reading this thread. And, if you have any further query do let us know. Thank you

Michael Wilcox 26

We have a similar networking issue w/ EFLOW. 


Environment: 

Windows Server 2019 
HyperV enabled (Passthrough)
	VM Options, enable VBS (Enable Virtualization based Security)
	Use External switch and turn on ‘Allow promiscuous mode’ 	
	EFLOW VM 1.1 in use 

Bug/Problem Description:

We are trying to update from Linux (Eflow version) 1.1 to 1.4  
However, the Linux VM is able to acquire the IP address and it begins an ssh connection but it asks me for a password which I do not have.  What is the password ?  Can it be reset to a default password ? 

Separately, when I try to use the newest version (1.4) the setup fails to acquire the IP and is unable to ssh into the machine.

Richard Reukema (Phx) 65 Reputation points

2023-05-19T21:17:06.3233333+00:00

I am very much in a similar situation, and have tried with my own "Default Switch" as well as a static IP. I both cases I got the same error. Images below:

Deployment using static IP:

2 answers

Your answer

LeelaRajeshSayana-MSFT 17,871 Reputation points Moderator

2023-02-03T21:39:37.69+00:00

Hi Saurabh, Greetings! Thank you for posting the question. We believe the issue is caused because the script to deploy Eflow expects to find a switch with an exact name which is Default Switch. The script is failing if the Virtual switch is named anything other than "Default Switch". We are investigating this issue internally and will update this thread with more details once we find the root cause and fix the script. Please look out for this thread for more updates in the next few days.
saurabh-3395 101 Reputation points

2023-02-04T18:11:37.31+00:00

Hi @LeelaRajeshSayana-MSFT ,

I have below two internal switch.

1- Default Switch

2- nat

If we do not specify any switch name while running the Deploy-Eflow command by Default Deploy-Eflow will use Default Switch.

I am not sure why it is failing with "Failed to acquire IP address for virtual machine" as Default Switch is already present.

Is there any other reason which is causing the command to fail?
LeelaRajeshSayana-MSFT 17,871 Reputation points Moderator

2023-02-06T20:13:35.21+00:00

Hi Saurabh, Greetings! You are correct. The script should succeed as you already have a switch named "Default Switch". Have you looked into the document Common issues and resolutions for Azure IoT Edge for Linux on Windows and look under Networking issues.

The article mentions the issue is caused by connectivity issues with the EFLOW virtual machine. The errors are generally related to an IP address change (if using static IP) or failure to assign an IP if using DHCP server. It further states that to resolve the error make sure to use the appropriate networking configuration. If there's a valid DHCP server, you can use DHCP assignation. If using static IP, make sure the IP configuration is correct (all three parameters: ip4Address, ip4GatewayAddress and ip4PrefixLength) and the address isn't being used by another device in the network. For more information about networking configurations, see Azure IoT Edge for Linux on Windows networking.

Can you please review and confirm if any of the above scenario applies to you and see if the fix proposed helps you.
LeelaRajeshSayana-MSFT 17,871 Reputation points Moderator

2023-02-08T17:58:30.21+00:00

Hi Saurabh, Greetings! I am following up to see if you are still stuck with this issue. Please let me know if you got a chance to review the above feedback and see if that helps addressing the error.

Kindly reach out to us with the status if you are still having issues and we would be glad to assist you further on this.
saurabh-3395 101 Reputation points

2023-02-10T07:02:10.8633333+00:00

Hi @LeelaRajeshSayana-MSFT ,

I have tried the solution which you mentioned but still I am facing the same issue.

I have also tried with external switch and assigning static ip and it got successful but while provisioning the edge device using dps it is falling.
QuantumCache 20,681 Reputation points Moderator

2023-02-13T23:30:35.7933333+00:00

We are looking into this
QuantumCache 20,681 Reputation points Moderator

2023-02-13T23:56:50.0633333+00:00

Hi Saurabh Shukla The Product team has responded to your query in the below section, please provide further details!
AshokPeddakotla-MSFT 36,021 Reputation points Moderator

2023-03-01T13:05:51.9566667+00:00

Saurabh Shukla Did you get a chance to see below response from Francisco?

Please share the requested details to help you further.
LeelaRajeshSayana-MSFT 17,871 Reputation points Moderator

2023-03-13T22:02:01.5666667+00:00

@Anonymous We still have not heard back from you. Just wanted to check if the information provided below was helpful? If it answers your query, please do click Accept Answer and Yes for this answer, as it might be beneficial to other community members reading this thread. And, if you have any further query do let us know. Thank you
Michael Wilcox 26 Reputation points

2023-03-28T20:49:27.17+00:00

We have a similar networking issue w/ EFLOW. Environment: Windows Server 2019 HyperV enabled (Passthrough) VM Options, enable VBS (Enable Virtualization based Security) Use External switch and turn on ‘Allow promiscuous mode’ EFLOW VM 1.1 in use Bug/Problem Description: We are trying to update from Linux (Eflow version) 1.1 to 1.4 However, the Linux VM is able to acquire the IP address and it begins an ssh connection but it asks me for a password which I do not have. What is the password ? Can it be reset to a default password ? Separately, when I try to use the newest version (1.4) the setup fails to acquire the IP and is unable to ssh into the machine.
Richard Reukema (Phx) 65 Reputation points

2023-05-19T21:17:06.3233333+00:00

I am very much in a similar situation, and have tried with my own "Default Switch" as well as a static IP. I both cases I got the same error. Images below:

Deployment using static IP:

Answer 1

Francisco Cabrera 5 Microsoft Employee

Hi Saurabh,

Could you please share the following information:

Are you using Windows Client or Server?
If so, could you please share the Win version (winver)?
Did you create the "nat" virtual switch? Is that virtual switch Internal or External?
If the switch is internal, do you have a DHCP server? Do you have a NAT table?
Could you please share the Deploy-Eflow command you're using? Are you using static Ip?

Thanks,

Francisco

0 comments

Answer 2

Hello @Saurabh Shukla,

Just wanted to follow-up on this issue, please let us know if you were unblocked on this issue? We are happy to assist you on this issue!

Few troubleshooting steps involve checking the virtual network adapter is connected to the correct virtual switch? ("nat" internal switch) and the virtual switch is configured correctly and has a DHCP server enabled ?
We can also Verify that the DHCP server is running and has available IP addresses to assign to the virtual machine? Try releasing and renewing the IP address of the virtual machine

ipconfig /release

ipconfig /renew

You can also try assigning a static IP address to the virtual machine manually.

Please comment in the below section if you need further help in this matter, we would be happy to assist you further!!!

If this answers your query, do click Accept Answer and Yes for this answer as helpful. And, if you have any further query do let us know by commenting in the below section.

Share via

Deploy Eflow Failed with error- Failed to acquire IP address for virtual machine

2 answers

Your answer