Giuseppe Larosa Wed, 11/11/2009 - 09:45
User Badges:
  • Super Silver, 17500 points or more
  • Hall of Fame,

    Founding Member

Hello Sherwin,

using NAT you can implement a "poor man " load balancer


see

http://www.cisco.com/en/US/tech/tk648/tk361/technologies_configuration_example09186a0080950834.shtml


or better for you :


Avoiding Server Overload Using Load Balancing: Example


In the following example, the goal is to define a virtual address, connections to which are distributed among a set of real hosts. The pool defines the addresses of the real hosts. The access list defines the virtual address. If a translation does not already exist, TCP packets from serial interface 0 (the outside interface) whose destination matches the access list are translated to an address from the pool.


ip nat pool real-hosts 192.168.15.2 192.168.15.15 prefix-length 28 type rotary


ip nat inside destination list 2 pool real-hosts


!


interface serial 0


ip address 192.168.15.129 255.255.255.240


ip nat outside


!


interface ethernet 0


ip address 192.168.15.17 255.255.255.240


ip nat inside


!


access-list 2 permit 192.168.15.1



see

http://www.cisco.com/en/US/docs/ios/ipaddr/configuration/guide/iadnat_addr_consv_ps6350_TSD_Products_Configuration_Guide_Chapter.html#wp1073492


Hope to help

Giuseppe


Actions

This Discussion