Overview
This article covers common issues encountered when connecting or maintaining NetOp integrations with network vendors (Meraki, Fortinet, Palo Alto, SNMP, etc.).
Integration Status Indicators
In Integrations → Datasources, each integration row shows:
| Column | Meaning |
|---|---|
| Status | Active / Error / Disabled |
| Last Access | Timestamp of last successful API call |
| Devices | Count of discovered devices |
| Enabled | Whether the integration is currently active |
Common Issues and Solutions
Authentication Failed
Symptoms: Status shows Error; Last Access timestamp is stale.
Causes and Fixes:
| Cause | Fix |
|---|---|
| API token expired or revoked | Regenerate the token in the vendor dashboard; update it in NetOp Integrations |
| Wrong token entered | Re-enter the token carefully; tokens are case-sensitive |
| Token missing required permissions | Ensure the API user has read-only admin access to all organizations |
| Wrong region selected (Meraki) | Verify your Meraki dashboard region matches the selection in NetOp |
No Sites Appear After Adding Integration
Steps to resolve:
- Confirm authentication is successful (no error status)
- Click Update Tenant List to refresh the list of available tenants
- Check the New Tenants column — all discoverable tenants appear here
- Select the tenants you want to monitor and click Save
- Wait 5–10 minutes for initial discovery to complete
Devices Missing from a Site
Causes and Fixes:
| Cause | Fix |
|---|---|
| Device added after initial sync | Run Sync Now from Operations |
| Device in wrong site | Reassign via Settings → Site Management |
| Device not supported by the integration | Check NetOp's supported device list for the vendor |
| SNMP agent cannot reach the device | Verify network access and community string |
Meraki Multi-Tenant Token Issues
For Meraki, a single API token can manage multiple organizations. Ensure:
- The Meraki admin user who created the token is added to all Meraki organizations you want to monitor
- The token has Dashboard API access enabled in Meraki
Fortinet / Palo Alto
- Ensure the API user has Read-Only Administrator permissions
- Verify the FortiManager/Panorama URL is reachable from the NetOp platform (no firewall blocking outbound HTTPS)
- For Palo Alto, confirm the API key is generated from the correct admin account
Editing an Existing Integration
- Go to Integrations → Datasources
- Click the integration row you want to edit
- Modify the token, URL, or region
- Click Save
Still Not Working?
If the issue persists after following the steps above, contact NetOp support with:
- The integration type and vendor
- The error message or status shown in NetOp
- The Last Access timestamp
- Whether the issue affects all tenants or specific ones
Comments
0 comments
Please sign in to leave a comment.