How to set up your FortiADC : Configuring the network settings : Configuring the network interfaces
Configuring the network interfaces
To connect to the CLI and web UI, you must assign at least one FortiADC network interface (usually port1) with an IP address and netmask so that it can receive your connections. Depending on your network, you usually must configure others so that FortiADC can connect to the Internet and to the servers whose load it balances.
How should you configure the other network interfaces? Should you add more? Should each have an IP address? That varies.
Initially, each physical network port (or, on FortiADC-VM, a vNIC) has only one network interface that directly corresponds to it — that is, a “physical network interface.” Multiple network interfaces (“subinterfaces” or “virtual interfaces”) can be associated with a single physical port, and vice versa (“redundant interfaces”/”NIC teaming”/”NIC bonding” or “aggregated links”). These can provide features such as link failure resilience or multi-network links.
FortiADC does not currently support IPSec VPN virtual interfaces, Layer 2 bridges, nor redundant links. If you require these features, implement them separately on your FortiGate, VPN appliance, or firewall.
Configure each network interface that will connect to your network or computer (see “Configuring the physical network interfaces”). If you want multiple networks to use the same wire while minimizing the scope of broadcasts, configure VLANs (see “Adding VLAN subinterfaces”).
See also
Configuring the physical network interfaces
Adding VLAN subinterfaces
Link aggregation