Description This article describes expected split-brain behavior when
additional VDOMs are configured in a cluster with inconsistent VDOM
licensing. While the issue is occurring, the following debug output is
visible in hatalk: 'HA cannot be formed b...
Description This article demonstrates a simple FortiGate Cloud
Organizations deployment. Scope FortiGate Cloud 24.3 and later. Solution
FortiGate Cloud supports the FortiCloud Organizations feature by
assigning FortiGate assets to Member Accounts and...
Description This article describes available speed configuration options
for numbered ports in FortiGate 90/91G and 120/12G in different firmware
versions. Scope FortiGate v7.2. Solution In v7.2.11, v7.4.7, and
earlier, FortiGate-90G/91G and 120G/121...
Description This article describes a repetitive error log that can occur
when advanced content processing acceleration is enabled, and how to
disable it. Scope FortiGate with SOC4 hardware such as 40F, 60F, 100F
and IPSA enabled. Solution This may ma...
Description This article provides an example of SSH session logging when
using Linux or MacOS to connect to FortiGate. Scope FortiGate. Solution
To connect to FortiGate as an SSH server while also logging output to a
file, open a Linux or MacOS comma...
Sometimes, useful info you can only find in one place is wrong! v7.2.11
was released yesterday and v7.0.17->v7.2.11->v7.4.7 is a supported
upgrade path despite breaking the rule of thumb I just gave (v7.2.11
released 2025-02-12, v7.4.7 released 2025-...
It's not because v7.0.17 was new, upgrade from chronologically later
(v7.0.17) releases to chronologically earlier (v7.2.10) releases is not
supported. That's because those upgrade steps are not QA-tested. Upgrade
v7.0.17->v7.2.10 or earlier should b...
Not monitoring this post, but dropping "word of TAC" here in since I'm
seeing it's unclear.This February 28 2025 FortiGate Cloud change applies
for devices without a FortiGate Cloud subscription, either per-device or
at the account level. It is diffe...
Hi Toshi,I can believe it. The Change Log has since been updated again
and CVE-2024-47575 is referenced in Resolved Issues.As you've noticed,
not all Known or Resolved Issues appear immediately in Release Notes.
Some never appear. For urgent releases...
