Juniper Mist monitoring
Site24x7's Juniper Mist monitoring gives you complete visibility into your Mist cloud-managed network from a single console. Once you connect your Mist account, Site24x7 automatically discovers your organizations, access points, switches, and WAN edges; tracks their availability and performance; and alerts you the moment a device goes down or a metric breaches its threshold—so you can resolve network issues before your end users notice them.
Use cases
- Monitor distributed wireless networks across branch offices, campuses, and retail sites without deploying an agent or probe at each location.
- Track Wi-Fi user experience with Mist service-level expectation (SLE) scores for coverage, roaming, capacity, throughput, and successful connects, and fix problem areas before complaints roll in.
- Keep SD-WAN links healthy by watching WAN edge high-availability (HA) cluster states; Mist tunnel statuses; and BGP, OSPF, and VPN peer states.
- Spot configuration drift early with Config Status, Config Version, and Config Reverted attributes polled from the Mist cloud.
Benefits
- Single console for wireless, wired, and WAN: View your entire Mist estate alongside your servers, applications, and other network devices in Site24x7.
- Zero-touch discovery: Connect once with an API token; Site24x7 discovers your organizations and their devices and keeps the inventory current.
- Faster troubleshooting: An interactive topology map, events timeline, and per-device dashboards help you isolate the faulty layer in minutes.
- Proactive alerting: Threshold-based alerts through your preferred notification channels reduce your mean time to repair (MTTR).
Prerequisites
- An active Juniper Mist account with at least one organization.
- A Mist API token with read access to the organizations you'd like to monitor.
- The Mist cloud region URL that hosts your organization (for example, api.mist.com).
Setup and tab descriptions
To start monitoring, add a Juniper Mist monitor from Network > Juniper MIST in the Site24x7 web client.
Once discovery is complete, the Juniper Mist monitor displays the following tabs:
| Tab | Description |
|---|---|
| Summary | Displays the monitor's availability, downtime, events timeline, response time, and device details such as the Mist Cloud Region URL and Account Name. |
| Topology | Maps your organizations and the devices under them, color-coded by status. |
| Organizations | Lists the discovered organizations with their name, ID, and status. |
| Access Points | Lists the discovered access points with their status, name, serial number, and model. |
| Switches | Lists the discovered switches with their status, name, serial number, and model. |
| WAN Edges | Lists the discovered WAN edges with their status, name, serial number, and model. |
| Outages | Lists the outage history of the monitor. |
| Notes | Displays the comments added to the monitor. |
| Log Report | Provides the polling log of the monitor. |
| Alert Logs | Lists the alerts raised for the monitor. |
Click any organization or device to drill down into its dedicated dashboard. To learn about the metrics collected for each device type, see Juniper Mist performance metrics.
Best practices
- Use a dedicated, read-only API token for Site24x7 so monitoring access can be rotated or revoked independently of admin credentials.
- Group monitors by organization or site using tags and monitor groups to simplify alerting and reporting.
- Set threshold profiles for critical metrics—such as CPU Utilization, Memory Utilization, SLE scores, and Mist Tunnels Down—based on your baseline values.
- Watch the Certificate Expiry attribute on switches and WAN edges to renew device certificates before they lapse.
- Schedule maintenance windows for planned firmware upgrades to avoid false alerts.
Troubleshooting
| Issue | Probable cause | Resolution |
|---|---|---|
| The monitor is in the Configuration Error state. | The API token is invalid, expired, or revoked. | Generate a new API token in the Mist portal and update it in the monitor's edit page. |
| Organizations or devices are not discovered. | The API token doesn't have access to the organization, or the wrong Mist cloud region URL was provided. | Verify that the token has read access to the organization and that the region URL matches the one in your Mist portal. |
| A device shows as Down in Site24x7 but appears connected in the Mist portal. | The device dropped and reconnected between polls, or the last poll failed. | Check the Log Report tab for the latest poll status and compare the Last Seen timestamp with the Mist portal. |
| Metric charts show no data for a device. | The device was recently discovered and hasn't completed a full poll cycle. | Wait for the next poll, then refresh the device's dashboard. |