Error adding 3rd node to my Azure Local stack

Question

Getting the following error when adding a node and I can't figure out what needs fixed.

FullStepIndex: 1.4

RolePath: Cloud\Infrastructure\EnvironmentValidator

Interface: ValidateScaleOutNetwork

StackTrace:

CloudEngine.Actions.InterfaceInvocationFailedException: Type 'ValidateScaleOutNetwork' of Role 'EnvironmentValidator' raised an exception:

{

"ExceptionType":  "json",

"ErrorMessage":  {

                     "Message":  "Network requirements not met. Review output and remediate.",

                     "Results":  {

                                     "Name":  "AzStackHci_Network_Test_New_Node_And_IP_Match",

                                     "DisplayName":  "Test New Node Configuration Name and IP Match",

                                     "Tags":  {

                                              },

                                     "Title":  "Test New Node Configuration Name and IP Match",

                                     "Status":  1,

                                     "Severity":  2,

                                     "Description":  "Checking New Node Name and IP match",

                                     "Remediation":  "https://aka.ms/hci-envch",

                                     "TargetResourceID":  "10.0.99.15",

                                     "TargetResourceName":  "IPAddress",

                                     "TargetResourceType":  "IPAddress",

                                     "Timestamp":  "\/Date(1754069486382)\/",

                                     "AdditionalData":  {

                                                            "Detail":  "New Node Mgmt IP \u002710.0.99.15\u0027 is not on the New Node. Found instead on \u0027\u0027",

                                                            "Status":  "FAILURE",

                                                            "TimeStamp":  "08/01/2025 17:31:26",

                                                            "Resource":  "NewNodeNameAndManagementIP",

                                                            "Source":  "NodeAndManagementIPMapping"

                                                        },

                                     "HealthCheckSource":  "AddNode\\Medium\\Network\\e3c1b510"

                                 }

                 },

This is claiming the management IP is not correct but it is.

Answer 1

You're seeing this error:

“New Node Mgmt IP '10.0.99.15' is not on the New Node. Found instead on ''”

This means:

The IP address 10.0.99.15 is not detected on the new node you're adding.

The system sees that IP on the network, but it's not mapped to the new node as expected.

As a result, the health check AzStackHci_Network_Test_New_Node_And_IP_Match fails.

Is likely IP Already Used by Another Device

Run ping 10.0.99.15 and arp -a from another machine.

Check if another server or device has that IP.

The IP must be free and assigned only to the new node.

New Node Does Not Have the IP Assigned

Log into the new node directly.



Run:

"Get-NetIPAddress -AddressFamily IPv4"

Confirm the IP 10.0.99.15 is actually assigned.

Also run:

"Get-NetIPConfiguration"

and check if it's on the correct NIC, with valid subnet/gateway.

Automated Configuration Missed It

If you're using a JSON or scripted config to deploy nodes (like NodeConfiguration.json), verify the management IP is correctly defined and applied.

Firewall/DNS Conflict

Make sure there are no firewall rules blocking node communication.

Check DNS to ensure the IP isn't mapped to a different hostname.

😊 If my answer helped you resolve your issue, please consider marking it as the correct answer. This helps others in the community find solutions more easily. Thanks!

Answer 2

Hi DA-Jeremy Nusser

If you have thoroughly confirmed that the IP 10.0.99.15 is present and correctly assigned to the new node, but Azure Stack HCI’s validator still reports New Node Mgmt IP '10.0.99.15' is not on the New Node.

Ensure the IP is assigned to the correct physical NIC/interface. Sometimes the IP ends up on the wrong interface, which the validator won’t accept. In Windows Admin Center, verify that the management network profile for the node matches your intended configuration.

Verify No Other Devices Hold the IP: Ensure that no switches, VMs, or other servers have this IP in their ARP tables.

The validator uses both forward and reverse DNS lookups when matching an IP to a node. If your PTR record or forward record doesn’t match the new node’s hostname, the test will fail with exactly your symptom.

Answer 3

@DA-Jeremy Nusser Did you ever find a solution for this error when adding another node?