Meraki switches missing interface data in DX NetOps Spectrum/VNA due to pagination failure

Products

• Network Observability

Issue/Introduction

After syncing Meraki devices via the Virtual Network Assurance (VNA) Meraki plugin, multiple switches (e.g., model MS130) appear in DX NetOps Spectrum with zero interfaces or missing port data. VNA logs may show the following warning:

`"Link response header not available"`

Environment

DX NetOps VNA 25.4.x release.

Cause

The Cisco Meraki API recently updated its response headers, changing the pagination key from capitalized "Link" to lowercase "link". The VNA plugin’s pagination logic was strictly case-sensitive, looking only for "Link." As a result, VNA failed to parse the header, causing it to stop data retrieval after the first page (typically the first 50 records), leaving subsequent devices without interface data.

 

Resolution

A permanent fix is scheduled for the DX NetOps 25.4.10 release, which implements case-insensitive header lookups.

Workaround:

To resolve this issue immediately, manually update the `MerakiHttpPagination.groovy` script to support both casing formats:

1.  Locate the script file: `TIM-INF/groovy/scripts/MerakiHttpPagination.groovy`
2.  Find the line that retrieves the link header:
    ```groovy
    def linkHeader = responseHeaderMap.get("Link")
    ```
3.  Modify it to include a fallback for the lowercase header:
    ```groovy
    def linkHeader = responseHeaderMap.get("Link") ?: responseHeaderMap.get("link")
    ```
4.  Save the file and allow VNA to perform a new discovery poll.