How to resolve Network Validation during Azure Local deployment

Question

Error:

On AZURESER: ERROR: Cannot find valid advanced property VlanId for adapter vNIC0. Use Get-NetAdapterAdvancedProperty/Set-NetAdapterAdvancedProperty with parameter RegistryKeyword set to VlanId to verify and configure it. PASS: DNS Client configuration has valid data for all adapters defined in intent PASS: Hyper-V is running correctly on the system PASS: All adapters defined in intent are physical NICs and Up in the system --- No intent found in the system. Skip intent adapter check. I cannot set Vlan on Azure Local server but its already configured at Switch level

Answer 1

To resolve the Network Validation error during Azure Local deployment related to the VLAN ID, you should ensure that the VLAN ID is correctly configured on the network adapter. Here are the steps you can follow:

1. Verify VLAN Configuration: Use the Get-NetAdapterAdvancedProperty command to check the current VLAN ID configuration for the adapter vNIC0. This will help you confirm if the VLAN ID is set correctly.

      Get-NetAdapterAdvancedProperty -Name "vNIC0" -RegistryKeyword "VlanId"
   

2. Set VLAN ID: If the VLAN ID is not set or needs to be changed, use the Set-NetAdapterAdvancedProperty command to configure it. For example:

      Set-NetAdapterAdvancedProperty -Name "vNIC0" -RegistryKeyword "VlanId" -RegistryValue "<YourDesiredVlanId>"
   

   Replace <YourDesiredVlanId> with the appropriate VLAN ID you want to assign.
3. Check Physical Network Adapters: Ensure that the physical network adapters used for the management intent are correctly selected during the deployment process. Do not select virtual network adapters for the network intent.
4. Validate Network Configuration: After making the changes, run the network validation again to ensure that all configurations are correct and that there are no further issues.
5. Refer to Documentation: For more detailed steps and troubleshooting, refer to the Azure documentation regarding network considerations and deployment validation issues.

By following these steps, you should be able to resolve the VLAN ID error and proceed with your Azure Local deployment.

Answer 2

Hello simranjit singh

The validator looked for a VlanId advanced property on a Hyper‑V virtual NIC (vNIC0). Hyper‑V vNICs don’t expose VlanId as an advanced driver property; VLANs must be configured on the vNIC via Hyper‑V/Network ATC. Having VLAN configured only on the physical switch (access mode) caused the validation to fail.

1. Configure VLANs on the host vNICs (preferred via Network ATC intent; alternatively with Set‑VMNetworkAdapterVlan).
2. Ensure the physical switch port is trunking the required VLANs (not forced to access mode).
3. Re-run Azure Local network validation and confirm it passes.

Azure PowerShell

# Show vNICs
Get-VMNetworkAdapter -ManagementOS

# Set VLAN 20 on vNIC0
Set-VMNetworkAdapterVlan -ManagementOS -VMNetworkAdapterName "vNIC0" -Access -VlanId 20

# Verify

Network validation fails during Azure Local deployment because the required network configuration is missing or incorrect.

Validate Network Configuration

• Ensure that the network settings for your Azure Local deployment meet the prerequisites:
  • Proper subnet configuration.
    • Required ports are open.
      • DNS resolution is working.

Open PowerShell with administrative privileges and execute the following commands:

PowerShell

# Import the Azure Stack module
Import-Module -Name Az.StackHCI

# Validate network configuration
Get-AzStackHciDeploymentNetworkValidation -NetworkConfiguration "V

If validation fails, apply the correct configuration using:

Azure PowerShell

Set-AzStackHciDeploymentNetworkConfiguration -NetworkConfiguration "VNET" -Verbose

After applying the configuration, re-run the validation command to confirm:

Azure PowerShell

Get-AzStackHciDeploymentNetworkValidation -NetworkConfiguration

Checks:

1. Verify that the Cluster Network and Management Network are properly configured.
2. Ensure that the Gateway IP, DNS servers, and VLAN settings match your deployment requirements.

Once these steps are completed, the network validation should pass, and you can proceed with the Azure Local deployment.

Thanks,
Manish Deshpande