Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.

Dell Microsoft Azure Stack HCI-klyngeimplementering

Summary: Oplysninger indeholder trin til implementering af en Microsoft Azure HCI S2D-klynge som beskrevet i implementeringsvejledningen "Microsoft HCI-løsninger fra Dell Technologies".

This article may have been automatically translated. If you have any feedback regarding its quality, please let us know using the form at the bottom of this page.

Article Content


Instructions

Skærmbilledet nedenfor viser miljøet for en tonode HCI-klynge på et switch-netværk.  PowerShell-oplysningerne nedenfor er tilpasset til denne konfiguration, men er stadig nyttige med modifikationer til klynger med flere noder og en switchfri netværkstopologi.


Diagram over Microsoft Azure Stack HCI-klynge med to noder i et Windows Active Directory-switchnetværksmiljø.
 
Scripteksempel nedenfor og installationsprocessen findes på side 12-21 i implementeringsvejledningen til .PDF-versionen "Microsoft HCI Solutions from Dell Technologies".
Script kører trin, når klyngenoderne har haft operativsystemer installeret, føjet til et Active Directory-domæne, og det fremtidige klyngenetværk er blevet etableret.


Konfigurationselementer:
  • Installation af Windows-funktion: Hyper-V, Failover-Clustering, Data-Center-Bridging, BitLocker, FS-FileServer, RSAT-Clustering-PowerShell, FS-Data-Deduplikering
  • Kontrol af driveropdatering:  Kontroller supportmatrixen
  • Omdøb klyngenoder
  • Klyngetest, validering
  • Opret S2D-klynge
  • Enable Storage Spaces Direct
  • Angiv værtsprioriteten "Administration" for live migrering
  • Indstillinger for sidefil: Allow for Memory Dump space (Tillad hukommelsesdumpplads)
  • Konfigurer klyngevidne
  • Spaces port timeout configuration (Konfiguration af timeout for spaces-port)
Scripteksempel nedenfor skal tilpasses det miljø, hvor HCI-klyngen implementeres.  Servernavne, klyngenavn, klyngedelingsnavn og IP-oplysninger skal ændres for at opfylde parametrene for installationsmiljøet.
Når du kopierer scriptteksten nedenfor til det tiltænkte implementeringsscript, skal du sørge for ikke at vikle PowerShell-tekst.

#Windows funktionsinstallation:
Install-WindowsFeature -Name Hyper-V, Failover-Clustering, Data-Center-Bridging, BitLocker, FS-FileServer, RSAT-Clustering-PowerShell, FS-Data-Deduplication -IncludeAllSubFeature
-IncludeManagementTools -verbose



#Retrieve liste over driverversioner:
Get-PnpDevice | Select-Object Name, @{l='DriverVersion';e={(Get-PnpDeviceProperty -InstanceId $_.InstanceId -KeyName 'DEVPKEY_Device_DriverVersion').Data}} -Unique |
Where-Object {($_.Name -like "*HBA*") -or ($_.Name -like "*mellanox*") -or ($_.Name -like "*Qlogic*") -or ($_.Name -like "*X710*") -or ($_.Name -like "*intel*") -or ($_.Name -like "*Broadcom*") -or ($_.Name -like "*marvell*") }



#Assign klyngenodenavn:
Rename-Computer -NewName CN01 -Restart


#Cluster test
Test-Cluster -Node CN01, CN02 –Include 'Storage Spaces Direct', 'Inventory', 'Network', 'System Configuration'



#Find status for lagerpuljediske
Get-PhysicalDisk



#Creating ny S2D-klynge:
New-Cluster -Name S2DSystem -Node CN01, CN02 -StaticAddress 192.168.10.33 -NoStorage -IgnoreNetwork 172.16.103.0/24, 172.16.104.0/24 -Verbose


#Enabling Storage Spaces Direct:
Enable-ClusterS2D -Verbose



##Capturing resultater af tidligere kommandoer
Get-ClusterS2D
Get-StoragePool
Get-StorageSubSystem -FriendlyName *Cluster* | Get-StorageHealthReport



#Configure værtsadministrationsnetværk med lavere prioritet for Live Migration:
$clusterResourceType = Get-ClusterResourceType -Name 'Virtual Machine'
$hostNetworkID = Get-ClusterNetwork | Where-Object { $_.Address -eq ‘192.168.10.0’ } |
Select-Object -ExpandProperty ID
$otherNetworkID = (Get-ClusterNetwork).Where({$_.ID -ne $hostnetworkID}).ID
$newMigrationOrder = ($otherNetworkID + $hostNetworkID) -join ';'
Set-ClusterParameter -InputObject $clusterResourceType -Name MigrationNetworkOrder -Value
$newMigrationOrder
Set-VmHost -VirtualMachine MigrationPerformanceOption SMB



#Page filindstillinger for at sikre, at hukommelsesdumpfilen kan optages:
$blockCacheMB = (Get-Cluster).BlockCacheSize

$blockCacheMB = (Get-Cluster).BlockCacheSize
$pageFilePath = "C:\pagefile.sys"
$initialSize = [Math]::Round(51200 + $blockCacheMB)
$maximumSize = [Math]::Round(51200 + $blockCacheMB)
$system = Get-WmiObject -Class Win32_ComputerSystem -EnableAllPrivileges
if ($system.AutomaticManagedPagefile) {
$system.AutomaticManagedPagefile = $false
$system.Put()
}
$currentPageFile = Get-WmiObject -Class Win32_PageFileSetting
if ($currentPageFile.Name -eq $pageFilePath)
{
$currentPageFile.InitialSize = $InitialSize
$currentPageFile.MaximumSize = $MaximumSize
$currentPageFile.Put()
}else{
$currentPageFile.Delete()
Set-WmiInstance -Class Win32_PageFileSetting -Arguments @{Name=$pageFilePath;
InitialSize = $initialSize; MaximumSize = $maximumSize}
}
#Configure cluster witness. Active Directory Cluster Name Object must be given write access on file #share before running this step:
Set-ClusterQuorum -NodeAndFileShareMajority \\VDC01\ClusterQuorum


#Disable SMB-signering; deaktiveret som standard med normal Installation af Windows Server
Set-SmbServerConfiguration -RequireSecuritySignature $FALSE -force



#Spaces ændring af konfiguration af porttimeout:
Set-ItemProperty -Path HKLM:\SYSTEM\CurrentControlSet\Services\spaceport \Parameters -Name HwTimeout -Value 0x00002710 -Verbose Restart-Computer -Force


Article Properties


Affected Product

Hyper-converged Systems, Microsoft Windows Server 2022

Product

Microsoft Windows Server 2016, Microsoft Windows Server 2019, Microsoft Windows Server 2022

Last Published Date

12 May 2023

Version

6

Article Type

How To