Preventing Duplicate or Conflicting FortiSwitch Data in Auvik (Ping Discovery vs FortiGate API)

Introduction

When monitoring FortiSwitches in Auvik, data can be collected through:

• Device discovery via ping (ICMP) and subsequent polling
• The FortiGate API (for switches managed via FortiLink)

Using both methods simultaneously can introduce duplicate devices, inconsistent topology, and conflicting device data. This article explains how to resolve these issues by standardizing your monitoring approach.

Problem

If both ping-based discovery and FortiGate API monitoring are enabled:

• Auvik may discover the same FortiSwitch more than once
• Device attributes (hostname, IP, interfaces) may not match
• Network topology may appear inconsistent
• Downstream devices may attach to different parent devices

This occurs because Auvik is ingesting two independent data sources describing the same infrastructure.

Recommended Approach

Use the FortiGate API as the authoritative data source for FortiSwitches and restrict direct discovery of those switches.

This ensures:

• A single source of truth
• Consistent device identification
• Stable topology mapping

Configuration Steps

Step 1: Exclude FortiSwitches from Discovery

1. In Auvik, go to Discovery > Manage Networks
2. Locate the IP ranges or specific IPs used by FortiSwitches
3. Add these to the exclusion list
4. Save changes

This prevents Auvik from discovering and polling the switches directly.

Step 2: Verify FortiGate API Integration

Ensure your FortiGate integration is functioning:

• API credentials are configured
• Connection tests succeed
• Device data is being populated in Auvik

(Refer to existing FortiGate/FortiSwitch API setup documentation if needed.)

When to Apply This Configuration

Use this approach when:

• FortiSwitches are managed via FortiLink
• Duplicate or mismatched devices appear in Auvik
• Topology inconsistencies are observed
• Stability and consistency are prioritized

Alternative Approach

You may choose to:

• Disable FortiGate API monitoring
• Use discovery and polling only

However, this is generally less effective in FortiLink environments and may reduce visibility into controller-managed relationships.

Summary

Running both direct discovery and FortiGate API monitoring for FortiSwitches can lead to duplicate and conflicting data in Auvik. By excluding switches from discovery and relying on the FortiGate API, you create a cleaner, more reliable network model with fewer inconsistencies.