Load balancing to a router?

[JoeyHogan]

Hi all!

We have an HP 8212zl acting as the core switch for our organization. On this switch, we have a VLAN setup for our internet connection:

vlan 9
 name "AT&T MIS to Internet"
 untagged A16
 ip address 10.9.1.4 255.255.255.0
 exit

 And then port A16 is connected to our web filter (10.9.1.5), and that's then connected to a Cisco ASA 5510 (10.9.1.2) which acts as our edge device/router. So we just use a simple default route on the 8212zl to send all of the internal traffic to the internet:

ip route 0.0.0.0 0.0.0.0 10.9.1.2

Over the summer, we're upgrading our Internet connection to a 1Gbps pipe, and replacing the ASA 5510 with a 5512-x. However, our web filter is not capable of handling such high speeds, and it'd be cheaper to buy a second filter and run it in parallel than it would be to buy one that can run at 1Gbps.

So what we'd like to do is create a second internal interface on the ASA, plug one web filter into each inside interface, and then plug each filter into the core switch, effectively creating two physical paths between the 8212 and the ASA. 

If we do this, however, is there any way to setup the 8212zl to balance traffic between the two? I don't mind if it requires creating a second VLAN, but I'm just trying to figure out the best way to take advantage of this additional bandwidth at the lowest possible cost.

Thanks!

Joey

[cenk sasmaztin]

is normal result for routing operation ....

what is your web filter software

[JoeyHogan]

We're using Cymphonix right now.

[cenk sasmaztin]

I don't any idea Chmphonix

but many web filtering services running two mode... routing and monitoring.

if cymphonix system running  monitoring mode  good news for you..

network users go to directly internet via vlan on the asa

and running any report or deny web traffic with monitor and mirror port configuration on switch..

can running cymphonix  system monitor state ?

[Vince_Whirlwind]

I am not aware you can do this with a L3 switch - you would need a dedicated load-balancing solution to do this.

On the other hand, if you are just trying to get some traffic going out via a different path, put in a PBR identifying your test PC and routing traffic from it for 0.0.0.0 at the new ASA IP address. The ASA will need a normal route routing traffic for your new PC out its new interface as well.