Description | This article provides steps to perform troubleshooting when CMDB add entry failed error shows up. |
Scope | FortiGate |
Solution |
Whenever the alerts related to CMDB are visible, add entry failed, it is most likely due to the wrong upgrade path followed.
It is always recommended to follow the upgrade path according to the upgrade path tool:
https://docs.fortinet.com/upgrade-tool
When user looks into the CLI by running this command:
# diag sys flash list
Two boot partitions will be visible inside the grub configuration: active and backup
It is to be observed that the primary boot partition should have the current firmware version loaded, if not, that means your image got corrupted.
Here is the solution to remedy this:
1). First, you can try killing the cmdb process, in order to do that,
# get sys cmdb status
# diag sys kill 11 <PID>
2). If still the issue is not resolved then you need to do the flash format of your firewall by using this kb link: https://community.fortinet.com/t5/FortiGate/Technical-Tip-FortiGate-Flash-Format-process/ta-p/198704...
3). Later, you need to be ready with the TFTP server, load the firmware image on TFTP, and then to FortiGate device via TFTP server.
This will help you resolve the issue, if the issue still persists, please open the TAC ticket.
|
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.