Monitor Juniper Mist wireless infrastructure
Add Juniper Mist orchestrator nodes for monitoring access points, interfaces, rogue access points, and clients for the wireless controller.
What does NPM monitor for Juniper Mist infrastructure?
Monitored entity | Metrics |
---|---|
Controller |
|
Access Point |
|
Interface |
|
Client |
|
Rogue Access Point |
|
Requirements
You need your the following details for monitoring Juniper Mist infrastructure:
- Juniper Mist Hostname, such as
api.ac2.mist.com
. See API Endpoints and Global Regions for Mist Juniper Networks. - Authentication data for the used authentication method:
- API token and Organization ID. See Find your Organization ID for Mist Juniper Networks.
- Username, password, and Organization ID. See Find your Organization ID for Mist Juniper Networks.
- Site: Select from a list of detected items
Limitations
-
The status poller uses API authorization requests to determine whether a node is responsive. API calls can take more time, and as a result, response time thresholds are exceeded. The nodes might appear to be exceeding the warning or critical status without showing any signs of connectivity problems (0% packet loss). Consider adjusting the response time thresholds for the nodes to better represent the average response times.
-
Poll Now is not supported.
-
Discovery is not supported. Add nodes using the Add Node wizard.
API calls used for polling wireless access points
API request | Purpose | |
---|---|---|
1 | \api\v1\self | Authentication via token, status polling |
2 | \api\v1\login | Authentication via username and password. |
3 | \api\v1\orgs\<OrgID>\sites | Get Site List in the Add/Edit Node wizard. |
4 | \api\v1\sites\<SiteID>\stats\devices\ | Statistics collection poller - gets information on APs and wireless interfaces. |
5 | \api\v1\sites\<SiteID>\stats\clients | Statistics collection poller - gets information on clients. |
6 | \api\v1\sites\<SiteID>\insights\rogues | Statistics collection poller - gets information on rogue APs. |
Before you begin
Prepare your Juniper Mist customer and client details. See Requirements.
Add Juniper Mist wireless infrastructure to NPM
-
Log in to the SolarWinds Platform Web Console as an administrator.
-
Click Settings > Manage Nodes and click Add a Node.
-
Provide the Juniper Mist hostname. See Requirements.
-
In Polling Method, select Orchestrators: API.
-
Select Juniper Mist Devices, select the authentication method, and provide the details.
API Token:
- API Token
- Organization ID
Username & Password:
- E-mail:
- Password:
- Organization ID
-
Click Get Site List and select the site to monitor.
Polling Juniper Mist devices uses the global HTTP proxy settings. To change the defaults, click the Configure your HTTP proxy link.
-
Review and adjust the device properties.
-
Review your Juniper Mist details and proxy settings.
-
To edit how often the node status, or monitored statistics are updated, change the values in the Polling area.
-
Enter values for custom properties for the node.
The Custom Properties area is empty if you have not defined any custom properties for the monitored nodes. See "Add custom properties to nodes" in the SolarWinds Platform Administrator Guide.
-
To adjust when the status of the node changes to Warning or Critical, edit alerting thresholds for the metric. Select the Override box and set thresholds for the node.
The status poller uses API calls with authentication. This can take longer than if the default ICMP polling was used. Consider adjusting the response time thresholds for the nodes to better represent the average response times.
-
-
Click OK, Add Node.
The Juniper Mist device is now added as a node. After the first poll, you can see the data from the device in the SolarWinds Platform Web Console.
On the Manage Nodes view, click the added node to see the node details in the Wireless Controller view, or drill down into thin access points listed on the view. Check Node Details to verify that the Machine Type of the new device is Juniper Mist Orchestrator.