Allow inbound service traffic. Select from the following options:

• HTTP—Enables connections to the web UI. We recommend this option only for network interfaces connected to a trusted private network, or directly to your management computer.
• HTTPS—Enables secure connections to the web UI. We recommend this option instead of HTTP.
• Ping—Enables ping and traceroute to be received on this network interface. When it receives an ECHO_REQUEST (“ping”), FortiADC will reply with ICMP type 0 (ECHO_RESPONSE or “ping”).
• SNMP—Enables SNMP queries to this network interface.
• SSH—Enables SSH connections to the CLI. We recommend this option instead of Telnet.
• Telnet—Enables Telnet connections to the CLI. We recommend this option only for network interfaces connected to a trusted private network, or directly to your management computer.

The MAC address is read from the interface. If necessary, you can set the MAC address.

Enable or disable.

The default is 1500. We recommend you maintain the default.

Select one of the following speed/duplex settings:

• Auto—Speed and duplex are negotiated automatically. Recommended.
• 10half—10 Mbps, half duplex.
• 10full—10 Mbps, full duplex.
• 100half—100 Mbps, half duplex.
• 100full—100 Mbps, full duplex.
• 1000half—1000 Mbps, half duplex.
• 1000full—1000 Mbps, full duplex.

This Status column is not the detected physical link status; it is the administrative status (Up/Down) that indicates whether you permit the network interface to receive and/or transmit packets.

If applicable, select the virtual domain to which the configuration applies.

• Static—Specify a static IP address. The IP address must be on the same subnet as the network to which the interface connects. Two network interfaces cannot have IP addresses on the same subnet (i.e. overlapping subnets).
• PPPoE—Use PPPoE to retrieve a configuration for the IP address, gateway, and DNS server. For example, if this interface uses a DSL connection to the Internet, your ISP may require this option.

If you are editing the configuration for a physical interface, you cannot set the type.

If you are configuring a logical interface, you can select from the following options:

• Aggregate—A logical interface you create to support the aggregation of multiple physical interfaces.
• VLAN—A logical interface you create to VLAN subinterfaces on a single physical interface.

set mode static

Specify the IP address and CIDR-formatted subnet mask, separated by a forward slash ( / ), such as 192.0.2.5/24. Dotted quad formatted subnet masks are not accepted.

Specify the IP address and CIDR-formatted subnet mask, separated by a forward slash ( / ), such as 2001:0db8:85a3:::8a2e:0370:7334/64. Dotted quad formatted subnet masks are not accepted.

set mode pppoe

Seconds the system waits before it retries to discover the PPPoE server.

Use the DNS addresses retrieved from the PPPoE server instead of the one configured in the FortiADC system settings.

Disconnect after idle timeout in seconds. The default is 0. The valid range is 0 to 32,000.

LCP echo interval in seconds. The default is 5. The valid range is 1 to 255.

Maximum missed LCP echo messages before disconnect. The default is 3. The valid range is 1 to 255.

Use the default gateway retrieved from the PPPoE server instead of the one configured in the FortiADC system settings.

PPPoE account user name.

PPPoE account password.

set type vlan

VLAN ID of packets that belong to this VLAN.

If one physical network port (that is, a VLAN trunk) will handle multiple VLANs, create multiple VLAN subinterfaces on that port, one for each VLAN ID that will be received.

If multiple different physical network ports will handle the same VLANs, on each of the ports, create VLAN subinterfaces that have the same VLAN IDs.

The valid range is between 1 and 4094. The value you specify must match the VLAN ID added by the IEEE 802.1q-compliant router or switch connected to the VLAN subinterface.

Physical interface associated with the VLAN; for example, port2.

set type aggregate

Connectivity layers that will be considered when distributing frames among the aggregated physical ports:

• Layer 2
• Layer 2-3
• Layer 3-4

Link aggregation type:

• 802.3ad
• Balance-alb
• Balance-rr
• Balance-tlb
• Balance-xor
• Broadcast

Specify the physical interfaces that are included in the aggregation.

config secondary-ip-list

Allow inbound service traffic. Specify a space-separated list of the following options:

• HTTP—Enables connections to the web UI. We recommend this option only for network interfaces connected to a trusted private network, or directly to your management computer.
• HTTPS—Enables secure connections to the web UI. We recommend this option instead of HTTP.
• Ping—Enables ping and traceroute to be received on this network interface. When it receives an ECHO_REQUEST (“ping”), FortiADC will reply with ICMP type 0 (ECHO_RESPONSE or “pong”).
• SNMP—Enables SNMP queries to this network interface.
• SSH—Enables SSH connections to the CLI. We recommend this option instead of Telnet.
• Telnet—Enables Telnet connections to the CLI. We recommend this option only for network interfaces connected to a trusted private network, or directly to your management computer.

Secondary IP addresses can be used when you deploy the system so that it belongs to multiple logical subnets. If you assign multiple IP addresses to an interface, you must assign them static addresses.

To add secondary IP addresses, enable the feature and save the configuration. After you have saved it the first time, you can edit it to add secondary IP addresses and enable inbound traffic to that address.

config ha-node-ip-list

You use the HA node IP list configuration in an HA active-active deployment. For each HA cluster node, configure an HA node IP list that includes an entry for each cluster node. When the appliance is in standalone mode, it uses the physical port IP address; when it is in HA mode, it uses the HA node IP address.

For each address, specify an IP address using the CIDR-formatted subnet mask, separated by a forward slash ( / ), such as 192.0.2.5/24.

ID of the corresponding node.

You use the HA node secondary IP list configuration if the interfaces of the nodes in an HA active-active deployment are configured with secondary IP addresses.

For each address, specify an IP address using the CIDR-formatted subnet mask, separated by a forward slash ( / ), such as 192.0.2.5/24.