Your Browser is Out of Date

Nytro.ai uses technology that works best in other browsers.
For a full experience use one of the browsers below
E2E Deployment and Operations Guide with Stretched Cluster: Integrated System for Microsoft Azure Stack HCI
About using this guide Introduction Solution overview Solution deployment Creating a stretched cluster
Creating a stretched cluster
Introduction
Test-Cluster
Cluster creation
Configuring host networking
Creating a cluster
Configuring a cluster witness
Creating required intents for a stretched cluster
Volumes
Storage efficiency
Test-SRTopology
Virtual Machines Failure/Recovery from failure of Site/Node Appendices Day 1 operations Managing and monitoring clusters with Windows Admin Center Dell OpenManage Integration with Windows Admin Center Updates and maintenance References

Cluster creation

Home > Integrated Products > Microsoft HCI Solutions from Dell Technologies > Guides 22H2 and earlier > E2E Deployment and Operations Guide with Stretched Cluster: Integrated System for Microsoft Azure Stack HCI > Cluster creation

Cluster creation

  • 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.
    Note: Cluster witness can be either on a tertiary site or on Azure Cloud. Ensure that the "Storage Replica" feature is installed on all nodes in 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:

    Figure 7. IP subnets in an Active Directory
    If both sites are in the same IP network, use the New-ClusterFaultDomain cmdlet to define the two site names. Site names defined using New-ClusterFaultDomain override the names given in Active Directory.
    Note: Configure cluster witness and enable Storage Spaces Direct on the cluster.

    Note: PowerShell commands for configuring the sites using New-ClusterFaultDomain is mentioned in the following sections.

    The following is a sample image of how sites appears in Failover Cluster Manager:

    Figure 8. Sites in Failover Cluster Manager

    Once a cluster is created, use Failover Cluster Manager to rename the cluster networks.