SD-WAN Fortinet Troubleshooting Guide
This document provides a useful troubleshooting scenario for SD-WAN Fortinet Collector.
Troubleshooting
Device or Orchestrator populated with Partial Object synchronization
If the Device Onboarding process is not functioning, check the spk import status in the MySQL database.
- Navigate to SevOne NMS container.
nms - Execute the command to perform database
validation.
mysqlconfig - Execute the SQL command.
SELECT vendor, spk_file_name, CAST(processed_status AS INT) AS processed_status, CAST(active AS INT) AS active_int, processed_at FROM net.spk_data WHERE vendor = 'Fortinet'; - Verify the import status for the .spk files.
Example
+----------+----------------------------------------------+------------------+------------+---------------------+ | vendor | spk_file_name | processed_status | active_int | processed_at | +----------+----------------------------------------------+------------------+------------+---------------------+ | Fortinet | Fortigate_Alerts_v1-1_v1.0.0.spk | 1 | 1 | 2025-05-13 11:52:23 | | Fortinet | Fortigate_Certification_v1.0.0.spk | 1 | 1 | 2025-05-13 11:52:22 | | Fortinet | Fortigate_Interface_SubType_Rules_v1.0.0.spk | 1 | 1 | 2025-05-13 11:52:22 | | Fortinet | Fortigate_MIBs_v1.0.0.spk | 1 | 1 | 2025-05-13 11:52:14 | | Fortinet | Fortigate_ObjectGroups_v1.0.0.spk | 1 | 1 | 2025-05-13 11:52:22 | | Fortinet | Fortigate_TopN_v1.0.0.spk | 1 | 1 | 2025-05-13 11:52:30 | +----------+----------------------------------------------+------------------+------------+---------------------+ 6 rows in set (0.001 sec)Note: The processed_status should be set to 1, and the processed_at field should record the UTC timestamp when the device was first discovered.Note: For Fortigate_* .spk files where processed_at is 0 or null, manually import them using the following command.cd /config/sdwan/Fortinet SevOne-import --allow-overwrite --file <spk_name>