config load-balance ippool
Use this command to configure a NAT IP address range pool to be used in a Layer 4 virtual server deployment
In a Layer 4 virtual server configuration, you select a “packet forwarding method” that includes the following network address translation (NAT) options:
- Direct Routing—Does not rewrite source or destination IP addresses.
- DNAT—Rewrites the destination IP address for packets before it forwards them.
- Full NAT—Rewrites both the source and destination IP addresses. Use for standard NAT, when client and server IP addresses are all IPv4 or all IPv6.
- NAT46—Rewrites both the source and destination IP addresses. Use for NAT 46, when client IP addresses are IPv4 and server IP addresses are IPv6.
- NAT64—Rewrites both the source and destination IP addresses. Use for NAT 64, when client IP addresses are IPv6 and server IP addresses are IPv4.
In a Layer 7 virtual server configuration, you do not select a packet forwarding option. Layer 7 virtual servers use NAT46 and NAT64 to support those traffic flows, but they do not use the Source Pool configuration.
See the FortiADC Handbook for example usage.
Before you begin:
- You must have a good understanding of NAT. You must know the address ranges your network has provisioned for NAT.
- Be sure to configure the backend servers to use the FortiADC address as the default gateway so that server responses are also rewritten by the NAT module.
- You must have read-write permission for load balancing settings.
After you have configured a source pool IP address range configuration object, you can select it in the virtual server configuration. You can assign a virtual server multiple source pools (with the same or different source pool interface associated with it).
Syntax
config load-balance ippool
edit <No.>
set interface <datasource>
set addr-type {ipv4|ipv6}
set ip-min <class_ip>
set ip-max <class_ip>
config node-member
edit <name>
set ha-node <integer>
set interface <datasource>
set addr-type {ipv4|ipv6}
set ip-min <class_ip>
set ip-max <class_ip>
next
end
next
end
interface |
Interface to receive responses from the backend server. The interface used for the initial client traffic is determined by the virtual server configuration. |
addr-type |
IPv4 or IPv6 |
ip-min |
The first address in the address pool. |
ip-max |
The last address in the address pool. |
config node-member | |
<name> |
Create a node member list to be used in an HA active-active deployment when the node interfaces have multiple IP addresses. Name is a configuration name. Valid characters are Note: After you initially save the configuration, you cannot edit the name. |
ha-node
|
Specify the HA cluster node ID. |
interface |
Interface to receive responses from the backend server. The interface used for the initial client traffic is determined by the virtual server configuration. |
addr-type |
IPv4 or IPv6 |
ip-min |
The first address in the address pool. |
ip-max |
The last address in the address pool. |