From: Kevin Young (kvyoung@xxxxxxxx)
Date: Thu Jun 29 2000 - 00:00:16 GMT-3
This feature was designed to provide protocol translation load distribution. It
is not designed nor intended to be used as a substitute technology for Cisco's
LocalDirector product. Destination address rotary translation should not be us
ed to provide web service load balancing because, like vanilla DNS, it knows no
thing about service availability. As a result, if a web server were to become o
ffline, the destination address rotary translation feature would continue to se
nd requests to the downed server.
**************************************
Kevin Young
Senior Network Engineer
Yinxi Electronic Information Co.,Ltd
(86)-10-82625798 x 810
**************************************
----- Original Message -----
From: Derek Buelna <dameon@aracnet.com>
To: <ccielab@groupstudy.com>
Sent: Thursday, June 29, 2000 7:53 AM
Subject: ip nat inside destination
> Hi,
>
> I am trying to figure out the details of using the ip nat inside destination
> command.
> When initially learning about NAT, I recall something about load balancing.
> An engineer at the TAC said that I can't do it and should use a Local
> Director. I don't believe him.
>
> Anyone get something like this to work?
>
> int e0
> ip addr 10.0.1.1 255.255.255.0
> ip nat out
>
> int e1
> ip addr 10.0.2.1 255.255.255.0
> ip nat in
>
> ip nat inside destination list 1 pool WEBSERV
> ip nat pool WEBSERV 10.0.2.50 10.0.2.55 prefix-length 24
> access-list 1 permit 10.0.2.50
> access-list 1 permit 10.0.2.51
> access-list 1 permit 10.0.2.52
> access-list 1 permit 10.0.2.53
> access-list 1 permit 10.0.2.54
> access-list 1 permit 10.0.2.55
>
> Thanks,
>
> -Derek
>
> Derek A. Buelna, CCNP CCDP MCSE
> Network Engineer
> Firstworld Communications
>
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:23:43 GMT-3