Comments for jtpedersen.com IT made simple https://jtpedersen.com/ Just another WordPress site Fri, 29 Nov 2024 00:09:17 +0000 hourly 1 Comment on Cluster Node failed to join the cluster by Suki Singh https://jtpedersen.com/2021/12/cluster-node-failed-to-join-the-cluster/#comment-86689 Fri, 29 Nov 2024 00:09:17 +0000 https://jtpedersen.com/?p=2942#comment-86689 This process worked for me with Windows 2019, 2022 without any issues.
Thanks Alot….

]]>
Comment on RoCE/RDMA/DCB what is it and how to configure it by Zach Heise https://jtpedersen.com/2017/06/rocerdmadcb-what-is-it-and-how-to-configure-it/#comment-86258 Thu, 14 Nov 2024 22:31:55 +0000 http://jtpedersennew.azurewebsites.net/?p=362#comment-86258 Hi JT, I apologize if you receive this comment/moderated twice. I posted it previously with a URL to another blog, and I think wordpress moderation removed it because of it. I’m trying a repost without the URL this time.

In your first big script block after installing DCB, I notice you are not setting the NetQOSPolicy using the windows Template of “cluster” – you have written “New-NetQosPolicy “Cluster” -PriorityValue8021Action 7″

According to this fellow here – and I confirmed myself – link removed for wordpress approval reasons but he’s darrylvanderpeijl – you might consider wanting to use the flag -Cluster when you are making that New-NetQOSPolicy.

Here’s the difference in results if you run Get-NetAdapterQOS cmdlet with that -Cluster flag, vs without it. I apologize in advance as the formatting will probably be pretty compacted and not tab/space separated, but hopefully will get the gist across.

Without it:
Name : SLOT 2 Port 1
Enabled : True
Capabilities : Hardware Current
——– ——-
MacSecBypass : NotSupported NotSupported
DcbxSupport : None None
NumTCs(Max/ETS/PFC) : 4/4/4 4/4/4

OperationalTrafficClasses : TC TSA Bandwidth Priorities
— — ——— ———-
0 ETS 49% 0-2,4-6
1 ETS 50% 3
2 ETS 1% 7

OperationalFlowControl : Priorities 3,7 Enabled
OperationalClassifications : Protocol Port/Type Priority
——– ——— ——–
Default 7
NetDirect 445 3

With it:

Name : SLOT 2 Port 1
Enabled : True
Capabilities : Hardware Current
——– ——-
MacSecBypass : NotSupported NotSupported
DcbxSupport : None None
NumTCs(Max/ETS/PFC) : 4/4/4 4/4/4

OperationalTrafficClasses : TC TSA Bandwidth Priorities
— — ——— ———-
0 ETS 49% 0-2,4-6
1 ETS 50% 3
2 ETS 1% 7

OperationalFlowControl : Priorities 3,7 Enabled
OperationalClassifications : Protocol Port/Type Priority
——– ——— ——–
Default 0
TCP/UDP 3343 7
NetDirect 445 3

