AzStackHciNetworkTestNewNodeAndIP_Match

January 30, 2026 · View on GitHub

Name	AzStackHci_Network_Test_New_Node_And_IP_Match
Severity	Critical: This validator will block operations until remediated.
Applicable Scenarios	Add-Server

Overview

This validator checks that the new node's hostname and management IP address match the expected configuration provided in the Add-Server operation. The node name retrieved from the system must correspond to the management IP address assigned to that node.

Requirements

The new node must meet the following requirement:

The node's hostname must match the expected configuration for its management IP address

Troubleshooting Steps

Review Environment Validator Output

Review the Environment Validator output JSON. Check the AdditionalData.Detail field for information about the node name and IP mismatch. The TargetResourceID shows the management IP address.

{
  "Name": "AzStackHci_Network_Test_New_Node_And_IP_Match",
  "DisplayName": "Test New Node Configuration Name and IP Match",
  "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.1.50",
  "TargetResourceName": "IPAddress",
  "TargetResourceType": "IPAddress",
  "Timestamp": "\\/Date(timestamp)\\/",
  "AdditionalData": {
    "Source": "NodeAndManagementIPMapping",
    "Resource": "NewNodeNameAndManagementIP",
    "Detail": "New Node Mgmt IP '10.0.1.50' is not on the New Node. Found instead on 'NODE1'",
    "Status": "FAILURE",
    "TimeStamp": "<timestamp>"
  }
}

Failure: Node Name and IP Do Not Match Expected Configuration

Error Message:

New Node Mgmt IP '10.0.1.50' is not on the New Node. Found instead on 'NODE1'

Root Cause: The management IP address being used for the Add-Server operation is associated with a different node than expected. This typically indicates a configuration mismatch where:

The wrong IP address was specified in the Add-Server configuration
The node hostname doesn't match the expected mapping
The node was not properly configured before Add-Server

Remediation Steps

Verify Node Configuration

Check the actual node name and IP configuration on the node being added:

# Run on the node being added
$computerName = $env:COMPUTERNAME
$mgmtIP = (Get-NetIPConfiguration | Where-Object {
    $null -ne $_.IPv4DefaultGateway -and
    $_.NetAdapter.Status -eq "Up"
}).IPv4Address.IPAddress

Write-Host "Actual Node Name: $computerName"
Write-Host "Actual Management IP: $mgmtIP"

Compare with the expected configuration:
- Expected Node Name: (from Add-Server configuration)
- Expected Management IP: (from error message, e.g., 10.0.1.50)

Option 1: Correct the Add-Server Configuration (If Wrong IP Specified)

If the Add-Server configuration specifies the wrong IP address:

Review the Add-Server parameters and retry with the corrected configuration.

Option 2: Rename the Node (If Wrong Hostname)

If the node has the wrong hostname:

Check if the node needs to be renamed to match the expected configuration:
Rename the computer (requires restart):
After the node restarts, verify the name change:
```
$env:COMPUTERNAME
```
Retry the Add-Server operation.

Warning: Renaming a computer requires a restart and will temporarily disconnect the node.

Option 3: Reconfigure the Node's Management IP (If Wrong IP)

If the node has the wrong management IP configured:

Determine the correct IP address for this node from your deployment plan.
On the node being added, change the management IP:
Retry the Add-Server operation.

Additional Information

Understanding the Node Name and IP Mapping

During Add-Server operations, Azure Local expects:

A specific node name to be added (e.g., NODE4)
A specific management IP for that node (e.g., 10.0.1.13)
The hostname and IP must match on the actual node

This validator ensures the mapping is correct before proceeding with the add operation.

Best Practices for Add-Server Preparation

Pre-configure the node:
- Set the correct hostname
- Configure the correct management IP
- Verify network connectivity
- Document the configuration

Create a deployment checklist:

Node Preparation Checklist:
☐ Hostname set to: NODE4
☐ Management IP: 10.0.1.13 /24
☐ Gateway: 10.0.1.1
☐ DNS: 10.0.1.1
☐ Network connectivity tested
☐ Time synchronized with cluster

Verify before Add-Server:

# Run on the node before adding to cluster
$computerName = $env:COMPUTERNAME
$mgmtIP = (Get-NetIPConfiguration | Where-Object {
    $null -ne $_.IPv4DefaultGateway -and
    $_.NetAdapter.Status -eq "Up"
}).IPv4Address.IPAddress

Write-Host "Node Name: $computerName"
Write-Host "Management IP: $mgmtIP"
Write-Host ""
Write-Host "Expected Node Name: NODE4"
Write-Host "Expected Management IP: 10.0.1.13"
Write-Host ""
if ($computerName -eq "NODE4" -and $mgmtIP -eq "10.0.1.13") {
    Write-Host "✓ Configuration matches expectations" -ForegroundColor Green
} else {
    Write-Host "✗ Configuration does NOT match expectations" -ForegroundColor Red
}

Example Deployment Plan

For adding NODE4 to an existing 3-node cluster:

Node	Expected Hostname	Expected Management IP	Status
NODE1	NODE1	10.0.1.10	Existing
NODE2	NODE2	10.0.1.11	Existing
NODE3	NODE3	10.0.1.12	Existing
NODE4	NODE4	10.0.1.13	Being Added

Before running Add-Server:

Configure NODE4 with hostname "NODE4"
Configure NODE4 with IP 10.0.1.13
Verify configuration matches expectations
Run Add-Server with NODE4/10.0.1.13 configuration