UCF / Meraki - No events are coming through

Products

• Network Observability
• Virtual Network Assurance

Issue/Introduction

You observe that no events are coming through for Meraki devices in the Universal Connector Framework (UCF) ․ Only device alarms from the inventory pull appear ․ The Meraki portal shows minimal API calls used only for inventory ․​​​​‌​‍

 

SYMPTOMS:

• Meraki devices only show device alarms from inventory pulls

• Meraki portal API usage section shows minimal calls (10-15)

• No events pull through UCF configuration

Cause

Engineering designed the plugin to require webhooks for event reception ․ This architecture reduces the number of API requests and the load on the Meraki rate limiter, which decreases overall polling time ․

 

KNOWN LIMITATIONS:

• Standard event polling is disabled by design to protect rate limits

Resolution

ENABLE WEBHOOKS

Configure webhooks in the Meraki portal ․

 

EXPECTED: Events begin to flow to DX NetOps Classic ․
NOTE: The UCF plugin requires webhooks to receive events; it does not pull events natively ․

Additional Information

UCF 25.4.4 includes support for Meraki webhooks.

 

When vnaMerakiPlugin.enable: true in netops-config.yaml, a webhook receiver is enabled under the http://<node>:30002/MerakiHook endpoint

 

To receive events from Meraki via webhook, you must expose the HTTP endpoint above to Meraki using a reverse proxy (RP) with a public SSL certificate.

 

Note: The certificate on the RP must meet Meraki's requirements and be signed by a globally trusted certificate authority (CA)

 

The RP must terminate the HTTPS request and forward the event payload of the webhook to the http://<node>:30002/MerakiHook endpoint of the UCF cluster

Note: By default, Meraki sharedSecret validation is disabled in the webhook receiver.