<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Nlb on sigtar.com</title>
		<link>https://sigtar.com/tags/nlb/</link>
		<description>Recent content in Nlb on sigtar.com</description>
		<generator>Hugo</generator>
		<language>en-nz</language>
		
		
		
		
			<lastBuildDate>Fri, 10 Dec 2010 00:00:00 +1300</lastBuildDate>
		
			<atom:link href="https://sigtar.com/tags/nlb/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>vmware and NLB  (unicast vs multicast)</title>
				<link>https://sigtar.com/2010/12/10/vmware-and-nlb-unicast-vs-multicast/</link>
				<pubDate>Fri, 10 Dec 2010 00:00:00 +1300</pubDate>
				<guid>https://sigtar.com/2010/12/10/vmware-and-nlb-unicast-vs-multicast/</guid>
				<description>&lt;p&gt;Thought I’d get a bit of clarification around this one. VMWare states –&lt;/p&gt;&#xA;&lt;p&gt;&lt;em&gt;VMware recommends that you use multicast mode, because unicast mode forces the physical switches on the LAN to broadcast all Network Load Balancing traffic to every machine on the LAN.&lt;/em&gt;&lt;/p&gt;&#xA;&lt;p&gt;There are some issues which come to the surface if you are using unicast. Where possible we should always try to use a Multicast NLB as Unicast can cause some complications around vSwitch configurations. (requirement to change switch notifications to “No” – and seemingly break port id teaming). Detail below;&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
