Network Management

Juniper Mist API node goes down soon after being added in SolarWinds Platform 2024.4

This article explains how to resolve an issue where nodes polled via the Juniper Mist Orchestrator API go down soon after being added, even though other data about the node is polled correctly.

First published date

1/15/2025 11:32 AM

Last published date

2/23/2025 6:35 PM

Overview

After adding a new node polled via the Juniper Mist Orchestrator API, the node goes into Down status, even though the node is up, and other data about the node displays as expected. 

The following log file contains an error relating to a missing '$..email' value:

C:\ProgramData\SolarWinds\Logs\Orion\Wireless\Declarative\Wireless.Declarative.PollersJobs_[#####].log

ERROR SolarWinds.Orion.Declarative.Pollers.Polling.DeclarativeRestPoller - job failed
SolarWinds.Orion.Declarative.Contract.Exceptions.MapPropertyException: Failed to pick source values from Path: '$..email'

Product section

Network Performance Monitor

Cause

The SolarWinds Juniper Mist API status poller makes an API request to \api\v1\self to check the up/down status.

The API response must include an "email" value; otherwise, the status poll will fail.

If the Juniper Mist API token is created under the Organization, the response does not include an associated email address.

Resolution

To resolve this issue, please upgrade to SolarWinds Platform 2025.1 and above.  If upgrade is not possible, perform the steps below to workaround the issue:

Create the API token under a user account so that the response includes an "email" value.