FortiGate-6000 7.4.3 incompatibilities and limitations

FortiGate 6000F for FortiOS 7.4.3 has the following limitations and incompatibilities with FortiOS features:

The FortiGate 6000F uses the Fortinet Security Fabric for communication and synchronization between the management board and the FPCs and for normal GUI operation. By default, the Security Fabric is enabled and must remain enabled for normal operation.

Remote console limitations

Some console input may not function as expected. For example, when remotely connecting to an FPC console using Telnet, when viewing the BIOS menu, pressing the H key to display BIOS menu help does not always work as expected.

Default management VDOM

By default the FortiGate-6000 configuration includes a management VDOM named mgmt-vdom. The ha1, ha2, mgmt1, mgmt2, and mgmt3 interfaces are in mgmt-vdom and all other interfaces are in the root VDOM. For the FortiGate-6000 system to operate normally, mgmt-vdom must always be the management VDOM. You also must not remove interfaces from this VDOM. You can change the IP addresses of the interfaces in mgmt-vdom, allow the required management services, and add routes as required for management traffic.

You have full control over the configurations of other FortiGate-6000 VDOMs.

Maximum number of LAGs and interfaces per LAG

FortiGate-6000 systems support up to 16 link aggregation groups (LAGs). This includes both normal link aggregation groups and redundant interfaces. A FortiGate-6000 LAG can include up to 20 interfaces.

High Availability

Only the HA1 and HA2 interfaces are used for the HA heartbeat communication. For information on how to set up HA heartbeat communication using the HA1 and HA2 interfaces, see Connect the HA1 and HA2 interfaces for HA heartbeat communication.

The following FortiOS HA features are not supported or are supported differently by FortiGate-6000:

Active-active HA is not supported.
The range for the HA group-id is 0 to 255.
Failover logic for FortiGate-6000 HA is the same as FGCP for other FortiGate clusters.
HA heartbeat configuration is specific to FortiGate-6000 systems and differs from standard HA.

FortiGate-6000 HA does not support the route-wait and route-hold options for tuning route synchronization between FortiGate-6000s.
VLAN monitoring using the config system ha-monitor command is not supported.
FortiGate-6000 HA does not support using the HA session-sync-dev option. Instead, session synchronization traffic uses the HA1 and HA2 interfaces, separating session sync traffic from data traffic.
For information about virtual clustering limitations, see Limitations of FortiGate-6000 virtual clustering and Virtual clustering VLAN/VDOM limitation.

FortiOS features that are not supported by FortiGate-6000 7.4.3

The following mainstream FortiOS features are not supported by the FortiGate-6000:

Hardware switch.
DLP archiving.
GRE tunneling is only supported after creating a load balance flow rule, for example:

config load-balance flow-rule

edit 0

set status enable

set vlan 0

set ether-type ip

set protocol gre

set action forward

set forward-slot master

set priority 3

end

Only the FortiGate 6001F, FortiGate 6301F, and FortiGate 6501F support hard disk features such as disk logging, and GUI-based packet sniffing.
The FortiGate 6000F platform, including the FortiGate 6001F, FortiGate 6301F, and FortiGate 6501F do not support quarantining files to the internal hard disks. Instead you must set the quarantine function to quarantine files to FortiAnalyzer.
The management interfaces (mgmt1-3) do not support device detection for the networks they are connected to.
The FortiGate-6000 does not support configuring dedicated management interfaces using the config system dedicated-mgmt command or by enabling the dedicated-to management interface option. The purpose of the dedicated management interface feature is to add a routing table just for management connections. This functionality is supported by the FortiGate-6000 management VDOM (mgmt-vdom) that has its own routing table and contains all of the FortiGate-6000 management interfaces.
The FortiOS session-ttl option never (which means no session timeout) is only supported if the dp-load-distribution-method is set to src-dst-ip-sport-dport (the default) or src-dst-ip and the firewall policy that accepts the session does not perform NAT. If any other load distribution method is used, or if NAT is enabled, the DP session timer will terminate the session according to the DP processor session timer. For more information about the never option, see No session timeout.
Enabling the system settings option tcp-session-without-syn and configuring a firewall policy to accept sessions without syn packets allows FortiOS to add entries to its session table for sessions that do not include SYN packets. These sessions can only be load balanced by the DP processor if the dp-load-distribution-method is set to src-dst-ip-sport-dport (default) or src-dst-ip. If any other load distribution method is used, the sessions will be dropped. As well, the DP processor cannot load balance these sessions if they are accepted by a firewall policy with NAT enabled.
The source-ip option for management services (for example, logging, SNMP, connecting to FortiSandbox) that use interfaces in the mgmt-vdom is not supported and has been removed from the CLI.
The config vpn ssl settings option tunnel-addr-assigned-method is now available again. This option had been removed from the CLI in a previous release because setting this option to first-available and configuring multiple IP pools can reduce FortiGate 6000F SSL VPN load balancing performance. However, some users may want the ability to use multiple IP pools for their SSL VPN configuration, even if performance is reduced. So the change has been reverted.
The encryption option of the config system standalone-cluster command does not encrypt session synchronization traffic. Enabling this option has no effect.

IPsec VPN tunnels terminated by the FortiGate 6000F

For a list of IPsec VPN features not supported by FortiGate 6000F, see IPsec VPN load balancing.

Traffic shaping and DDoS policies

Each FPC applies traffic shaping and DDoS quotas independently. Because of load-balancing, this may allow more traffic than expected.

FortiGuard web filtering and spam filtering queries

The FortiGate-6000 sends all FortiGuard web filtering and spam filtering rating queries through a management interface from the mgmt-vdom VDOM.

Web filtering quotas

On a VDOM operating with the Inspection Mode set to Proxy, you can go to Security Profiles > Web Filter and set up Category Usage Quotas. Each FPC has its own quota, and the FortiGate-6000 applies quotas per FPC and not per the entire FortiGate-6000 system. This could result in quotas being exceeded if sessions for the same user are processed by different FPCs.

Special notice for new deployment connectivity testing

Only the management board can successfully ping external IP addresses. During a new deployment, while performing connectivity testing from the Fortigate-6000, make sure to run execute ping tests from the management board and not from an FPC. See Using data interfaces for management traffic for information about changes to this limitation.

Display the process name associated with a process ID

You can use the following command to display the process name associated with a process ID (PID):

diagnose sys process nameof <pid>

Where <pid> is the process ID.