In my experience, if you don't do anything, then the NLB traffic addressed to the virtual IP's MAC, will be flooded to all ports in the VLAN. If you run MRTG, you'd see the graph for every port in the VLAN look about the same. Every server in the cluster sees a copy of every request, and only one server does something with it. If all you need is redundancy, this can work.
I believe that you can enable IGMP Snooping on the 5324, so that the packets are not flooded to all ports in the VLAN. I have not tried this, but I imagine that all servers in the NLB cluster would still get a copy. So if the NLB servers are in a VLAN all by themselves, then IGMP Snooping may have no effect: you still may get all requests forwarded to all ports in the vlan.
IGMP snooping would be helpful if the NLB servers share a VLAN with non-NLB servers.
speedcolo
1 Rookie
•
43 Posts
0
October 18th, 2009 16:00
In my experience, if you don't do anything, then the NLB traffic addressed to the virtual IP's MAC, will be flooded to all ports in the VLAN. If you run MRTG, you'd see the graph for every port in the VLAN look about the same. Every server in the cluster sees a copy of every request, and only one server does something with it. If all you need is redundancy, this can work.
I believe that you can enable IGMP Snooping on the 5324, so that the packets are not flooded to all ports in the VLAN. I have not tried this, but I imagine that all servers in the NLB cluster would still get a copy. So if the NLB servers are in a VLAN all by themselves, then IGMP Snooping may have no effect: you still may get all requests forwarded to all ports in the vlan.
IGMP snooping would be helpful if the NLB servers share a VLAN with non-NLB servers.