Azure Local - Add Node Error

Question

Azure Local - Add Node Error

Luke Jackson 0

We have recently deployed an Azure Local cluster with two nodes, tested and would like to add an additional Node to the cluster.

The additional node is identical in hardware spec etc. (HPE DL380 Gen11 servers)

I am running: "Add-Server -Name "NODENAME" -HostIpv4 "NODEIP" -LocalAdminCredential <credentials>

The process was running fine but has now errored out completeld on step 80.1, which is relating to: Prepare ATC Local intent on new server before joing into cluster.

The full error I receive is:

Error Details:

----------------------------------------

FullStepIndex: 80.1

RolePath: Cloud\Infrastructure\HostNetwork

Interface: HostNetworkScaleOutPrepareLocalATCOnNewNodeBeforeClusterJoin

StackTrace:

CloudEngine.Actions.InterfaceInvocationFailedException: Type 'HostNetworkScaleOutPrepareLocalATCOnNewNodeBeforeClusterJoin' of Role 'HostNetwork' raised an exception:

Cannot process argument transformation on parameter 'StorageVlans'. Cannot convert value "NN" to type "System.Int32". Error: "Input string was not in a correct format."

at ConfigureHostAdaptersWithNetworkAtcForHosts, C:\NugetStore\Microsoft.AS.Network.Deploy.HostNetwork.1.2506.0.26\content\Powershell\Roles\HostNetwork\HostNetwork.psm1: line 2255

at Set-HostAdaptersWithNetworkAtc, C:\NugetStore\Microsoft.AS.Network.Deploy.HostNetwork.1.2506.0.26\content\Powershell\Roles\HostNetwork\HostNetwork.psm1: line 2399

at <ScriptBlock>, <No file>: line 28

at CloudEngine.Actions.PowerShellHost.WaitAndReceiveJob(Job job, CancellationToken token, UInt32 timeoutSeconds, Stopwatch watch)

at CloudEngine.Actions.PowerShellHost.Invoke(InterfaceParameters parameters, CancellationToken token, UInt32 timeoutSeconds, ThrottlingDescription throttlingDesc)

at CloudEngine.Actions.InterfaceTask.Invoke(Configuration roleConfiguration, String startStep, String endStep, String[] skip, Nullable`1 retries, Nullable`1 interfaceTimeout, CancellationToken token, Dictionary`2 runtimeParameter, Boolean runInProcess, String storeName, String storeRoot)

I can't seem to determine the error here, the log suggests it's passing a string value to something that only accepts an int and that value is the VLAN, for some reason it's passing "NN" when it should be passing 711/712 as the VLAN ID's

I can create the Intent manually on the node and it works correctly, however the Add-Server process overwrites this and I get the same error.

Any assistance would be appreciated.

Himanshu Shekhar 255 Reputation points Microsoft External Staff Moderator

2025-08-20T18:39:13.77+00:00
Hello Luke Jackson

Welcome to Microsoft Q&A Platform. Thank you for reaching out & hope you are doing well.

Please let us know about few queries below:

How are VLANs typically configured in your cluster - PowerShell, JSON, or wizard?

Has this error appeared on a previous node?

Are all NICs and adapters (name, binding, firmware) on the new server identical to the existing ones?

Do you find any "NN" values in the network intent configuration files, scripts, or variables for any node?

Also please refer few Microsoft documentations below for details

Manage network atc - https://learn.microsoft.com/en-us/windows-server/networking/network-atc/manage-network-atc

Known issue azure local - https://learn.microsoft.com/en-us/azure/azure-local/known-issues?view=azloc-2507

Health service faults https://learn.microsoft.com/en-us/azure/azure-local/manage/health-service-faults?view=azloc-2506
Himanshu Shekhar 255 Reputation points Microsoft External Staff Moderator

2025-08-25T18:52:11.5133333+00:00

Hello Luke Jackson

Could you please provide an update on this post?

Kindly let us know if the suggested steps helps or you need further assistance on this issue.

1 answer

Your answer

Himanshu Shekhar 255 Reputation points Microsoft External Staff Moderator

2025-08-20T18:39:13.77+00:00

Hello Luke Jackson

Welcome to Microsoft Q&A Platform. Thank you for reaching out & hope you are doing well.

Please let us know about few queries below:

How are VLANs typically configured in your cluster - PowerShell, JSON, or wizard?

Has this error appeared on a previous node?

Are all NICs and adapters (name, binding, firmware) on the new server identical to the existing ones?

Do you find any "NN" values in the network intent configuration files, scripts, or variables for any node?

Also please refer few Microsoft documentations below for details

Manage network atc - https://learn.microsoft.com/en-us/windows-server/networking/network-atc/manage-network-atc

Known issue azure local - https://learn.microsoft.com/en-us/azure/azure-local/known-issues?view=azloc-2507

Health service faults https://learn.microsoft.com/en-us/azure/azure-local/manage/health-service-faults?view=azloc-2506
Himanshu Shekhar 255 Reputation points Microsoft External Staff Moderator

2025-08-25T18:52:11.5133333+00:00

Hello Luke Jackson

Could you please provide an update on this post?

Kindly let us know if the suggested steps helps or you need further assistance on this issue.

Answer 1

Luke Jackson 0

Managed to resolve this so the answer in my case for clarity that anyone may find.

As part of testing Azure Local we removed the storage intent to add an additional NIC to the storage intent itself, we did this from the WAC console - doing this doesn't seem to tag (or give you the options to) VLANs on the Intent.

We had to revert this change, manually create the intent again with PowerShell and ensure you pass through the -StorageVLANs to the cmdlet then resume the wizard.

Share via

Azure Local - Add Node Error

1 answer

Your answer