Hyper-V Failover Cluster High Level Design & Architecture


High Level Design & Architecture

 

Hyper-v.jpg

tt

 

1.1      Hardware Requirements and Prerequisites

1.1.1       Host (Server)

  • Use a set of matching server host that contain the same or similar components.
  • CPU, RAM must be good enough for hosting VMs
  • A 64-bit processor with second level address translation (SLAT).
  • Virtualization support turned on in the BIOS or UEFI.
  • Hardware-assisted virtualization.
  • Hardware-enforced Data Execution Prevention (DEP)

1.1.2       Network adapters and Cable

  • NIC drivers is compatible and up-to-date
  • NIC Teaming (LBFO) recommendations
    • Teaming mode: Switch Independent (the default setting)
    • Load balancing mode: Hyper-V Port
  • avoid having single points of failure in the network infrastructure (VLAN, Separated physical Switch, NIC Teaming, Multipath, Isolated Network)
  • Virtual Switches, must have the same name on all the hosts
  • In order, VM, Management, and Cluster NIC must be the first Network Providers (NIC Advance Settings)
    • Managements and VM the 1st providers
  • Design the Network (and Virtual Switch) depending on traffic type:
Network Traffic Type NIC Prosperities Network isolation (Cluster Communication) Weight Description
Management Default settings Both of the following:

– Allow cluster network communication on this network
– Allow clients to connect through this network

10 – Provides connectivity between the server that is running Hyper-V and basic infrastructure functionality.
– Used to manage the Hyper-V management operating system and virtual machines.
Cluster (HB) ·   NO Gateway, NO DNS

·   uncheck File and Printer Sharing for Microsoft Networks,

·   Uncheck Client for Microsoft network

·   Uncheck Register in DNS,

·   disable NetBIOS over TCP/IP in WINS,

·   Uncheck LMHOSTS lookup in WINS

 

Allow cluster network communication on this network Note: Clear the Allow clients to connect through this network check box. 10 – Used for inter-node cluster communication such as the cluster heartbeat and Cluster Shared Volumes (CSV) redirection.
Live migration (LM) 40 – Used for virtual machine live migration.
Storage Do not allow cluster network communication on this network 40 – Used for SMB traffic or for iSCSI traffic.
Replica traffic Default settings Both of the following:

– Allow cluster network communication on this network
– Allow clients to connect through this network

10 – Used for virtual machine replication through the Hyper-V Replica feature.
Virtual machine access (VM) Disable and Uncheck IPv4, IPv6

 

non 1, 3 or 5 (low, medium and high-throughput virtual machines) – Used for virtual machine connectivity.
– requires external network connectivity to service client requests.

 

1.1.3        Storage and Device controllers

  • use shared storage that is compatible with Windows Server 2016
  • should contain multiple, separate disks (logical unit numbers, or LUNs) that are configured at the hardware level
  • All elements of the storage stack should be identical.  HBA driver and firmware, multipath, adapters.
  • All the disk should be accessed by all the Cluster Nodes
  • Storage Disk Design
Disk type Formant partitioning structures Size Cluster Shared Volume Backup & Antivirus Number of Disk Type
Quorum (Disk witness) NTFS, ReFS MBR 1 GB, at least 512 MB Not Clustered excluded One Disk
Clustered Disk (CSV) NTFS MBR, GPT Depend on the Size VMs Clustered Include Multi-Disks

 

1.2      Roles, Features and Software Prerequisites

all Hyper-V host nodes

  • Install Multipath feature or 3rd party software
  • Install ISCSI Feature or 3rd party software
  • Install Hyper-V Role
  • Install Failover Cluster Role
  • Install OS Host Fixes for Cluster
  • Fully update the Cluster Nodes

For Cluster Aware Updating

  • Enable Windows Management Instrumentation
  • Enable Windows PowerShell and Windows PowerShell remoting
  • Install .NET Framework 4.5
  • Enable a firewall rule to allow automatic restarts
  • Prestage Computer Object for the CAU

1.3      Accounts and Permissions

Create the following accounts in Active Directory

Account Name Description
HVCLAdmin Cluster admin and Installation Account
HVClusteradmins Cluster Administrators security group

 

    • Installation cluster Account:
      • Administrative and local permissions on the servers’ nodes.
      • Create Computer objects and Read All Properties permissions in the Cluster container (include this object all descendant objects)
    • Cluster Admin Account
      • Administrative and local permissions on the servers’ nodes.
      •  Full Control permissions in the Cluster container (include this object all descendant objects)
    • Prestage Computer Object for the Cluster Name
      • Full control and permission on the cluster container
    • Prestage Computer Object for the Cluster Aware Updating Server
      • Full control and permission on the cluster container

1.4      Additional prerequisites

  • Prepare Cluster Name and IP address
  • Make sure that all servers that you want to add as cluster nodes are joined to the same Active Directory domain
  • Prestage Cluster Computer Objects in Active Directory Domain Services
  • Create an organizational unit (OU) and move the computer accounts for the servers that you want to add as cluster nodes into the OU, with the Cluster Computer object
  • Validate the Configuration – Run all tests (recommended), before creating the cluster
  • Install the Hotfix and updates After installing Failover Cluster Role
  • Allow cluster to dynamically manage the assignment of node votesoption
Advertisements