Configuration Guide 5. NAT and NAPT
Version 7.2 23 Security Setup
5.1.3 Configuring Load Balancing using NAT
This example includes two HTTP servers on the NAT side. One with IP address 192.168.0.3
and one with IP address 192.168.0.4. Both are identical HTTP server with main page. To
access these servers, a secondary IP address of the WAN interface GigabitEthernet 0/0 is
configured. The main IP address of the WAN interface is 180.1.100.1 and the secondary is
180.1.100.10.
# configure data
(config-data)# interface gigabitethernet 0/0
(conf-if-GE 0/0)# ip address 180.1.100.1 255.255.255.0
(conf-if-GE 0/0)# ip address 180.1.100.10 255.255.255.0 secondary
(conf-if-GE 0/0)# exit
(config-data)# ip nat pool L-balancing 192.168.0.3 192.168.0.4
rotary
(config-data)# ip nat inside destination 180.1.100.10 port 80 pool
L-balancing
(config-data)#
The output of the show data ip nat translations command displays a source
address 180.1.100.20 from port 4355 that accesses IP address 180.1.100.10 on port 80. The
connection is then NATed to the inside address of 192.168.0.3:80.
# show data ip nat translations
(Note: static translations are not shown)
NAT summary: 1 TCP, 0 UDP, 0 ICMP. Total 1 NAT connections.
.Pro Inside global Inside local Outside local
Outside global Timeout
TCP 180.1.100.10:80 192.168.0.3:80 180.1.100.20:4355
180.1.100.20:4355 86395
After waiting a while, a refresh command is issued at the source and the source accesses
the external IP address again. Now the output of the show data ip nat translations
command displays that the other HTTP server with the IP address 192.168.0.4 was
accessed:
# show data ip nat translations
(Note: static translations are not shown)
NAT summary: 1 TCP, 0 UDP, 0 ICMP. Total 1 NAT connections.
.Pro Inside global Inside local Outside local
Outside global Timeout
TCP 180.1.100.10:80 192.168.0.4:80 180.1.100.20:4356
180.1.100.20:4356 86397