Hello,We have an HA pair of FortiGate VM04s in our Azure development
environment that we are using to test for a redesign. The FortiGates
were built with the "ELB/ILB Sandwich", as Azure/Fortinet documentation
outlines. We also have a GLB placed in f...
On our FortiGate running 7.2.8, we received the message with a link to
this 9.1 CVE: https://www.fortiguard.com/psirt/FG-IR-25-647However I do
see an additional 7.4 CVE released just 3 days ago, which aligns better
with when the message first showed ...
Do you have a health check configured and applied to your SD-WAN rules?
If a health check is not configured, the SD-WAN rule will not fail over
to the next member unless the WAN interface itself is physically or
administratively down.For more info, s...
This is related to a known vulnerability specifically related to
FortiCloud SSO admin login to FortiGate. As long as you have FortiCloud
SSO login disabled in system settings you are fine to ignore the
message.
Unfortunately this is what I'm seeing as well. The only reference to a
set neighbor-group is within config neighbor range. After checking the
CLI reference, it does look like you'd be forced to create a unique
neighbor-range for each /32 peer.
