SDN on virtual lab

I built my SDN lab to prepare for 70-475 exam, had an issue with management network. But first few words about lab itself:

1 physical host, with standard set of VMs on it: DC, CA, VMM, WSUS, SQL, Hyper-V role and file server. The nested virtualization is enabled on Hyper-V role VM.

My scenario: build network controller (NC) as VM on top of Hyper-V VM. I followed standard procedure, download and install NC template from GitHub, created management network and started to deploy NC role.

Finally I failed with the VMM error 22725: “VMM received name NC1 for VM NC1.domain.name. Expected computer name is NC1.domain.name. Ensure that the VM has joined the right domain or workgroup and then retry the operation.”

I did some troubleshooting and found NC1 VM is not reachable from VMM, IP address has normally assigned from IP pool, it had correct gateway and DNS server settings. I could ping this VM from host, but not from VMM. It’s critical to have direct communication between VMM and VM, because VMM uploads SDN scripts to there and run the PS commands. That explains why VM could not join to domain, because VM couldn’t simply talk with other hosts in the same network. The gateway also was not reachable.

After doing some research I found the solution: ARP spoofing must be enable on the host (in my case it’s virtual machine with nested virtualization). Here is the command:

Get-VMNetworkAdapter -VMName <VMName> | Set-VMNetworkAdapter -MacAddressSpoofing On

Shutdown VM, run this command, start VM. You’re done.

Hope this helps.

You may also like

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.