From: Brian Hescock (bhescock@xxxxxxxxx)
Date: Thu Jun 29 2000 - 08:52:35 GMT-3
Derek,
Actually, you're correct and it does work. The key is you need two
different access-lists, one of them defines the virtual ip address that
the outside world connects to. Something else you need is "type rotary".
Here's a working config (minus the standard interface info):
ip nat pool load-dist 10.1.12 10.1.1.3 netmask 255.255.255.255.0 type
rotary
ip nat inside destination list 3 pool load-dist
access-list 1 permit 10.0.0.0 0.255.255.255
access-list 3 permit 200.200.200.3
Brian
On Wed, 28 Jun 2000, Derek Buelna wrote:
> 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