Configuration Guide Configuring NAT
No static route is configured or no IP address is configured for the outside interface, so that the router does not know
to which interface a data packet should be sent after NAT or from which interface a data packet is received after
NAT.
10.4.4 Configuring TCP Load Balancing
Networking
Requirements
When the TCP traffic load of an intranet host is excessively heavy, multiple hosts can be deployed to implement TCP
service load balancing. In this case, NAT can be used to attain this objective. In the following configuration, a virtual host
address is defined, so that all TCP connections from extranets to the virtual host are distributed by a router to multiple
physical hosts, so as to implement traffic load balancing.
Notes
The newly configured NAT rules take effect on new flows only but not on any existing flows.
Configuration Steps
Configuring Dynamic Translation of Inside Destination Address
Mandatory configuration.
Configure dynamic translation of inside destination address in global configuration mode for TCP load balancing.
Verification
N/A
Commands
Configuring the NAT Inside Interface and the NAT Outside Interface
ip nat { inside | outside }
inside: inside interface
outside: outside interface
Interface configuration mode
NAT does not work on a data packet unless a route exists between the outside interface and the inside
interface and the data packet meets a certain rule. Therefore, at least one inside interface and one
outside interface need to be configured on the router.
Configuring the Address Pool
ip nat pool address-pool start-address end-address { netmask mask |
prefix-length prefix-length } [ type rotary ]
To Next Page
Loading...
