FortiSwitches Not Visible After Fortinet API Setup: Root‑Cause Guide

Overview

If FortiSwitches are not appearing in Auvik after configuring the Fortinet API integration, the issue is typically related to FortiLink visibility, API permissions, integration scope, device reachability, or unsupported API exposure for the FortiOS version in use.

This guide outlines the most common causes and the recommended troubleshooting steps.

Symptoms

You may observe one or more of the following:

• FortiGate API credentials test successfully in Auvik
• FortiGate devices appear normally
• Managed FortiSwitches do not appear in device inventory or topology
• Only partial switch information is displayed
• Discovery completes without errors, but switches remain missing

Cause

FortiSwitch visibility through the Fortinet API depends on multiple conditions being met:

• The switches must be managed through FortiLink
• The FortiGate must expose switch data through the API
• The API user must have sufficient permissions
• The Auvik integration must be configured for the correct site and organization
• The collector must be able to reach required management interfaces

If any of these requirements are not met, Auvik may not discover or display the switches.

Resolution

Step 1 - Verify FortiSwitches Are Managed by FortiLink

Log into the FortiGate GUI and confirm the switches appear under:

WiFi & Switch Controller → Managed FortiSwitch

Verify:

• The switches are online
• The switches are authorized
• FortiLink management is active
• The expected switch inventory is visible in FortiGate

If the switches are not visible in FortiGate, Auvik cannot retrieve them through the Fortinet API.

Step 2 - Verify API User Permissions

The REST API administrator account used by Auvik must have sufficient permissions to read switch information.

Review the associated admin profile and ensure the following permissions are enabled:

After updating permissions:

1. Save the profile
2. Re-test the API credentials in Auvik
3. Force rediscovery

Step 3 - Verify the Integration Is Configured for the Correct Site

In Auvik:

1. Navigate to Discovery → Manage Credentials
2. Open the Fortinet API credentials
3. Confirm the credentials are associated with the correct:
   • Organization
   • Site
   • FortiGate device

Incorrect site assignment can result in successful API authentication while preventing discovered devices from appearing in the expected inventory.

Step 4 - Confirm the FortiOS Version Exposes Switch Data Through API

Some FortiOS versions may not fully expose FortiSwitch inventory or telemetry through the REST API.

If switch data is unavailable through the API:

1. Enable SNMP directly on the FortiSwitches
2. Add SNMP credentials to Auvik
3. Allow the collector to poll the switches directly

This provides an alternative discovery method when API-based switch visibility is limited.

For SNMP configuration guidance, see the Fortinet and Auvik documentation appropriate for your FortiOS and FortiSwitch versions.

Step 5 - Verify Collector Connectivity to Management IPs

Ensure the Auvik collector can reach the management interfaces used by the FortiSwitches.

Verify:

• Routing exists between the collector and switch management VLANs
• Firewall policies permit SNMP, ICMP, and management traffic
• No ACLs are blocking collector access
• NAT or VPN configurations are not preventing reachability

Additional Recommendations

To improve FortiSwitch monitoring reliability:

• Use the FortiGate API as the primary source of truth for FortiLink-managed switches
• Avoid duplicate monitoring methods where possible
• Keep FortiOS and FortiSwitch firmware versions current
• Ensure the collector has stable Layer 3 reachability to management interfaces
• Validate API functionality after firmware upgrades

Related Articles

• How do I monitor a FortiSwitch in FortiLink mode?
• Troubleshooting Fortinet device API credentials
• Preventing Duplicate or Conflicting FortiSwitch Data in Auvik (Ping Discovery vs FortiGate API)