Fortinet white logo
Fortinet docs logo DOCUMENT LIBRARY
Fortinet white logo
Fortinet docs logo DOCUMENT LIBRARY
Products Best Practices Hardware Guides Products A-Z
Summary
By Solution
By 4D Pillars
By Cloud
Secure Networking
Unified SASE
Security Operations
Secure SD-WAN
Secure Access Service Edge (SASE)
ZTNA
LAN Edge
Identity and Access Management
Next Generation Firewall
Public Cloud
Private Cloud
FortiCloud
Secure Networking
  • Hybrid Mesh Firewall
  • NOC Management
  • LAN
  • WAN
    • More >>
    Unified SASE
  • Single Vendor SASE
  • Cloud Network Security
  • Secure Endpoint Connectivity
  • Web Application / API Protection
    • More >>
    Security Operations
  • Security Operations Automation
  • Identity
  • Early Detection & Prevention
    • More >>
    Secure Networking
  • Hybrid Mesh Firewall
  • NOC Management
  • LAN
  • WAN
  • Communication & Surveillance
    • Unified SASE
  • Single Vendor SASE
  • Secure Endpoint Connectivity
  • Cloud Network Security
  • Cloud-Native Security
  • Web Application / API Protection
    • Security Operations
  • Security Operations Automation
  • Endpoint
  • Data Protection
  • Identity
  • Email
  • Early Detection & Prevention
  • Expert Services
  • Edge Firewall
  • Orchestration & management
  • SD Branch
  • Application Delivery
  • Single Vendor SASE
  • Secure Endpoint Connectivity
  • Secure Private Access
  • Thin Edge
  • Identity
  • Application Gateway
  • Enterprise Asset Management
  • Endpoint Agent
  • Agentless Security Posture
  • Identity
  • Wireless
  • Switching
  • Identity
  • Privilege Acccess Management
  • Next Generation Firewall
  • Orchestration & management
  • Expert Services
  • All
  • All
  • Account Management
  • SAAS Management
  • SAAS Application Security
  • Managed Services
  • Platform as a service (PAAS)
  • Other SAAS Services
    • 4D Resources
    Solution Hubs
  • 4D Pillars
  • Cloud
  • Popular Solutions

    • FortiGate-7000F Handbook

    Home FortiGate-7000 6.4.10 FortiGate-7000F Handbook
    6.4.10
    7.0.16
    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.2.16
    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

    Session failover

    Session failover

    FortiGate-7000F session synchronization involves the primary FortiGate-7000F informing the secondary FortiGate-7000F of changes to the primary FortiGate-7000F connection and state tables, keeping the secondary FortiGate-7000F up-to-date with the traffic currently being processed by the cluster.

    Session synchronization traffic uses the M1 and M2 interfaces. FortiGate-7000F does not support using the session-sync-dev option to use data interfaces for session synchronization. The M1 and M2 interfaces provide enough bandwidth for both HA heartbeat and session synchronization traffic, so additional session synchronization devices are not required. As well, keeping session synchronization traffic on the M1 and M2 interfaces separates session synchronization traffic from data traffic.

    After an HA failover, because of session synchronization the new primary FortiGate-7000F recognizes open sessions that were being handled by the cluster. The sessions continue to be processed by the new primary FortiGate-7000F and are handled according to their last known state.

    Previous
    Next

    Session failover

    Session failover

    FortiGate-7000F session synchronization involves the primary FortiGate-7000F informing the secondary FortiGate-7000F of changes to the primary FortiGate-7000F connection and state tables, keeping the secondary FortiGate-7000F up-to-date with the traffic currently being processed by the cluster.

    Session synchronization traffic uses the M1 and M2 interfaces. FortiGate-7000F does not support using the session-sync-dev option to use data interfaces for session synchronization. The M1 and M2 interfaces provide enough bandwidth for both HA heartbeat and session synchronization traffic, so additional session synchronization devices are not required. As well, keeping session synchronization traffic on the M1 and M2 interfaces separates session synchronization traffic from data traffic.

    After an HA failover, because of session synchronization the new primary FortiGate-7000F recognizes open sessions that were being handled by the cluster. The sessions continue to be processed by the new primary FortiGate-7000F and are handled according to their last known state.

    Previous
    Next