Notice that when -Cluster flag is used, how we have an operation classification of “TCP/UDP 3343 7” – I apologize if I am making a mistake, I’m really new at this and trying to read all the docs on RDMA and the PFC that is recommended to go with it. Would love to hear if you agree with the other website’s usage of -Cluster flag, and if you disagree, your take on it! Cheers and thanks for writing this up!

]]>
Comment on Configure Cross Domain Failover Cluster Replication with a selfsigned Wildcard Certificate by andy https://jtpedersen.com/2019/04/configure-cross-domain-failover-cluster-replication-with-a-selfsigned-wildcard-certificate/#comment-86079 Tue, 12 Nov 2024 11:39:38 +0000 http://jtpedersen.com/?p=2433#comment-86079 Doesn’t work with self-signed certificates in Failover Cluster.
Added all reg keys disabling revocation check.
Worked in Hyper-V Replication without cluster, but when building and enabling cluster ReplicaBroker says that self-signed certificates can`t be used.
Windows Server 2025.

]]>
Comment on Issue installing Hyper-V and Failover Cluster features by Paul https://jtpedersen.com/2020/10/issue-installing-hyper-v-and-failover-cluster-features/#comment-72224 Mon, 12 Feb 2024 10:41:59 +0000 https://jtpedersen.com/?p=2860#comment-72224 Interesting. The same is happening again with the latest Windows 2019 image, but it’s not so easy to fix when you’re using Terraform! I guess I’ll be raising it with Microsoft Azure support 🙁

]]>
Comment on How to configure System Center VMM Part 2 – Host Groups by jantorep https://jtpedersen.com/2019/05/how-to-configure-system-center-vmm-part-2-host-groups/#comment-69840 Fri, 25 Aug 2023 07:41:21 +0000 http://jtpedersen.com/?p=2454#comment-69840 In reply to Brian.

Yes correct

]]>
Comment on How to configure System Center VMM Part 2 – Host Groups by Brian https://jtpedersen.com/2019/05/how-to-configure-system-center-vmm-part-2-host-groups/#comment-69205 Thu, 27 Jul 2023 08:00:52 +0000 http://jtpedersen.com/?p=2454#comment-69205 This is a great blog and has helped me to understand VMM in greater detail.

I am new to SCVMM and I need to add a host group to a logical network site, is this as simple as just editing the logical network and ticking the host group?

I am unsure if doing this affects the clouds in anyway

]]>
Comment on Azure Stack HCI PhysicalDisks won’t go out of storage maintenance mode by Sveinbjorn https://jtpedersen.com/2021/09/azure-stack-hci-physicaldisks-wont-go-out-of-storage-maintenance-mode/#comment-67406 Fri, 03 Mar 2023 13:31:11 +0000 https://jtpedersen.com/?p=2930#comment-67406 In reply to jantorep.

Thank you Jan
One more question, after the reboot of the cluster were you able to continue patching, without this issue resurfacing ?

]]>
Comment on Azure Stack HCI PhysicalDisks won’t go out of storage maintenance mode by jantorep https://jtpedersen.com/2021/09/azure-stack-hci-physicaldisks-wont-go-out-of-storage-maintenance-mode/#comment-67402 Thu, 02 Mar 2023 16:14:39 +0000 https://jtpedersen.com/?p=2930#comment-67402 In reply to Sveinbjorn.

No this was on Azure Stack HCI 21H2 but the same things will apply to 2022 as well.

]]>
Comment on Azure Stack HCI PhysicalDisks won’t go out of storage maintenance mode by Sveinbjorn https://jtpedersen.com/2021/09/azure-stack-hci-physicaldisks-wont-go-out-of-storage-maintenance-mode/#comment-67401 Thu, 02 Mar 2023 14:20:08 +0000 https://jtpedersen.com/?p=2930#comment-67401 Hi Jan

I have a similar issue after installing februar update to my 4 node 2022 s2c cluster.
The first node I updated is stuck on stopping maintenance mode, so I stopped updating 🙂

just to confirm was this a cluster of 2022 windows servers ? I am not very excited to reboot the whole thing with over 50 production vm’s on it.

]]>
Comment on Azure Stack HCI PhysicalDisks won’t go out of storage maintenance mode by Roman Schnabl https://jtpedersen.com/2021/09/azure-stack-hci-physicaldisks-wont-go-out-of-storage-maintenance-mode/#comment-66880 Tue, 17 Jan 2023 09:10:58 +0000 https://jtpedersen.com/?p=2930#comment-66880 Hello,

I had a similar issue when using Enable-StorageMaintenanceMode on a Node of a 2-Node-Cluster in preparation of an OS upgrade : the Node’s disks were stuck in “{Starting Maintenance Mode…..}”

I found your post and thought “Before shutting down all those VMs, lets try a refresh on the active Node, this should suffice if cached information is the problem”, and I simply did a Refresh on Storage -> Disks in Failover Manager on the active Node….

And it worked – so thanks for putting me on the right track…

]]>
Comment on Changing already used logical networks in Virtual Machine Manager by jantorep https://jtpedersen.com/2020/10/changing-already-used-logical-networks-in-virtual-machine-manager/#comment-63192 Fri, 12 Aug 2022 08:45:01 +0000 https://jtpedersen.com/?p=2876#comment-63192 In reply to Ahmed.

Yes you can. But if it’s in use i don’t think you can. Id rather create a new logical network for it.

]]>
Comment on VMM 2022 Agent Upgrade Problem and Adding New physical hosts by jantorep https://jtpedersen.com/2022/05/vmm-2022-agent-upgrade-problem-and-adding-new-physical-hosts/#comment-63191 Fri, 12 Aug 2022 08:42:05 +0000 https://jtpedersen.com/?p=2971#comment-63191 In reply to Sascha.

You tried to manually install the agent on the host, then add the host to VMM? That one works for me and everyone else i have spoken with.

Im doing a new VMM 2022 upgrade in a months time. Il update once i have some feedback on that one.

]]>
Comment on VMM 2022 Agent Upgrade Problem and Adding New physical hosts by jantorep https://jtpedersen.com/2022/05/vmm-2022-agent-upgrade-problem-and-adding-new-physical-hosts/#comment-63190 Fri, 12 Aug 2022 08:40:20 +0000 https://jtpedersen.com/?p=2971#comment-63190 In reply to Sascha.

No this was internal MVP Talks. And it’s related to the deployment of the agent to AzHCI.

I have not recived a OK for it yet. Il try and ping the VMM team about it.

]]>
Comment on VMM 2022 Agent Upgrade Problem and Adding New physical hosts by jantorep https://jtpedersen.com/2022/05/vmm-2022-agent-upgrade-problem-and-adding-new-physical-hosts/#comment-63189 Fri, 12 Aug 2022 08:35:26 +0000 https://jtpedersen.com/?p=2971#comment-63189 In reply to Udo Geske.

No we think we found the issue as i was running a pre release of 2019 UR3 and that was the cause of it.

]]>
Comment on VMM 2022 Agent Upgrade Problem and Adding New physical hosts by Randy https://jtpedersen.com/2022/05/vmm-2022-agent-upgrade-problem-and-adding-new-physical-hosts/#comment-63112 Mon, 08 Aug 2022 15:52:26 +0000 https://jtpedersen.com/?p=2971#comment-63112 I had a similar issue, same error and message. Mine was for upgrading existing agents on a registered cluster from SCVMM2019 to SCVMM2022. I was using an existing RunAs profile that seemingly had full admin rights to the cluster since SCVMM is already managing them. But, was still failing.

I ran a Process Monitor against the system while the job was running and then filtered out all the unrelated noise. Finally, I saw a couple lines of interest (one pair of messages):

Process Name = VMMService.exe
Class: FileSystem
Operation = CreateFile
Result: PATH NOT FOUND
Path: C:\Program Files\Microsoft System Center\Virtual Machine Manager\agents\I386\10.22.1287.0\msiInstaller.exe

Process Name = VMMService.exe
Class: FileSystem
Operation = CreateFile
Result: NAME NOT FOUND
Path: \\server-name.domain.tld\ADMIN$\msiInstaller.exe

I verified that the PID was running under the SCVMM RunAs account I was using to send the update agents. It’s interesting it’s trying to locate an i386 version of the installer files and in fact there is no such installer source path on my SCVMM server. I also saw a couple lines complaining about inability to properly talk to the HV server I was pushing the updates to.

I switched over to directly entering creds of another administrative user that is a full domain admin and pushed the update again. This time it worked and the process looked a little different:

Process Name = VMMService.exe
Class: FileSystem
Operation = CreateFile
Result: Success
Path: C:\Program Files\Microsoft System Center\Virtual Machine Manager\agents\amd64\10.22.1287.0\msiInstaller.exe

Process Name = VMMService.exe
Class: FileSystem
Operation = CreateFile
Result: Success
Path: \\server-name.domain.tld\ADMIN$\msiInstaller.exe

This time it seems to know it needs to send the 64bit version of the binary and then successfully does so.

Maybe check this on your side to see if it’s the same issue.

]]>
Comment on VMM 2022 Agent Upgrade Problem and Adding New physical hosts by amir https://jtpedersen.com/2022/05/vmm-2022-agent-upgrade-problem-and-adding-new-physical-hosts/#comment-62745 Thu, 21 Jul 2022 19:26:08 +0000 https://jtpedersen.com/?p=2971#comment-62745 before installing the agent manually , check whether the time is synced between scvmm and host also active directory ? after that restart the task if it failed install agent manually

]]>
Comment on VMM 2022 Agent Upgrade Problem and Adding New physical hosts by Udo Geske https://jtpedersen.com/2022/05/vmm-2022-agent-upgrade-problem-and-adding-new-physical-hosts/#comment-62364 Thu, 30 Jun 2022 05:57:25 +0000 https://jtpedersen.com/?p=2971#comment-62364 Hello, is there already an official solution from Microsoft for the problem “Install Agent”? I have nothing on the net.
Greetings

]]>
Comment on Changing already used logical networks in Virtual Machine Manager by Ahmed https://jtpedersen.com/2020/10/changing-already-used-logical-networks-in-virtual-machine-manager/#comment-61509 Tue, 24 May 2022 14:15:15 +0000 https://jtpedersen.com/?p=2876#comment-61509 Thanks for the great article, can I change the subnet itself and start, end IP address range

]]>
Comment on Cluster Node failed to join the cluster by Eric Nord https://jtpedersen.com/2021/12/cluster-node-failed-to-join-the-cluster/#comment-61480 Tue, 24 May 2022 01:34:38 +0000 https://jtpedersen.com/?p=2942#comment-61480 Thank you @jantorep this is exactly what I needed.

]]>
Comment on VMM 2022 Agent Upgrade Problem and Adding New physical hosts by Sascha https://jtpedersen.com/2022/05/vmm-2022-agent-upgrade-problem-and-adding-new-physical-hosts/#comment-61176 Thu, 12 May 2022 19:39:57 +0000 https://jtpedersen.com/?p=2971#comment-61176 also you wrote:
“Multiple MVP’s have reported this”

How do you know this?

Is there some VMM Community im not aware of that i could participate in? Its a lonely problem solving with SCVMM sometimes…

]]>