<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Arp on vlan51</title><link>https://vlan51.com/tags/arp/</link><description>Recent content in Arp on vlan51</description><generator>Hugo</generator><language>en-gb</language><lastBuildDate>Mon, 01 Jan 2024 00:00:00 +0000</lastBuildDate><atom:link href="https://vlan51.com/tags/arp/index.xml" rel="self" type="application/rss+xml"/><item><title>Static ARP for Microsoft NLB Multicast on HPE Aruba ArubaOS-Switch</title><link>https://vlan51.com/aruba-provision/static-arp-nlb-multicast/</link><pubDate>Mon, 01 Jan 2024 00:00:00 +0000</pubDate><guid>https://vlan51.com/aruba-provision/static-arp-nlb-multicast/</guid><description>&lt;p&gt;Microsoft NLB in multicast mode causes switches to flood traffic to all ports because the multicast MAC address is never seen as a source — the switch cannot learn which port the cluster is on and treats it as an unknown destination.&lt;/p&gt;&#10;&lt;p&gt;HPE Aruba ArubaOS-Switch does not have a direct static MAC/ARP entry feature like Cisco, but &lt;code&gt;ip arp-mcast-replies&lt;/code&gt; combined with IGMP resolves the flooding.&lt;/p&gt;&#10;&lt;h2 id="hpe-aruba-solution"&gt;HPE Aruba solution &lt;a class="anchor" href="#hpe-aruba-solution" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;div class="code"&gt;&#10; &lt;div class="code-bar"&gt;&lt;span&gt;cli&lt;/span&gt;&lt;button class="copy" type="button" aria-label="Copy to clipboard"&gt;Copy&lt;/button&gt;&lt;/div&gt;&lt;pre&gt;&lt;code&gt;ip arp-mcast-replies&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&#10;&lt;p&gt;Enable IGMP on the NLB client VLAN, and ensure NLB is set to &lt;strong&gt;multicast&lt;/strong&gt; cluster operation mode:&lt;/p&gt;</description></item></channel></rss>