Fortinet black logo

FortiGate-7000 Release Notes

Home FortiGate-7000 7.0.12 FortiGate-7000 Release Notes
7.0.12
7.0.15
7.0.14
7.0.13
7.0.12
7.0.10
7.0.5
6.4.15
6.4.14
6.4.13
6.4.12
6.4.10
6.4.8
6.4.6
6.4.2
6.2.16
6.2.15
6.2.13
6.2.12
6.2.11
6.2.10
6.2.9
6.2.7
6.2.6
6.2.4
6.2.3
6.0.18
6.0.17
6.0.16
6.0.15
6.0.14
6.0.13
6.0.12
6.0.10
6.0.9
6.0.8
6.0.6
6.0.4
5.6.14
5.6.12
5.6.11
5.6.7
5.6.6
5.4.9
5.4.5
5.4.3

FortiGate-6000F and 7000E IPsec load balancing EMAC VLAN interface limitation

FortiGate-6000F and 7000E IPsec load balancing EMAC VLAN interface limitation

On a FortiGate-6000F or 7000E, because of a DP processor limitation, IPsec VPN load balancing is not supported for sessions received by an EMAC VLAN interface that is not in the same VDOM as the interface that the EMAC VLAN interface has been added to.

Note

The FortiGate-7000F platform uses NP7 processors for load balancing, so this limitation does not apply.

On a FortiGate-6000F or 7000E, the following workarounds are available:

  • Change the FortiGate configuration so that the EMAC VLAN interface is in the same VDOM as the interface that the EMAC VLAN interface is added to (the EMAC VLAN interface is in the same VDOM as its parent interface).

  • Disable IPsec VPN load balancing and configure the IPsec phase 1 to send packets to the primary FPC or FPM or to a specific FPC or FPM. If you have multiple IPsec VPNs, you can achieve some load balancing by configuring different IPsec phase 1 configurations to send packets to different FPCs or FPMs.

    In addition, for each IPsec phase 1, create a flow rule to forward clear-text traffic from the EMAC VLAN interface to the primary FPC or FPM or to a specific FPC or FPM. The FPC or FPM in the flow rule must match the FPC or FPM in the IPsec phase 1 configuration.

  • Do not use EMAC VLAN interfaces. For example, you could use standard VLAN interfaces. This may require using an external switch to handle VLAN tagging.

Previous
Next

FortiGate-6000F and 7000E IPsec load balancing EMAC VLAN interface limitation

On a FortiGate-6000F or 7000E, because of a DP processor limitation, IPsec VPN load balancing is not supported for sessions received by an EMAC VLAN interface that is not in the same VDOM as the interface that the EMAC VLAN interface has been added to.

Note

The FortiGate-7000F platform uses NP7 processors for load balancing, so this limitation does not apply.

On a FortiGate-6000F or 7000E, the following workarounds are available:

  • Change the FortiGate configuration so that the EMAC VLAN interface is in the same VDOM as the interface that the EMAC VLAN interface is added to (the EMAC VLAN interface is in the same VDOM as its parent interface).

  • Disable IPsec VPN load balancing and configure the IPsec phase 1 to send packets to the primary FPC or FPM or to a specific FPC or FPM. If you have multiple IPsec VPNs, you can achieve some load balancing by configuring different IPsec phase 1 configurations to send packets to different FPCs or FPMs.

    In addition, for each IPsec phase 1, create a flow rule to forward clear-text traffic from the EMAC VLAN interface to the primary FPC or FPM or to a specific FPC or FPM. The FPC or FPM in the flow rule must match the FPC or FPM in the IPsec phase 1 configuration.

  • Do not use EMAC VLAN interfaces. For example, you could use standard VLAN interfaces. This may require using an external switch to handle VLAN tagging.

Previous
Next