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-6000 Release Notes

    Home FortiGate-6000 6.4.15 FortiGate-6000 Release Notes
    6.4.15
    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.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.10
    5.4.9

    Known issues

    Known issues

    The following issues have been identified in FortiGate-6000 and FortiGate-7000 FortiOS 6.4.15 Build 1940. For inquires about a particular bug, please contact Customer Service & Support. The Known issues described in the FortiOS 6.4.15 release notes also apply to FortiGate-6000 and 7000 FortiOS 6.4.15 Build 1940.

    Bug ID

    Description

    653092

    You cannot use the SLBC management interface IP address to manage a FortiGate-6000 or 7000 by connecting to a data interface.

    724543

    Outbound bandwidth traffic statistics are showing incorrectly on individual FIM and FPM GUI pages.

    765407

    Management interfaces on the secondary FIM in a FortiGate-7000F cannot be used for the FGSP heartbeat.
    767742 Because of a limitation of the FIM-7921F switch hardware, the FortiGate 7121F with FIM-7921Fs does not support adding VLANs to flow rules. The vlan setting of the config load-balance flow-rule command is ignored.

    778239

    For all FortiGate-6000 and 7000 models, the CLI allows you to add up to 512 flow rules. However, the number of flow rules that you can add is actually limited by the FortiGate-6000 and 7000 internal switch hardware:

    • All FortiGate-6000F models support up to 256 flow rules.

    • All FortiGate-7000E models support up to 512 flow-rules.

    • A FortiGate-7000F with FIM-7941Fs supports up to 492 flow rules.

    • A FortiGate-7000F with FIM-7921Fs supports up to 52 flow rules.
    782095 FortiGate-6000 FGCP cluster interfaces may be assigned virtual MAC addresses that overlap with the virtual MAC addresses assigned to the interfaces of other FortiGates in FGCP clusters, even if they have different group IDs. If you have a FortiGate-6000 FGCP cluster on the same network as FGCP clusters with other FortiGates, you can work around this issue by setting the group IDs of other FortiGate clusters on the same network to a value of 81 or higher.
    782978 If you attempt to create an FGCP HA cluster and the FortiGate-6000s or 7000s making up the cluster have difference firmware versions, the CLI of one of the FortiGate-6000s or 7000s may display incorrect error messages after restarting.

    825029

    From the FortiGate-6000 or 7000 GUI or CLI you can only run a policy lookup if the FortiGate-6000 or 7000 has a route to the destination and a properly configured firewall policy that allows traffic to the destination. Normally policy lookup operations only require a route to the destination.

    854819

    FGSP auto session synchronization randomly fails for some FPCs and FPMs when the MTU of the FGSP session synchronization data interface is set to maximum value of 9216 bytes. FGSP auto session synchronization occurs after an FPC or FPM or a FortiGate-6000 or 7000 in an FGSP cluster restarts. The workaround to this problem is to decrease the MTU of the data interface to 9200 bytes or less.

    917382

    An error message similar to 118:socket_vf:[300] ERROR vf < 0: -1 may appear on the FortiGate-7000E console during a firmware upgrade. The firmware upgrade works as expected and operation of the FortiGate-7000E after the upgrade is not affected.

    919606

    During a FortiGate-7000F firmware upgrade FPM CLI consoles may display messages similar to the following:

    [ha_shm_mutex_enter:2781] fgtAttachShm() failed.

    [update_ha_mac:3497] ha_shm_mutex_enter() failed.

    These messages are caused by timing issues as the FPMs are starting up. Once the FPMs have started they should operate normally.

    927737

    On the FortiGate-7000F, ICMPv6 packet fragments received by an EMAC VLAN interface are load balanced to the wrong FIM.

    928653

    Session count information displayed on GUI dashboard widgets does not match session count information displayed from the CLI using the diagnose sys session full-stat command.
    Previous
    Next

    Known issues

    Known issues

    The following issues have been identified in FortiGate-6000 and FortiGate-7000 FortiOS 6.4.15 Build 1940. For inquires about a particular bug, please contact Customer Service & Support. The Known issues described in the FortiOS 6.4.15 release notes also apply to FortiGate-6000 and 7000 FortiOS 6.4.15 Build 1940.

    Bug ID

    Description

    653092

    You cannot use the SLBC management interface IP address to manage a FortiGate-6000 or 7000 by connecting to a data interface.

    724543

    Outbound bandwidth traffic statistics are showing incorrectly on individual FIM and FPM GUI pages.

    765407

    Management interfaces on the secondary FIM in a FortiGate-7000F cannot be used for the FGSP heartbeat.
    767742 Because of a limitation of the FIM-7921F switch hardware, the FortiGate 7121F with FIM-7921Fs does not support adding VLANs to flow rules. The vlan setting of the config load-balance flow-rule command is ignored.

    778239

    For all FortiGate-6000 and 7000 models, the CLI allows you to add up to 512 flow rules. However, the number of flow rules that you can add is actually limited by the FortiGate-6000 and 7000 internal switch hardware:

    • All FortiGate-6000F models support up to 256 flow rules.

    • All FortiGate-7000E models support up to 512 flow-rules.

    • A FortiGate-7000F with FIM-7941Fs supports up to 492 flow rules.

    • A FortiGate-7000F with FIM-7921Fs supports up to 52 flow rules.
    782095 FortiGate-6000 FGCP cluster interfaces may be assigned virtual MAC addresses that overlap with the virtual MAC addresses assigned to the interfaces of other FortiGates in FGCP clusters, even if they have different group IDs. If you have a FortiGate-6000 FGCP cluster on the same network as FGCP clusters with other FortiGates, you can work around this issue by setting the group IDs of other FortiGate clusters on the same network to a value of 81 or higher.
    782978 If you attempt to create an FGCP HA cluster and the FortiGate-6000s or 7000s making up the cluster have difference firmware versions, the CLI of one of the FortiGate-6000s or 7000s may display incorrect error messages after restarting.

    825029

    From the FortiGate-6000 or 7000 GUI or CLI you can only run a policy lookup if the FortiGate-6000 or 7000 has a route to the destination and a properly configured firewall policy that allows traffic to the destination. Normally policy lookup operations only require a route to the destination.

    854819

    FGSP auto session synchronization randomly fails for some FPCs and FPMs when the MTU of the FGSP session synchronization data interface is set to maximum value of 9216 bytes. FGSP auto session synchronization occurs after an FPC or FPM or a FortiGate-6000 or 7000 in an FGSP cluster restarts. The workaround to this problem is to decrease the MTU of the data interface to 9200 bytes or less.

    917382

    An error message similar to 118:socket_vf:[300] ERROR vf < 0: -1 may appear on the FortiGate-7000E console during a firmware upgrade. The firmware upgrade works as expected and operation of the FortiGate-7000E after the upgrade is not affected.

    919606

    During a FortiGate-7000F firmware upgrade FPM CLI consoles may display messages similar to the following:

    [ha_shm_mutex_enter:2781] fgtAttachShm() failed.

    [update_ha_mac:3497] ha_shm_mutex_enter() failed.

    These messages are caused by timing issues as the FPMs are starting up. Once the FPMs have started they should operate normally.

    927737

    On the FortiGate-7000F, ICMPv6 packet fragments received by an EMAC VLAN interface are load balanced to the wrong FIM.

    928653

    Session count information displayed on GUI dashboard widgets does not match session count information displayed from the CLI using the diagnose sys session full-stat command.
    Previous
    Next