<html>
<body>
FWLB relies heavily on FW-paths... I have never seen this working with
ServerIrons at one side only - I personally would not go for this. I
would go for LLB...<br><br>
This would imply you are going to do NAT twice... you do need two
transfer subnets in between the ServerIron (standalone) and the FWs. One
subnet for each FW. The ServerIron needs a physical IP per subnet and it
needs a NAT IP per subnet. Configure LLB similar to the config example in
the documentation BUT use the FWs as upstream routers instead of the ISP
facing routers. The FWs need to do NAT again towards the ISP(s). I would
go for health check checking something in front of the FWs - this helps
to verify that the FW is up and running and the device in front of the
FW...<br><br>
Should be straight forward... <br><br>
R, Oliver<br><br>
<br>
At 21:57 28.04.2009, John McCabe [Ext. 363] wrote:<br>
<blockquote type=cite class=cite cite="">Content-Language: en-US<br>
Content-Type: multipart/alternative;<br>
<x-tab> </x-tab>
boundary="_000_771397A62D34774DB13A1AE1E5A33C352477A16974exch2007Ridea_"<br>
<br>
I know what I would like, I know the diff between link load balance as
FWLB.<br>
I want to balance all traffic going out of our network, i want to balance
this over out 2 10 meg links.<br>
<br>
Each link has its own firewall so i would like to link load balance, but
before the firewall, this may be the best way to do it,<br>
has anyone tried?<br>
I have multiple LB units I just don’t want to set up the whole meshed
system in the FWLB scenario. Seems overkill from where I am
standing.<br>
<br>
<br>
<br>
<br>
john<br><br>
<hr>
<font size=1 color="#808080">RIDEAU CONFIDENTIALITY NOTICE<br>
This communication may contain privileged or confidential information. If
you are not the intended recipient or received this communication by
error, please notify the sender by reply email and delete the message
without copying or disclosing it.<br><br>
AVIS DE CONFIDENTIALITÉ DE RIDEAU<br>
Ce message peut contenir de l'information légalement privilégiée ou
confidentielle. Si vous n'êtes pas le destinataire ou croyez avoir reçu
ce message par erreur, nous vous saurions gré d'en aviser l'émetteur par
courriel et d'en détruire le contenu sans le communiquer à d'autres ou le
reproduire.<br><br>
AVISO DE CONFIDENCIALIDAD DE RIDEAU<br>
Este mensaje puede contener información privilegiada o confidencial. Si
usted no es la persona a quien estaba dirigido el mensaje o si recibió
este mensaje por error, notifique a quien se lo envió por correo
electrónico y elimine el mensaje sin copiarlo o divulgarlo.<br>
</font>_______________________________________________<br>
foundry-nsp mailing list<br>
foundry-nsp@puck.nether.net<br>
<a href="http://puck.nether.net/mailman/listinfo/foundry-nsp" eudora="autourl">
http://puck.nether.net/mailman/listinfo/foundry-nsp</a></blockquote>
</body>
<br>
</html>