PREP SERVER 2012 R2 FOR MAC CLIENTS MAC
The GUI on WNLB shows you the MAC address of the VIP. A mere ipconfig reveals only the unicast MAC address of the NIC. What MAC address do I feed my switch configurations?Īh! You are a smart cookie, aren’t you. Great little switch, many of them are still serving us well after 6 years on the job. For this demo I have a DELL PowerConnect 5424 at my disposal. Why IGMP multicast? Unicast isn’t the best option and multicast might not cut it or be the best option for your environment and IGMP is less talked about yet it’s a nice solution with Windows NLB, bar replacing into with a hardware load balancer. Even wild messy ramblings by myself here. Lots on this weak host/strong host model behavior on the internet. You might have to do some configuration work to get the network flow to do what it needs to do. I’m not going in to the fact that since W2K8 the network default configurations are all about security. While chancing this there will be some advice warnings thrown at you
Set up WNLB with IGMP multicast as option.Note that there is no need to use a static MAC address or copy your VIP mac into the settings of your VM with Windows Server 2012 (R2) Hyper-V.Make sure you enable MAC Spoofing on the appropriate vNIC or vNICs in the advanced settings.Here we’ll use a single switch to mimic a stacked one (the model available to me is non stackable and I have only one anyway). If you have a 2 node Hyper-V cluster, are using NIC Teaming for the switch and depending on how teaming is set up you’ll might run into these issues. Let’s look at the situation we’ll use to show case one possible solution to the issues. We were dealing with some issues on on several WNLB clusters running on a Windows Server 2012 R2 Hyper-V cluster after a migration from an older cluster. To know and see the issues we are dealing with in this demo, you need to read this blog post first: Windows NLB Nodes “Misconfigured” after Simultaneous Live Migration on Windows Server 2012 (R2).
0 kommentar(er)
