You can also turn off NLB multicast support and use a unicast network address without a hub. You should be able to add a static ARP entry to the router to circumvent the issue. If these tests work properly, the router is probably at fault. Solution: Verify that you can use ping to access the cluster from a client on the cluster's subnet and to access the cluster hosts' dedicated IP addresses from a computer outside the router.Cause: If you are using multicast support, you might find that your router has difficulty resolving the primary IP address into a multicast media access control (MAC) address by using the Address Resolution Protocol (ARP).If you are using a single network adapter for the dedicated and cluster IP addresses, consider the following causes: If this test fails, and you are using multiple network adapters, the issue is not related to NLB. I just want to make sure that I understand it all right so that I know that the changes I need to make are correct and do not break something else.īTW.Verify that you can use ping to access the dedicated IP addresses for the cluster hosts from a computer outside the router. The docs I am reading on CCO are helping it make sense but all seem to reference single standalone servers and not VMs. Network Load Balancing is new to me and all I had to start with was the programmers comming to me and saying I needed to apply a static ARP command and disable snooping on my switches to make their Sharepoint cluster work.
I gather that I need to bind the "virtual" MAC address to the link used specifically by the sharepoint servers but will there be any issues with this being a single stack or the fact that there are three other servers on that same link? The VMs have multiple connections to the stack with at least four servers on each link. I am sort of in the same boat but I have a single 4500x switch stack with two different Sharepoint servers attached to build the cluster with and both Sharepoint servers are on VMs. (Depending on the platform, the commands could vary.) Mac-address-table static 03-bf-xx-xx-xx-xx vlan interface You don't need to do this for functionaltiy reasons, it's just for preventing from flooding.Īnd no, this will not result in layer-2 loops. To avoid this undesired flooding, you should bind the cluster MAC address only to the ports (including uplinks) which are needed for NLB communication. The reason is that Cisco routers do not accept this combination in ARP requests (see RFC 1812 3.3.2).īy default the cluster MAC address is 03:bf:Ģ) Now with the ARP entry, it would actually work because the group bit of the cluster MAC address is set and the frames will be flooded within the VLAN. Multicast Mode ( without IGMP option) requires 2 configuration tasks:ġ) Static ARP entry(s) to bind the Multicast MAC address to the IP address of the NLB cluster.
0 kommentar(er)
