Technical Tip: Automating migration of SD-WAN conf...

dkoprusak · 09-27-2024

Description This article describes how to get more information and provides the solution for a successful ADOM upgrade if such an issue occurs. During an ADOM upgrade, it is possible to encounter the error 'Fail(errno=-2):Invalid FQDN'. Scope FortiMa...

dkoprusak · 06-06-2024

Description This article describes that during an ADOM upgrade, it is possible to encounter the error 'Fail(errno=-2): Do not support urlfilter-table for global scope webfilter profile'. This article describes how to get more information and provides...

dkoprusak · 05-06-2024

Description This article describes that the reference between the device object and the actual SSL VPN web portal configuration can break which causes the changes done via the 'VPN Manager' are not reflected as a change in the 'Policy package'. Scope...

dkoprusak · 03-18-2024

Description This article describes the meaning of such an error and how to resolve it. Scope FortiManager. Solution By the current FortiManager design for the FortiGate HA cluster, if the configuration is not identical between the primary and seconda...

dkoprusak · 05-11-2023

Description This article describes how to prepare FortiManager for an upgrade from 6.4 to 7.0, which significantly changes the way configurations work. Scope FortiManager. Solution The upgrade from FortiManager 6.4 to 7.0 introduced SD-WAN configurat...

dkoprusak · 07-20-2022

Hello eliasd, In case you have a standalone firewall with no VDOMs, you can double-check if you have:1) enabled SNMP on FGT interface: https://docs.fortinet.com/document/fortigate/6.4.9/administration-guide/325005/interface-access2) set up SNMPv3 age...

User Statistics

User Activity

Troubleshooting Tip: ADOM upgrade fails with error 'Fail(errno=-2):Invalid FQDN'

Troubleshooting Tip: ADOM upgrade fails with error 'Fail(errno=-2):Do not support urlfilter-table for global scope webfilter profile'

Technical Tip: Configuration change on SSL VPN portal profile via the 'VPN Manager' is not detected as the change to trigger installation

Technical Tip: Unable to push changes due to 'HA configuration is not allowed to be changed in HA mode' error