Issue description:

When the customer deploys VyOS on Azure with Accelerated Networking enabled and multiple NICs using terraform, at least one of them doesn’t receive an IP address. It doesn’t matter if the allocation method is static or dynamic.

However, the main issue is the interface association between VFs and Eth. These are not set properly, and there is a mix of renaming while VyOS is applying Accelerated Networking. The result is that at least one of the interfaces won’t receive any traffic at all, which could be causing the IP address assignment issue as well, but most importantly, no connection is present for these interfaces.

Workaround:

+ Only enabling AN in a single NIC will make everything work as expected, traffic being received in all the interfaces, and IP assignment works as well.

Attachments:

First_deploy_AN_enabled --> Even the naming is correct no connectivity on interface eth1 and eth2.
First_deploy_AN_enabled2 --> Mix of VFs name but still no connectivity.
Single_NIC_AN_Enabled --> working as expected with a single NIC and AN enabled.
One_NIC_with_AN_Enabled --> Works as expected, as long only one nic with AN enabled.
Enabled_AN_after_deployment --> Duplicate MAC address for two interfaces. (Reboot sometimes fix this)
Working_With_AN_Enabled_just_once --> Weird scenario that worked with AN enabled and multiple NICs configured in the first deploy.

Azure documentation reference:
https://learn.microsoft.com/en-us/azure/virtual-network/accelerated-networking-how-it-works