AKS Edge Essentials - Single Machine Cluster Install

Question

I am trying to complete a local install of AKS Edge Essentials for a "Single Machine Cluster".

The install was going OK, until I hit the network requirement(s). As you can see it appears my local private subnet 192.168.1.0 is being used.

Is there a way to get round this, in configuration of a single machine cluster? Do I need to make adjustments in my Hyper V or make changes in my local home network?

Any help appreciated.

New-AksEdgeDeployment -JsonConfigFilePath .\aksedge-config.json
 - Checking host for required features
 - Checking the status of 'Microsoft-Hyper-V'
 - Checking the status of 'Microsoft-Hyper-V-Management-PowerShell'
 - Checking the status of 'Microsoft-Hyper-V-Hypervisor'
 - Checking the status of 'OpenSSH.Client*'
 - Checking power management settings of the Host
 - Checking HNS version of the Host
 - Checking OpenSSH version of the Host
 - Checking Nested Virtualization of the Host

[12/05/2024 08:56:57] All required host features are installed


[12/05/2024 08:56:57] Validating AksEdge network parameters...

 - Selecting private subnet in the '192.168' network segment...
 - Identified candidate for private subnet: '192.168.1.0'. Validating subnet's gateway IP '192.168.1.1' is free...
WARNING: IP address '192.168.1.1' is not free
 - One or more specified IPs do not seem to be available
 - Identified candidate for private subnet: '192.168.2.0'. Validating subnet's gateway IP '192.168.2.1' is free...
WARNING: IP address '192.168.2.1' is not free
 - One or more specified IPs do not seem to be available
 - Identified candidate for private subnet: '192.168.3.0'. Validating subnet's gateway IP '192.168.3.1' is free...
WARNING: IP address '192.168.3.1' is not free
 - One or more specified IPs do not seem to be available
 - Identified candidate for private subnet: '192.168.4.0'. Validating subnet's gateway IP '192.168.4.1' is free...
WARNING: IP address '192.168.4.1' is not free
 - One or more specified IPs do not seem to be available
 - Identified candidate for private subnet: '192.168.5.0'. Validating subnet's gateway IP '192.168.5.1' is free...
WARNING: IP address '192.168.5.1' is not free
 - One or more specified IPs do not seem to be available
 - Identified candidate for private subnet: '192.168.6.0'. Validating subnet's gateway IP '192.168.6.1' is free...
WARNING: IP address '192.168.6.1' is not free
 - One or more specified IPs do not seem to be available

Answer 1

Hi Duncan House,

The error indicates a conflict with the 192.168.x.x subnet used by AKS Edge Essentials, likely due to existing network settings (e.g., gateway IPs like 192.168.1.1).

Steps to Resolve:

Change Subnet in aksedge-config.json modify the IpAddressPrefix to a non-conflicting range, such as:

"IpAddressPrefix": "10.100.0.0/16"

Verify it doesn’t overlap with your local network.

Create an Internal Network Switch in Hyper-V with an IP range that matches your new IpAddressPrefix.

Use the ping command to check if gateway IPs (e.g., 192.168.x.1) are in use, and free up any conflicting IPs.

After updating the configuration, rerun the New-AksEdgeDeployment command.

For more details, please refer to the below documentation:
Prepare your machines for AKS Edge Essentials
Prepare your nested virtualization environment for AKS Edge Essentials

If an answer has been helpful, please consider accept the answer and "Upvote" to help increase visibility of this question for other members of the Microsoft Q&A community.