Hyper-v
Azure Stack HCI – Installation Series – 13 (Pre-) Cluster
Azure Stack HCI – Installation Series – 13 (Pre-) Cluster Validation
#Azure #Stack #HCI #Installation #Series #Pre #Cluster
“The Hybrid Friends”
This Episode:
Before creating the cluster we run a validation to find any issues before building the cluster. We run the test with PowerShell and analyse it remotely using a browser. The network issue we see will be fixed and a second test proves that. Cluster tests can and should be done…
source
To see the full content, share this page by clicking one of the buttons below |
it would be interesting to see if the error in the validation matches with the issue I have mentioned in a prev. video that the VMNetadapter with ManagementOS enabled, does not work with RDMA on a SET Switch, despite everything is correctly configured. I believe if Carsten did a get-NetAdapterRDMA the vEthernet (Compute) would be in the state RDMA enabled, operation false.
in some cases, still in 2023, with SAN storage, the cluster validation caused to unexpectedly crash all running VMs even though everything was correctly configured. Interesting Carsten mentioned it is fixed now.
protip: to avoid issues, also with WAC and Scripts and Microsoft / OEM Support, do deploy all your OSes in en-us. If you really need a localization, mind that feature names not only for Test-Cluster but also Install-WindowsFeature will be renamed, also in Server Manager. The dreadful thing is that if you search for Features across different servers with Server Manager, you have a mix of different languages.
tldr: Language does not affect PowerShell. install all your OS with en-us to avoid a number of issues. Apply language pack if really needed.
If you applied language pack, when doing an in-place upgrade you need to use dynamic updates to upgrade these, too.