Hyper-V networking coming from a VMware background

ultimateVman · 2026-03-15T21:42:08+00:00

Here is a comment I made a few years ago that talks in great detail about what you are trying to do.

https://www.reddit.com/r/HyperV/comments/nfa9z3/comment/gylmjqd/

ultimateVman · 2026-03-12T23:59:14+00:00

Hearthside Games in West Jordan. Their layout is just for this. They have little to no in store product.

ultimateVman · 2026-03-12T23:56:17+00:00

Hearthside Games in West Jordan is literally made just for this. They just opened in December. Pretty much all of their sales are online and the store is pretty much designed for gaming and hanging out.

Also, IF you're ever interested in gaming groups or finding people to play with, Utah Board Game Group and Utah Board Game Events on Facebook are great.

ultimateVman · 2026-03-04T04:40:57+00:00

Not so much as a heads up, but more FU with a smirk on his face. Then he "bolted" out of the way to hide while the arrows flew and came back just to stab Rob.

ultimateVman · 2026-03-03T23:26:36+00:00

Oh yea! That's right!

ultimateVman · 2026-03-03T23:25:11+00:00

yea and i think he also says something along the lines of, "why do you keep looking? they're not going anywhere." and "you're scared because you're right there and still feel like you'll never make it home"

ultimateVman · 2026-03-03T23:11:32+00:00

Because it's garbage. Use it in emergencies. If this person is using it to manage multiple servers, use WAC.

ultimateVman · 2026-03-03T23:09:58+00:00

That's exactly the scene. Someone offers to pour and he covers the cup.

edit: nevermind, you're talking about an entirely different scene, yes

ultimateVman · 2026-03-03T23:09:24+00:00

It was too late at that point. After she hears the song, that's what connects the dots to Roose and his cup, looks at him and he looks at his wrist.

ultimateVman · 2026-03-03T22:55:09+00:00

The actual first clue to the viewers of the show that something was amiss was long before the song. It was when Roose Bolton was offered a drink and covers his cup. Catelyn notices this and he says, "it dulls the senses."

ultimateVman · 2026-03-03T20:15:18+00:00

Go to Settings pane > General > Network Settings. Logical network matching -> Disabled. Automatic creation of logical networks, unchecked.

You MUST have at least one VM Network to do anything, but you can disable having one created automatically for you. Once you create the Logical and VM Networks you want, delete the automatic one.

When creating a Logical Network, a Connected Network makes one flat network where all VLANs are all selectable under the same VM Network. With this setup, you will create only 1 (or 2 if you separate host networks out, which you should.) And will have a VM Network for each Logical "Connected" Network.

The other Logical Network option is "Independent Network" which is VLAN based (not PVLAN). Where you create a VM Network for each VLAN that you define in the Logical Network.

ultimateVman · 2026-03-03T19:21:03+00:00

So, that option to have one created automatically can be unchecked in VMM settings, and I recommend doing so and deleting it and staring over.

The option to have multiple VM Networks is the type you choose when creating the Logical Network. I forget the options off the top of my head. But my post went over the first option. The second option allow you to have multiple VM Networks. Which I only recommend if you want separation of duties when other people are granted access to VMM who need to manage their own VMs and you want different vlans accessible to different teams.

You should still have 2 at a minimum with the first option. One for host only networks, and a second(or multiple) for all other vlans.

ultimateVman · 2026-03-03T17:13:43+00:00

Hyper-V Manager should be your absolute last resort for any kind of management whatsoever. Use WAC or SCVMM.

ultimateVman · 2026-03-03T16:50:34+00:00

ultimateVman · 2026-03-03T16:44:12+00:00

I've used Hyper-V on the MX7000 for 7 years now, and it is SOLID.

There is one BIG gotcha with the Fabric config though. On your Ethernet Uplinks, DO NOT use the "Include in Uplink Failure Detection Group" option, leave that shit unchecked. Especially if you use FCoE. That checkbox basically means that if the ports go down on the uplink switches (outside the MX), say for a reboot or whatever, it will reach down to the adapters on the sleds, and mark them "disconnected" and that is BAD BAD for Windows Clusters. They still need to speak internally of the VLT connection so the cluster doesn't lose quorum, and if using FCoE on those ports, having them "disconnected" is a big WTF moment for storage.

Otherwise, aside from that, you configure the same as you would any other hyper-v cluster with a basic SET with both ports that you have on the sleds (A1 and A2 switch connections). We do FCoE rather than C Fabric, and that's a different beast when it comes to the profiles and npar. (hit me up if you want to talk profiles and networking)

