202102 - External Feed Name Not Found on Target FortiGates
Agent error code #202102 indicates that the agent pushed a dynamic entry update to the target FortiGates, but the specified external feed name does not match any external resource configured on those FortiGates. The FortiGate(s) returned an error indicating the feed name was not recognised. This error applies to Passive+ mode (both FortiManager and direct FortiGate variants).
This error is distinct from target device issues (#202101). Error #202102 means the target device was reached successfully, but the external resource name does not exist on it.
Common causes include:
- The External Feed Name in Knocknoc does not match the external resource name configured on the FortiGates
- The external resource was renamed or deleted on the FortiGate
- The external resource was configured on some FortiGates but not all targets (FortiManager mode)
- A typo or case mismatch between the name in Knocknoc and the name on the FortiGate
Steps to Resolve
Verify the External Feed Name
- In the Knocknoc admin interface, check the External Feed Name configured for the ACL
- On the target FortiGate(s), navigate to Security Fabric > External Connectors (or System > External Resource on older firmware)
- Confirm an external resource exists with the exact same name — names are case-sensitive
- If the names do not match, update either the Knocknoc configuration or the FortiGate external resource name
Verify via CLI (FortiGate)
- SSH into the FortiGate and run:
diagnose system external-resource list - This lists all configured external resources and their names
- Verify the name matches what is configured in Knocknoc
Verify All Target FortiGates (FortiManager Mode)
- If using Passive+ (FortiManager) mode with multiple target devices, the external resource must exist on every target FortiGate
- If the resource was deployed via FortiManager policy push, verify the push completed successfully on all devices
- If some FortiGates are missing the resource, redeploy the policy or configure the resource manually
Still Having Issues?
We can help you out, contact us at support@knocknoc.io.