mattmcspirit
commented
3 years ago Hi Liam,
Based on the nested config you've deployed in the guide, I actually think that any VMs running on your nested AzSHCI nodes, attached to the AzSHCI nodes "External" network vSwitch (which in turn is bound to the InternalNAT switch) should be able to reach anything on your sandbox 192.168.0.0/24 network, including the AzSHCI nodes themselves (on the mgmt network) and the DC/WAC VMs. There's no reason why that shouldn't work from a network communication perspective.
The challenge however, is that you're then at multiple layers of nesting, so performance may be pretty bad at that point, but should still work, assuming you can throw enough horsepower at the nested VM running on the AzSHCI cluster.
This is primarily the reason i just walked people through deploying an "empty" VM rather than one with an OS, but networking should work fine.
Let me know! :)
liamfoneill
Not sure if what I want to do is even possible but let's say you have successfully completed the guide (following all of the instructions) and deployed the cluster with Hyper-V nested virtualisation. You will end up with 4 VMs,
They are connected to the NAT switch. You deploy your first VM on the Stack HCI cluster and you want to join it to the Domain (let's assume it is a secondary domain controller you are trying to deploy). As the only domain controller existing outside of the Stack Cluster I don't think it will be able to see the existing Domain controller.
This might be impossible or it might a simple nested virtualisation/networking question but my mind is drawing a blank. The VMs are connected to an 'external' compute switch on the Stack HCI nodes but I don't think they will be able to see the Domain controller on the Nat switch on my top level hypervisor host
How do I extend the existing domain into the cluster network where the VMs will be located?