Configuring Load Sharing Nat Server - HPE FlexNetwork HSR6800 Configuration Manual

Step
3. Configure one or
more common
NAT Server
mappings.

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:
•
One public address and N consecutive public port numbers are mapped to one internal server
group.
•
N consecutive public addresses and one public port number are mapped to one internal server
group.
To configure load sharing NAT Server:
Step
1. Enter system view.
Command
•
A single public address with a single or no public port:
nat server [ protocol pro-type ] global
{ global-address | current-interface | interface
interface-type interface-number } [ global-port ]
[ vpn-instance global-vpn-instance-name ] inside
local-address [ local-port ] [ vpn-instance
local-vpn-instance-name ] [ acl { ipv4-acl-number |
name ipv4-acl-name } ] [ reversible ] [ disable ]
[ description text ]
•
A single public address with consecutive public ports:
nat server protocol pro-type global { global-address
| current-interface | interface interface-type
interface-number } global-port1 global-port2
[ vpn-instance global-vpn-instance-name ] inside
{ { local-address | local-address1 local-address2 }
local-port | local-address local-port1 local-port2 }
[ vpn-instance local-vpn-instance-name ] [ acl
{ ipv4-acl-number | name ipv4-acl-name } ] [ disable ]
[ description text ]
•
Consecutive public addresses with a single or no
public port:
nat server protocol pro-type global global-address1
global-address2 [ global-port ] [ vpn-instance
global-vpn-instance-name ] inside { local-address |
local-address1 local-address2 } [ local-port ]
[ vpn-instance local-vpn-instance-name ] [ acl
{ ipv4-acl-number | name ipv4-acl-name } ] [ disable ]
[ description text ]
•
Consecutive public addresses with a single public
port:
nat server protocol pro-type global global-address1
global-address2 global-port [ vpn-instance
global-vpn-instance-name ] inside local-address
local-port1 local-port2 [ vpn-instance
local-vpn-instance-name ] [ acl { ipv4-acl-number |
name ipv4-acl-name } ] [ disable ] [ description text ]
Command
system-view
128
Remarks
By default, no NAT
Server mappings
exist.
You can configure
multiple NAT Server
mappings on an
interface.
Remarks
N/A