<p>Hi,</p>
<p>We had exactly the same problem with NLB on SX and FCX. All traffic would go to a single server, and the setup was never stable enough for production.</p>
<p>After a Brocade TAC case which went on for nearly 12 months, we concluded that multi port static ARP is not supported on the FastIron platform. Only multi port static MAC is supported.</p>
<p>You need to run L2 code on FastIron to get NLB, etc to work correctly.</p>
<p>We are hanging dual FCXs stacked and running L2 code. These are connected redundantly to dual SX800 L3 cores. Servers, firewalls, etc are connected to the FCX stack.</p>
<p>Suggest you run 7202d on your SX boxes. Don't run any other 7.x code release at this time.</p>
<p>- Raja<br>
</p>
<div class="gmail_quote">On Oct 19, 2011 2:14 PM, "Robert Toth" <<a href="mailto:rtoth@iperceptions.com">rtoth@iperceptions.com</a>> wrote:<br type="attribution"><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">Hi everyone,<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Was just referred to this list, hopefully somebody can help me with a very stubborn problem here..<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">I have been fighting for a few months now to get my WatchGuard Firecluster's up and running with stability on both a Super-X and SX-800. Here's a quick overview:<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Datacenter: SX-800 with V07.2.00 Full Layer 3 software, redundant mgmt & fabric, and eight 424C modules.<u></u><u></u></p><p class="MsoNormal">This is our core switch that handles all network connectivity to our datacenter servers.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">1 Layer-3 segment (VLAN-9) that is primary gateway for INTERNAL remote network routing across a 2GB dedicated fiber trunk to head office.<u></u><u></u></p><p class="MsoNormal">
Multiple VLAN's used to partition both external and internal network as Layer-2 segments, with firewalls being used to manage and provide controls between them as needed (FastIron does NOT participate in Internal/External access).<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Fireboxes are the Peak 5500e series, with Fireware XTM Pro V11.3.4 - setup for Firecluster H/A support for load-sharing and redundancy. These ports on firebox are given MULTICAST MAC addresses, with UNICAST IP's.<u></u><u></u></p>
<p class="MsoNormal">Firewall ports are ALL plugged into various Layer-2 segments.<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">On the primary trusted network, as well as every other Layer-2 segment (VLAN) the Firebox is the default gateway - however, there is a Layer-3 router on the SX-800 for that one segment that provides an alternate lower-cost route to distant internal networks via RIP so that internal traffic is sent directly across the 2GB trunk line instead of being sent through the firewall at slower speed (and higher load on the firewalls themselves handling inter-office traffic via VPN's). ACL's were in place to limit and control who had access across that link, but those were removed to faciliate debugging for the moment.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Head office: Similar to the above, but using a Super-X instead of the SX-800, and a pair of Firebox Core 1250e's - same release of software on both sets of devices.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">The instructions from Watchguard are clear: We need to setup Static ARP and MAC addresses as needed to correctly direct traffic to/from the switches and fireboxes. The samples given are for a Cisco 3750 and an Extreme Summit 15040 (ref: <a href="http://www.watchguard.com/help/docs/wsm/11/en-us/content/en-us/ha/cluster_example_cisco_wsm.html" target="_blank">http://www.watchguard.com/help/docs/wsm/11/en-us/content/en-us/ha/cluster_example_cisco_wsm.html</a>) . This is what I have tried to replicate to the best I can but have had no luck with setting the static arp address on the switch outside of the single layer-3 segment we have, and to set it on more than one port. Setting the multicast mac is fine for both ports needed to support the pair of firewalls by interface )(ex: static-mac xxx.xxxx.xxxx eth 1/yy eth 2/yy - works fine on every Vlan I need it on).<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Digging further into Google (which ended up pointing me at this list), I found this article about "hairpinning" to correctly support a specific setup of Microsoft NLB clusters (which we also use extensively at the datacenter) here: <a href="https://puck.nether.net/pipermail/foundry-nsp/2010-June/002498.html" target="_blank">https://puck.nether.net/pipermail/foundry-nsp/2010-June/002498.html</a><u></u><u></u></p>
<p class="MsoNormal">While I haven't found need to do this for the NLB clusters themselves as they appear to be working perfectly (up to 5 physical servers per cluster running IIS7 & Win2K8), it appeared to be the best solution to adapt for the Firecluster problem... And getting a static arp assigned to multiple ports.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Anyways, long story short - it's not working well. It seems that the traffic is being forced from port to port by only having the ARP/MAC entry recognized on a single port at a time (and being kicked around constantly). Apparently, if this was a Cisco - this would work brilliantly.. But because we can't map static ARP's as we should, the switch is constantly moving things around instead of sending it out to both ports at the same time for each interface. <u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Has ANYONE seen or tried this kind of setup using similar hardware ? If so, did you get it working correctly? Am I on the right track with the hairpinning solution?<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Is Brocade making any changes to Ironware to provide similar functionality so that I can get this working properly any time soon, or will I have to resort to a couple of dumb Layer-2 switches that apparently won't need any configuration and will just work, and cobble the whole thing together into a massive mess to get it all tied together? Are there any issues with WatchGuard Firecluster that I need to know about that make it work differently than documented, and prevent the FastIron's from being able to cope or perform as expected ( I realize that last question isn't really a Foundry question... My apologies, but I hope that someone else with Fireboxes has seen this problem on Foundry or perhaps found another solution using other hardware if the FastIron's or other Foundry products just couldn't do what was needed. This assumes that FireCluster will work given the right infrastructure setup - maybe THAT assumption is wrong? If so, I'd gladly listen to a solution that DOES work?)<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Best regards,<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal"><b><span style="font-size:12.0pt">Robert Toth<u></u><u></u></span></b></p>
<p class="MsoNormal"><span style="font-size:10.0pt">Director of Information Technology Services<u></u><u></u></span></p><p class="MsoNormal"><b>iPerceptions Inc<u></u><u></u></b></p><p class="MsoNormal">Tel: <a href="tel:514.488.3600" value="+15144883600" target="_blank">514.488.3600</a> ext. [284] | <a href="tel:877.796.3600" value="+18777963600" target="_blank">877.796.3600</a> ext. [284]<u></u><u></u></p>
<p class="MsoNormal">Fax: <a href="tel:514.484.2600" value="+15144842600" target="_blank">514.484.2600</a><u></u><u></u></p><p class="MsoNormal">London - Montreal - New York - Toronto<u></u><u></u></p><p class="MsoNormal">
[<a href="mailto:rtoth@iperceptions.com" target="_blank"><span style="color:blue">rtoth@iperceptions.com</span></a>] | <a href="http://www.iperceptions.com" target="_blank"><span style="color:blue">www.iperceptions.com</span></a><u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Subscribe to our blog: <a href="http://blog.iperceptions.com/" target="_blank"><span style="color:blue">blog.iperceptions.com</span></a><u></u><u></u></p><p class="MsoNormal">
Follow us on Twitter: <a href="http://www.twitter.com/iperceptions" target="_blank"><span style="color:blue">www.twitter.com/iperceptions</span></a><u></u><u></u></p><p class="MsoNormal">Register for our upcoming webinar “Is the check engine light ‘on’ for your analytics” at <a href="https://www1.gotomeeting.com/register/501539032" target="_blank"><span style="color:blue">https://www1.gotomeeting.com/register/501539032</span></a><u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal"><span style="font-size:9.0pt">The contents of this email and any attachments are confidential. They are intended for the named recipient(s) only and are not to be communicated to anyone else without permission. If you have received this email in error please notify the sender immediately and do not make copies or disclose the contents to anyone.<u></u><u></u></span></p>
<p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal"><img border="0" width="148" height="46" src="cid:image001.png@01CC8E0E.70F93B90" alt="cid:image001.png@01CB8183.17346640"><u></u><u></u></p><p class="MsoNormal">
<u></u> <u></u></p></div></div><br>_______________________________________________<br>
foundry-nsp mailing list<br>
<a href="mailto:foundry-nsp@puck.nether.net">foundry-nsp@puck.nether.net</a><br>
<a href="http://puck.nether.net/mailman/listinfo/foundry-nsp" target="_blank">http://puck.nether.net/mailman/listinfo/foundry-nsp</a><br></blockquote></div>