Configuring load sharing NAT Server

You can add multiple internal servers to an internal server group so that these servers provide the same service for external hosts. The NAT device chooses one internal server based on the weight and number of connections of the servers to respond to a request from an external host to the public address of the internal server group.

When you configure load shared internal servers, you must make sure a user uses the same public address and public port to access the same service on an internal server. For this purpose, make sure value N in the following mappings is equal to or less than the number of servers in the internal server group:

To configure load sharing NAT Server:

Step

Command

Remarks

1. Enter system view.

system-view

N/A

2. Configure a NAT Server group and enter its view.

nat server-group group-id

By default, no NAT Server groups exist.

3. Add an internal server into the group.

inside ip inside-ip port port-number [ weight weight-value ]

By default, no internal servers exist.

You can add multiple internal servers to a group.

4. Return to system view.

quit

N/A

5. Enter interface view.

interface interface-type interface-number

N/A

6. Configure load sharing NAT Server.

nat server protocol pro-type global { { global-address | current-interface | interface interface-type interface-number } { global-port | global-port1 global-port2 } | global-address1 global-address2 global-port } [ vpn-instance global-vpn-instance-name ] inside server-group group-id [ vpn-instance local-vpn-instance-name ] [ acl { ipv4-acl-number | name ipv4-acl-name } ] [ disable ]

By default, no load sharing NAT Server mappings exist.

You can configure multiple load sharing NAT Server mappings on an interface.