Cluster: can't create new cluster, static address not found on any network

[GeordieGuy]

I am trying to create the first node of a two node WFOC cluster, the configuration is;

	xCluster CreateCluster
	{
		Name = "server01"
		StaticIPAddress = "10.12.4.15/24"
		DomainAdministratorCredential = $AdminCreds
		DependsOn = '[WindowsFeature]AddRemoteServerAdministrationToolsClusteringCmdInterfaceFeature'
	}

This is on Windows Server 2012 R2, that was deployed via an ARM template that also deploys a 10.12.4.0/24 vnet and an Azure ALB with the IP 10.12.4.15. The error thrown is;

Set-AzureRmVmDscExtension : Long running operation failed with status 'Failed'. Additional Info:'VM has reported a failure when processing extension 'Microsoft.Powershell.DSC'. Error message: "DSC Configuration 'MyAOAG' completed with error(s). Following are the first few: PowerShell DSC resource MSFT_xCluster failed to execute Set-TargetResource functionality with error message: The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: Static address '10.12.4.15/24' was not found on any cluster network. The SendConfigurationApply function did not succeed.".'

This is with version 2.72

[johlju]

For the community to help with this

Could you provide the arm template in a https://gist.github.com? Obfuscating any sensitive information.
Could you list the NIC configuration on the VM where you run the configuration?

[GeordieGuy]

Gist: https://gist.github.com/GeordieGuy/a521f53a5e243badff54b6df3f23f4c0
Please note I've find-and-replaced sensitive information which may have replaced an element of the json with something invalid, that's not the problem, it's just to sanitise the info.

The nic configuration is in that gist, but directly it has the static IP address 10.12.4.9. There's another server with 10.12.4.10 as the static IP, and the DSC as shown above is to create a cluster network address with 10.12.4.15. That's the same IP as an Azure load balancer in the same ARM template.

[johlju]

The JSON ARM template deployed successfully, so it seems to work after you replaced sensitive information. Although, just deployed it, did not test anything.

Please look at issue #29 and issue #173 and see if they can help with this.

[sun2silicon]

The fix seems to be that all the nodes must have a Default Gateway IP address. It doesn't have to be a real gateway, just an IP in the same range.

And now the cluster is created with no problems. After the cluster is running, you can remove the gateway IP address.