Content deleted Content added
Rescuing 1 sources and tagging 0 as dead.) #IABot (v2.0.9.3) (Whoop whoop pull up - 13005 |
→Multicast mode: link |
||
Line 21:
=== Multicast mode ===
Another option is to make NLB in [[Multicast routing protocol|multicast]] mode. The unicast [[IPv4]] address of the cluster is linked to a [[multicast]] MAC address. The hosts is in the cluster will never send traffic to the [[Network switch|switch]] using this MAC address with the cluster IPv4 address so one would need to create a static [[Address Resolution Protocol|ARP]] entry on the router (layer 3) in the attached network. Not all vendors will allow you to create an ARP entry where you use a unicast IP address and a multicast MAC address. Cisco publishes some examples how to set up MS NLB on Catalyst switches running [[IOS]]<ref>Cisco: [http://www.cisco.com/en/US/products/hw/switches/ps708/products_configuration_example09186a0080a07203.shtml Catalyst configuration examples] {{webarchive|url=https://web.archive.org/web/20140131115541/http://www.cisco.com/en/US/products/hw/switches/ps708/products_configuration_example09186a0080a07203.shtml |date=2014-01-31 }}, visited 8 June 2013</ref> and these same examples can be used for switches from many other vendors. As with NLB in unicast mode: incoming traffic towards the cluster will be flooded to all ports in the switch/VLAN and not all vendors support this setup. To limit the flooding, MS NLB now supports IGMP which should lead to the switches learning which ports are actually using the [[multicast address]],<ref>Microsoft Support knowledge base: [http://support.microsoft.com/kb/283028 KB283028: IGMP Snooping support on NLB], visited 8 June 2013</ref> but it doesn't always lead to the desired result. For example, [[Dell PowerConnect]] [[multi-layer
== Server load balancing ==
|