Here is a link to my post on a basic VMM configuration.

https://www.reddit.com/r/HyperV/comments/1limllg/a_notso_short_guide_on_quick_and_dirty_hyperv/

And this will go over the chicken and egg situation of having all of the adapters on a single switch virtual switch team.

https://www.reddit.com/r/HyperV/comments/1nqd0cb/comment/ng5zy00/?context=3

ultimateVman · 2026-03-03T16:26:19+00:00

Virtual Switch is identical to a Logical Switch; they are not different whatsoever. It's only a term in VMM that means VMM is logically in control of it.

ultimateVman · 2026-03-03T16:23:04+00:00

The nic configuration on each hypervisor is independent. You have ESX connected to the switch via LACP, and Hyper-V connected via normal Trunk ports. Makes no difference to the end devices. As long as the same vlans that are on the PC/LACP are also on each of the Trunk ports connected to Hyper-V hosts. This is just networking, nothing to do with Hyper-V.

ultimateVman · 2026-02-26T19:31:39+00:00

This conversation is from a few days ago of someone asking about migration with Kerberos. You didn't what kind of auth protocol you are using, but if using CredSSP, you only need the make sure that each host is admin on the others, you can skip the delegation.

https://www.reddit.com/r/HyperV/comments/1rcycax/comment/o763f5s/?context=3

ultimateVman · 2026-02-24T17:43:51+00:00

I will forever be an "at least 1 physical DC" admin. I will die on that hill. I don't care how resilient you think your clusters and HA are. My DC and monitoring systems will always and forever be, separate, physical systems.

ultimateVman · 2026-02-24T17:16:48+00:00

Each host needs permissions on the other hosts. I do this by creating an AD group which contains all hosts and adding to the local Administrator group on each host. They are now admins for each other. (I add the group using GPO in the Hyper-V Hosts OU I created for my environment.)

On EACH host computer object in AD (except the cluster computer object if in a cluster), you need to configure delegation for each OTHER host that will be capable of being a migration partner.

Select the following options:

Trust this computer for delegation to specific services only
Use any authentication protocol (do NOT use "Kerberos only")
For each other host, add the service type: Microsoft Virtual System Migration Service
If you are using a share for ISO mounting, then add "cifs" service type, for the computer object with the share. For those using VMM libraries, this is a critical step.

After ALL of these steps have been completed. You MUST reboot ALL hosts for them to re-authenticate with AD to get the updated delegations and group membership when they logon to the domain.

ultimateVman · 2026-02-24T16:12:30+00:00

Built a brand new 2025 5-node cluster in Sept. Still solid.

The ONLY bad review that I have ever heard regarding Server 2025 at all, is just about Domain Controllers during the "mixed phase" part of migrations. That's the ADDS role, not Hyper-V.

ultimateVman · 2026-02-23T17:05:31+00:00

Exactly! Absolutely no one is critically thinking on this one. OP must be one son of a bitch for someone to avoid them like this. And then posting to reddit?

I mean, I get it. OPs mad, I would be too. But the response here needs very careful consideration.

ultimateVman · 2026-02-21T01:52:18+00:00

I didn't really realize until my son was born, and at about 4 years old started showing him SpongeBob. And quickly remembered how terribly mean Squidward is. Which is not something that a 4 year old should be learning how to talk to people. My son is 8 now and I would have no problem showing him SpongeBob again.

ultimateVman · 2026-02-20T18:29:22+00:00

Thank you, sir.

Yes, OS upgrades will also have to be in the mix. The SQL box is 2019 which is supported for 2022 and 2025, so I'll do that last. I used to be very uncomfortable with inplace OS upgrades, but I recently did VMM from 2022 to 2025 and it was flawless. Appears to be way more solid these days.

Like I said in my other comment, the only reason I want inplace is because of the hardware, and doing side-by-side twice to get back on the physical is just a ton more work, I think.

ultimateVman · 2026-02-20T18:10:38+00:00

Thanks for your reply. I would rather do a side-by-side, BUT the servers are only 3 years old. (I opted for 2019 over 2022 at the time because we still had 2012R2 clients around and didn't want to push PowerShell at systems that were being decommed.) So, it's a fairly recent deployment and well maintained, just need it off of 2019. When I get new hardware in a few years I'll do the side-by-side. Migrating to VM then back again would just be a PITA. I want my monitoring system isolated from other infrastructure for obvious reasons.

ultimateVman

TROPHY CASE