Forum Widgets
Latest Discussions
Azure Stack HCI - adding NIC to Network ATC Intent
Hello fellow Azure Stack HCI Admins, I currently have a compute_management Intent for my two node switchless cluster with only one pNIC per node (port1) assigned. I now want to add port2 of each node to the intent for redundancy. (See image) I found this command-set on learn: https://learn.microsoft.com/en-us/azure-stack/hci/manage/manage-network-atc?tabs=21H2&pivots=azure-stack-hci Get-NetIntentStatus -ClusterName <YourClusterName> Update-NetIntentAdapter -IntentName <YourIntentName> -AdapterName pNIC2 Get-NetIntentStatus -ClusterName <YourClusterName> Is that the correct command set to archive that? Or is there another way to do so? I am a bit anxious on running those commands because I already have workloads deployed on that cluster and I don't want to break it. Thanks in advance! :) PS: I chose only one NIC per node because at the time of deployment I only had one ToR switch available.
Starting VMs may fail after installation of 10-2023 CU when Veeam RCT is being used -SOLVED-
Dear community, Please consider reading this article https://learn.microsoft.com/en-us/answers/questions/1390624/virtual-machines-failed-to-start-after-installing?page=2#answers in case you are directly affected by the issue, that Hyper-V VMs fail to start, in the certain scenario described below. The issue is not related to VMs not starting on VMware ESXi after applying current CUs. Find remediation instructions for https://kb.vmware.com/s/article/90947 Affected Hosts: Hyper-V Hosts OS: Windows Server 2019 (by community) Windows Server 2022 (by community) Azure Stack HCI 22H2 (experienced myself) Scenario: Gen1 / Gen2 VMs backed up by Veeam using RCT (Change Block Tracking) Not completely confirmed but it seems that unclustered VMs are affected, and clustered VMs are not affected. In a case this morning this caused the unclustered Domain Controllers dedicated for the Azure Stack HCI cluster to fail. edit: 19. Oct. 2023: clustered and unclustered VMs are affected. Reasons: Microsoft has made changes, fixing a long-standing performance issue with Veeam RCT feature, but the fix this can cause a side-effect. The fix is not mentioned in the change log (Windows Update history), despite the criticality of the improvement. https://forums.veeam.com/memberlist.php?mode=viewprofile&u=55718 wrote: https://forums.veeam.com/post500560.html#p500560Oct 09, 2023 10:15 pmThe long awaited 'RCT fix', for the RCT side of this ongoing issue, should be released in the October 2023 Windows update, ie tomorrow!" example of perf. improvements during Veeam backups using RCT from the community: Root cause: directly related to Veeam RCT and CU 10-2023, yet unknown why it happens. Reproducible: yes, 100% in certain scenarios. The https://aka.ms/hci-slack is voluntarily working on the reproducibility in more scenarios to understand the dependencies. Remediation: a. rename or delete MCT / RCT files (quick and dirty). Keep the files if you want Microsoft Support / Veeam Support to engage on this issue. b. uninstall the CU 10-2023 from your cluster (I cannot recommend that for several reasons), using manual suspending of nodes, WUSA and monitor migration and storage replication jobs to be finished before and after restarting nodes. Solution: Deploy Cumulative Update 11-2023, instead of 10-2023 on affected Hyper-V hosts. kudos: ErnieCostaCVLT Jaromir Kaspar Darryl van der Peijl
MSLab Azure Stack HCI: Waiting until SBL Disks are surfaced.
Hi everyone, Still trying to get an Azure Stack HCI Lab run on my rig. Came far thanks to MSLabs and sorts. Scenario: Azure Stack HCI 22N2 using nested virtualization. Parent OS Windows 11 22H2 Parent Virtualization: Hyper-V Storage HW: 2x Samsung 970 Evo NVMe pooled in Storage Space. S2D Cluster Storage: 4x VHDX each 256 GB, per cluster node (2 cluster nodes) expected behaviour: I hoped that there will be no issues creating a pool. WAC isn't helpful. One message claims everything's alright. but an error in the main screen This is the manual command, since WAC delivers contradictionary results: Enable-ClusterStorageSpacesDirect -Autoconfig 1 -SkipEligibilityChecks -CollectPerformanceHistory 1 -Confirm -Verbose -BusTypesToUse SAS But it its stuck at that point. It used to be possible: https://learn.microsoft.com/en-us/windows-server/storage/storage-spaces/storage-spaces-direct-hardware-requirements#virtual-deployment Cleaning up the disks and starting over won't help, so they can be pooled once again. Unfortunately a link from Elden seem to be dead end. https://techcommunity.microsoft.com/t5/windows-server-for-it-pro/enabling-s2d-cluster-in-virtual-test-environment-issue/m-p/84186/highlight/true#M267 Any ideas? (again this is a not a prod. env.) Thanks for your time! ✌️ cc JamesvandenBerg cblackuk1 Darryl van der Peijl John Marlin Thomas-Maurer
