


Make sure you do not use the same range on different Hyper-V hosts!! So, if you not take care it is possible to accidentally deploy hosts with duplicate MAC address pools. Hyper-V has an algorithm to deal with duplicate MAC addresses on a single host, but not across multiple hosts. You could set your own MAC here, using the static MAC option.īut what happens when you have more than 1 host?

You can view the MAC of a VM under “Settings > Network Adapter > Advanced Features”Īs you can see the allocated MAC is within the specified MAC range. So every new VM gets a MAC address in this range specified on the Hyper-V host. You can see/edit the range under the “Virtual Switch Manager”. In the Hyper-V Manager you can set a specific range what addresses are allocated to the VM’s. There are many threads on technet forums about virtual machines changing MAC addresses and especially Linux virtual machines losing network connection. It seems easy to setup and never look at it again but this can cause some serious issues. Internet Group Management Protocol (IGMP) multicast mode-The switch sends packets only out of the ports that connect to the cluster members rather than all ports.In this post I’m going to talk about the MAC Address Pools in Hyper-V / VMM and the actual way they work. Multicast mode-NLB uses a multicast MAC address that is a virtual MAC address for network communication (for example 0300-5e11-1111). In addition, because the cluster MAC address is unknown to the switch, packets destined to it are forwarded on all ports of the switch. The switch cannot add the cluster MAC address to its MAC table. Unicast mode-NLB assigns each cluster member a common MAC address, which is the cluster MAC address, and changes the source MAC address of each sent packet. Microsoft NLB provides the following packet sending modes to make the switch forward network traffic to all servers or specified servers: For more information about NLB, see the related documents for Windows Server. In a medium or small data center that uses the Windows Server operating system, the proper cooperation of the switch and NLB is very important. To implement fast failover, NLB requires that the switch forwards network traffic to all servers or specified servers in the cluster, and each server filters out unexpected traffic. NLB supports load sharing and redundancy among servers within a cluster. Microsoft NLB is a load balancing technology for server clustering developed on Windows Server.
