Thanks.

I have searched all internet :) looking for this and this is first precise answer.

Not even combined with some form of routing, and than if one route "fails", the other kicks in? Like on the above link?

Scripting is a good idea though.

Thanks a ton.

I have used the above procedure for outbound connections before. It is very effecitve. But i'm afraid nothing like this will work inbound.

I did not look at this in much detail. But have a look and see if this is along the lines of what you require. It does seem as tho some extra hardware would be required.

http://www.cisco.com/en/US/docs/ios/12_3t/12_3t7/feature/guide/gtsnatay.html#wp1046675

HTH

Regards

Stephen

One of the load balance methods I have seen pretty much puts the virtual address sharing on the servers themselves. Our web proxies work this way.

What happens is you put a "loopback" address on each server with same ip address. When the server responds to users it always uses this loopback address as his source rather than his true ethernet address.

So if your server application can accomplish this you can make this work.

The Nat part is simple you put in a static from the outside to the shared inside.

To make the "loadbalance" work you would put a policy route on the outside interface and set the nexthop to the server ethernet address you want to process the data. The policy routing can track RTR object to select which server to send to.

Thank you all! Now at least I know what are my options!

Hello Sir,

This scenario provides failover for your website. The primary web server is WEB_A. The R2 router is send a ping the virtual ip of WEB_A in every 4 seconds and the wating for the response for 2 seconds. If the WEB_A fails then the router will switch to WEB_B.

Of course the router is keep pinging the virtual ip address, but it will never response anymore. So if WEB_A is recovered, you have to manually set the same virtual ip address for WEB_B. Onece the router is chaged the static route back to WEB_A (should happen in few seconds) you should remove the virtual address from WEB_B config.

Here is my solution for you:

And the configs:

http://www5.zippyshare.com/v/29325000/file.html

PS: i can see that this topic is very old, but my asnwer might helps to others. If so please rate

/edit:

You can use NAT load balancing aswell.

ip nat pool 'poolname' prefix-length 24 type rotary

ip address 'start' 'end'

ip nat inside destination list 100 pool 'poolname'

access-list 100 permit tcp any host xxxxx eq 80 (use any instead of host xxx if you have more pub addresses)

This scenario will provide a load balance between the servers. If one of them fails then every second attemp to load the page will fail.