This section looks at creating a cluster using PowerShell cmdlets.
Manual cluster creation
Once Test-Cluster completes successfully, use the
New-Cluster cmdlet to create a new stretched cluster. Because the nodes specified are part of different IP schemas, Enable-ClusterS2D understands that the cluster is part of a multi-site topology. It automatically creates two storage pools and corresponding ClusterPerformanceHistory volumes and their replica volumes.
After a cluster is created, you will see a warning similar to the following example. This is an expected behavior.
No matching network interface found for resource 'Cluster IP Address 172.18.160.160' IP address '192.168.200.100' (return code was '5035'). If your cluster nodes span different subnets, this may be normal.
Configure cluster witness and Enable Storage Spaces Direct on the cluster.
If Sites and Services with IP Subnets are configured on Active Directory, Failover Cluster Manager correctly shows a node to Site mapping, under Cluster Name >> Nodes.
The following is a sample image of IP subnets defined in an Active Directory:
New-ClusterFaultDomaincmdlet to define the two site names. Site names defined using
New-ClusterFaultDomainoverride the names given in Active Directory.
The following is a sample image of how sites appears in Failover Cluster Manager:
Once a cluster is created, use Failover Cluster Manager to rename the cluster networks.