Fortinet Document Library

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:


Table of Contents

FortiGate-7000 Release Notes

FGSP with LAG session synchronization interfaces

The FortiGate-6000 and FortiGate-7000F for FortiOS 6.4.6 supports using a LAG for FGSP session synchronization. Using a LAG for session synchronization provides redundancy and load sharing. This feature is not currently supported by the FortiGate-7000E.

For the FortiGate-6000 you can create an aggregate interface using the HA1 and HA2 interfaces:

Example LAG configuration:

config system interface

edit ha1-ha2

set vdom mgmt-vdom

set ip 10.1.1.1 255.255.255.0

set type aggregate

set member ha1 ha2

end

Example cluster sync configuration:

config system cluster-sync

edit 1

set peervd mgmt-vdom

set peerip 10.1.1.2

set syncvd <vdoms >

end

Example HA configuration:

config system ha

set session-pickup enable

set session-pickup-connectionless enable

set session-pickup-expectation enable

set session-pickup-nat enable

end

For the FortiGate-7000F, you can create an aggregate of 100G interfaces using the M1 and M2 interfaces of both FIMs. You can also create an aggregate of 10G interfaces using the M3 and M4 interfaces of both FIMs. Choose the interfaces to create the LAG with depending on your session synchronization bandwidth requirements and the other uses you might have for these interfaces.

Example LAG configuration using the M1 interfaces of both FIMs.

config system interface

edit sess-sync-lag

set vdom mgmt-vdom

set ip 10.1.1.1 255.255.255.0

set type aggregate

set member 1-M1 2-M1

end

Example cluster sync configuration:

config system cluster-sync

edit 1

set peervd mgmt-vdom

set peerip 10.1.1.2

set syncvd <vdoms >

end

Example HA configuration:

config system ha

set session-pickup enable

set session-pickup-connectionless enable

set session-pickup-expectation enable

set session-pickup-nat enable

end

FGSP with LAG session synchronization interfaces

The FortiGate-6000 and FortiGate-7000F for FortiOS 6.4.6 supports using a LAG for FGSP session synchronization. Using a LAG for session synchronization provides redundancy and load sharing. This feature is not currently supported by the FortiGate-7000E.

For the FortiGate-6000 you can create an aggregate interface using the HA1 and HA2 interfaces:

Example LAG configuration:

config system interface

edit ha1-ha2

set vdom mgmt-vdom

set ip 10.1.1.1 255.255.255.0

set type aggregate

set member ha1 ha2

end

Example cluster sync configuration:

config system cluster-sync

edit 1

set peervd mgmt-vdom

set peerip 10.1.1.2

set syncvd <vdoms >

end

Example HA configuration:

config system ha

set session-pickup enable

set session-pickup-connectionless enable

set session-pickup-expectation enable

set session-pickup-nat enable

end

For the FortiGate-7000F, you can create an aggregate of 100G interfaces using the M1 and M2 interfaces of both FIMs. You can also create an aggregate of 10G interfaces using the M3 and M4 interfaces of both FIMs. Choose the interfaces to create the LAG with depending on your session synchronization bandwidth requirements and the other uses you might have for these interfaces.

Example LAG configuration using the M1 interfaces of both FIMs.

config system interface

edit sess-sync-lag

set vdom mgmt-vdom

set ip 10.1.1.1 255.255.255.0

set type aggregate

set member 1-M1 2-M1

end

Example cluster sync configuration:

config system cluster-sync

edit 1

set peervd mgmt-vdom

set peerip 10.1.1.2

set syncvd <vdoms >

end

Example HA configuration:

config system ha

set session-pickup enable

set session-pickup-connectionless enable

set session-pickup-expectation enable

set session-pickup-nat enable

end