I would set teaming in the web server to start with. Then both routers have to be connected to each switch. The problem is the gateway. Server will see the public ip of client, and it can only have one default gateway.

You can:

  • Set up HSRP on the lan side between your 2 routers
  • Change the client IP by the one of your router (each one its ip), so the webserver send packet to them without going through a default gateway

The HSRP ip 1 and 2 are not so clear on their usage


You would really need HSRP running on the inside interfaces of the routers so that you have a single gateway to the outside world.

As long as you have a solid layer 2 config on the inside, this should be fine otherwise. You would not want teaming on the webserver, however you might consider bridging to a single L3 address as long as you make sure that your spanning-tree setup is solid (else, there is the strong possibility of a bridge loop).

edit: if the comment above is correct in that the co-lo is handing you an HSRP address as your gateway, then disregard my comment about adding HSRP to the inside interface of those routers. At that point, the routers are actually sort of redundant, and you would be better served by putting a fault-tolerant firewall setup (some cheap PIXs or such) there.