VNA self-monitoring module incorrectly displays Meraki module in Spectrum
search cancel

VNA self-monitoring module incorrectly displays Meraki module in Spectrum

book

Article ID: 429140

calendar_today

Updated On:

Products

Network Observability Virtual Network Assurance Spectrum

Issue/Introduction

When you add a Virtual Network Assurance (VNA) self-monitoring module for a Fortinet plugin in Spectrum, the system incorrectly displays the Meraki VNA module instead ․․․․

 

SYMPTOMS:

VNA self-monitoring for Fortinet shows as Meraki VNA module 
Inventory discrepancy exists where self-monitoring for the VNA is missing in Performance Center (PC) 

Potential ID identifier conflict within the Spectrum integration 

CONTEXT: This occurs when integrating multiple VNA plugins (e.g․, Fortinet and Meraki) on different VNA instances into the same Spectrum environment 

Environment

Product: DX NetOps Spectrum 

VNA Plugins: Fortinet, Meraki 

Product Release: 25․4․4

Resolution

1. DISCONNECT INTEGRATION: Separate the VNA integration from Spectrum 

2. RE-ADD INTEGRATION: Re-add the VNA integration to Spectrum after a period of separation 

3. RESTART SERVICES: Restart the VNA and Performance Center (PC) services to clear cached identifiers 

EXPECTED: The correct self-monitoring domain should appear for the specific VNA plugin