This article describes the steps to create a Two-Node Windows 2012r2 Cluster to be used for storage services as well as host Hyper-V VMs.
- Both nodes should be domain joined
- Prerequisite Roles and Features installed (see Windows Cluster and Storage Spaces Prerequisite Roles and Features)
- Multipath IO must be installed and configured (see Configuring Multipath IO on Windows Cluster Systems)
- The initial network configuration should be complete. Additional networks can be added at anytime.
- Interconnection networks should be configured and active
- One network port common to all cluster members should be configured and active (see Configure network ports on Windows Clustered Systems)
- Mellanox network cards should be available to support RDMA (see Installing Mellanox Network Card device drivers)
- Storage Pools and Virtual Disks should be configured and active
Validate the Cluster
Log onto one of the systems using a domain administrator account. This procedure is run on only one node.
Run PowerShell command which runs the Cluster Validation: PowerShell
|1||Test-Cluster –Node node-1,node-2|
Note: This procedure can be run from the Cluster Failover Manager console. If there are errors in the validation, troubleshooting from the Cluster Failover Manager console is a simpler process.
This process will typically report completion with warning messages. We can still continue on and create the cluster. We will come back at the end and handle outstanding warning issues. The warnings in this case say that we have only single network connections to Node-1 and Node-2 which is not high availability. This will be remedied as later as more networks are added If the warnings look more severe, then this process can be run from the Cluster Manager Console which will display complete error and warning reports interactively.
Create the Cluster
Run the following command to create the cluster. PowerShell
|1||New-Cluster -Name MyCluster -Node node-1,node-2 -NoStorage -StaticAddress 188.8.131.52|
Note: Select relevant node names, addresses and cluster names for your environment. Note: The NoStorage parameter was selected so we can include only the relevant storage resources. By default New-Cluster will move all discovered storage to the cluster as a resource and often create a disk witness on whatever disks or virtual disks it finds, which is likely not desirable. Note: This can be completed from the Failover Cluster Manager console, but be sure to NOT select the add storage checkbox.
The screen above shows the output of the New-Cluster command.
When you bring up the Failover Cluster Manager GUI you should see a functioning cluster.
The next steps will be to configure the storage and networks as cluster resources.
- Windows Cluster and Storage Spaces Prerequisite Roles and Features Each cluster member server requires a set of Windows Roles and Features to be installed and configured. Open a PowerShell window and run the following commands on all…
- Create the Windows Cluster We will now create the Windows 2016 or 2012r2 cluster on the domain joined systems. Log onto one of the systems using a domain administrator account. This procedure is run…
- Fault Domain Awareness in WS2016 – Part 1: Overview Rack outage? Storage Spaces Direct doesn’t sweat it. Find out how. Failover Clustering enables multiple servers to work together to provide high availability – or put another way, to…
- Fault Domain Awareness in WS2016 – Part 4: Location, Description Rack outage? Storage Spaces Direct doesn’t sweat it. Find out how. Failover Clustering enables multiple servers to work together to provide high availability – or put another way, to…
- Fault Domain Awareness in WS2016 – Part 3: Using XML Rack outage? Storage Spaces Direct doesn’t sweat it. Find out how. Failover Clustering enables multiple servers to work together to provide high availability – or put another way, to…