Technical Tip: Error code: 2 Protocol error while uploading FortiGate configuration managed by FortiManager in Backup mode ADOM

[RMarqeshi]

Description	This article describes a new option in FortiManager to enable FCP service that impacts backup files/Revisions of FortiGate managed by FortiManager in Backup mode ADOM.
Scope	FortiManager v7.2.6, v7.4.4, v7.6.0, and above.
Solution	After the FortiManager upgrade, uploading the FortiGate config file managed by FortiManager in Backup mode ADOM will fail with Error code: 2(Protocol error), as shown below: FG200E-4 (global) # diagnose fdsm cfg-upload test2 Retrieving full config. Error code: 2(Protocol error) FG200E-4 (global) # This happens as a new option has been added to FortiManager to enable or disable FCP service. By default it is disabled. FMG-VM64 # config system global (global)# set fcp-cfg-service  disable    FCP service doesn't process configuration requests from web  enable     FCP service processes configuration requests from web. For FortiGate to be able to upload a Backup file to FortiManager via 'diagnose fdsm cfg-upload test2' or just a simple Autoupdate, option 'fcp-cfg-service' needs to be enabled in FortiManager. After  'fcp-cfg-service' is enabled in FortiManager, then FortiGate uploads the config file: FortiManager CLI: FMG-VM64 # config system global (global)# set fcp-cfg-service enable (global)# end FortiGate CLI: FG200E-4 (global) # diagnose fdsm cfg-upload test2 Retrieving full config. Result=Success FG200E-4 (global) # Note: fcp-cfg-service impacts Automatic Backup in FortiManager with ADOM Backup mode. It needs to be enabled to create new Revisions in FortiManager. Related documents: Technical Tip: How to do bulk retrieve config in FortiManager using a script

[mvlasak]

Very helpful KB