Newer Windows versions can be enabled for IGMP, but this may not work for all switches as some models (notably Catalyst 3750 and similar) forward multicast at L2 based on destination IP (which we can't determine from the NLB IGMP reports) rather than MAC. This is because by default NLB servers do not generate IGMP reports which are the primary mechanism switches use to constrain multicast traffic. Static CAM entries are recommended (but not mandatory) on all switches in the subnet(s) containing NLB servers to avoid flooding traffic destined for the cluster on unnecessary ports.This is because Cisco devices will not honour an ARP reply associating a unicast IP with a multicast Ethernet MAC address. Static ARP bindings must be applied on any devices which route traffic from a different subnet into the subnet with NLB servers.Thanks for the useful link and your answers The static arp on the 3LS seems sufficient for the NLB to work, but is there something else to it? Since the multicast mac address does not show in the mac-address table on 3LS, whenever someone searches for this multicast will it be flooded throughout the domain? If the physical servers were on different switches how would the above command be configured and would there be a point to it?Ĥ. I thought that it would get propagated to the 3LS, but it doesn't.ģ. We did that, and show mac-address table on the switch does show the entry as static.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |