<font class="Apple-style-span" face="'trebuchet ms', sans-serif">Thank you Jared.</font><div><font class="Apple-style-span" face="'trebuchet ms', sans-serif"><br></font></div><div><font class="Apple-style-span" face="'trebuchet ms', sans-serif">I will test it out in my office lab and if it goes as suggested, I will implement in the client's network.</font></div>
<div><font class="Apple-style-span" face="'trebuchet ms', sans-serif"><br></font></div><div><font class="Apple-style-span" face="'trebuchet ms', sans-serif">Thanks again for your time and suggestion.</font></div>
<div><font class="Apple-style-span" face="'trebuchet ms', sans-serif"><br></font></div><div><font class="Apple-style-span" face="'trebuchet ms', sans-serif">-Sujith<br></font><br><div class="gmail_quote">On Mon, Jun 14, 2010 at 3:36 AM, Jared Valentine <span dir="ltr"><<a href="mailto:hidden@xmission.com">hidden@xmission.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div lang="EN-US" link="blue" vlink="purple">
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Sounds like you need to map a static arp entry to multiple Ethernet
ports? I believe it’s possible with the SX800, but you’ll
have to use a hairpin in order to get the functionality to work. These
instructions assume the following:</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">SX800 is routing</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Servers use the SX800 as their default gateway</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Servers are in VLAN 100</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">SX800 VLAN100 VE address is 10.0.0.1</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Here’s something to try:</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span></p>
<p><span style="font-size:11.0pt;color:#1F497D"><span>1.)<span style="font:7.0pt "Times New Roman"">
</span></span></span><span style="font-size:11.0pt;color:#1F497D">Remove VE100 from VLAN100.</span></p>
<p><span style="font-size:11.0pt;color:#1F497D"><span>2.)<span style="font:7.0pt "Times New Roman"">
</span></span></span><span style="font-size:11.0pt;color:#1F497D">Add another port to VLAN100 untagged (example 2/1)</span></p>
<p><span style="font-size:11.0pt;color:#1F497D"><span>3.)<span style="font:7.0pt "Times New Roman"">
</span></span></span><span style="font-size:11.0pt;color:#1F497D">Create new VLAN (101) </span></p>
<p><span style="font-size:11.0pt;color:#1F497D"><span>4.)<span style="font:7.0pt "Times New Roman"">
</span></span></span><span style="font-size:11.0pt;color:#1F497D">Add single port, untagged, into VLAN101 (example eth 2/2)</span></p>
<p><span style="font-size:11.0pt;color:#1F497D"><span>5.)<span style="font:7.0pt "Times New Roman"">
</span></span></span><span style="font-size:11.0pt;color:#1F497D">Create VE101 in VLAN101</span></p>
<p><span style="font-size:11.0pt;color:#1F497D"><span>6.)<span style="font:7.0pt "Times New Roman"">
</span></span></span><span style="font-size:11.0pt;color:#1F497D">Assign VE101 with 10.0.0.1 </span></p>
<p><span style="font-size:11.0pt;color:#1F497D"><span>7.)<span style="font:7.0pt "Times New Roman"">
</span></span></span><span style="font-size:11.0pt;color:#1F497D">“Loop” 2/1 to 2/2</span></p>
<p><span style="font-size:11.0pt;color:#1F497D"><span>8.)<span style="font:7.0pt "Times New Roman"">
</span></span></span><span style="font-size:11.0pt;color:#1F497D">Create the static-arp entry on port 2/2</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">You can tweak these instructions for other scenarios (SX800 not
routing, just switching), but the concept remains the same. If the SX800
isn’t routing, then you’ll create VLAN101, move the physical uplink
from VLAN100 to VLAN101, loop VLANs 100/101, add your static-arp entry to the
loop port in VLAN101. </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Good luck,</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">-Jared</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt">From:</span></b><span style="font-size:10.0pt">
<a href="mailto:foundry-nsp-bounces@puck.nether.net" target="_blank">foundry-nsp-bounces@puck.nether.net</a>
[mailto:<a href="mailto:foundry-nsp-bounces@puck.nether.net" target="_blank">foundry-nsp-bounces@puck.nether.net</a>] <b>On Behalf Of </b>Sujith<br>
<b>Sent:</b> Wednesday, June 02, 2010 7:27 PM<br>
<b>To:</b> foundry-nsp<br>
<b>Subject:</b> [f-nsp] Interoperability issue between Windows NLB cluster with
Foundry SX800</span></p>
</div><div><div></div><div class="h5">
<p class="MsoNormal"> </p>
<p class="MsoNormal"><span>Hello,</span></p>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal"><span>Thank you for
your valuable suggestions and time.</span></p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal"><span>The client is
having a Windows NLB cluster configured for an application and is terminated to
the Foundry switch. The Windows cluster is receiving request constantly
on one server and not on other server.</span></p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal"><span>We tried
configuring static MAC address on both the Ethernet ports as suggested by
Foundry guide for Windows NLB setup and followed some guidelines from Cisco
guide also. Both the guidance were failing to deliver the request on both
the servers. </span></p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal"><span>The client is
running a Hyper-V on two separate physical servers and each Hyper-V is holding
3 Nos. of virtual machines. The Windows NLB cluster is configured only
for 1 Virtual machine in each physical server.</span></p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal"><span>The servers
are terminated in the Foundry SX800. The windows NLB cluster's are
configured to work in Unicast mode and also tested with Multicast mode also.
On both the testing, we are not getting the results on both the servers.
The Windows NLB cluster is working perfectly with Cisco switch without
any issue.</span></p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal"><span>The client
tested the Windows NLB cluster configured separately on the physical servers
(test bench) which is connected to the Foundry switch and we get the results as
expected. But when tested with Windows NLB cluster configured on a
Virtual machine, it fails.</span></p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal"><span>Do someone
have come across this issue and is there any workaround to resolve the same?</span></p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal"><span>Thanks</span></p>
</div>
<div>
<p class="MsoNormal"><span>-Sujith</span></p>
</div>
</div></div></div>
</div>
</blockquote></div><br></div>