---
title: "Juniper Mist"
canonical: "https://docs.infoblox.com/space/UniversalAssetInsights/1919025202/Juniper%20Mist"
format: markdown
---
Juniper Mist is a cloud-native networking platform that uses AI-driven operations (AIOps) to manage and optimize wireless, wired, and WAN environments. Through a centralized cloud service, Juniper Mist provides continuous visibility into network devices, access points, switches, and their operational state, enabling administrators to efficiently manage distributed enterprise networks with improved reliability and user experience.

Integrating Juniper Mist with Universal Asset Insights extends this visibility by continuously discovering and ingesting Mist-managed assets into a unified asset inventory. Devices, interfaces, and associated network attributes discovered from the Juniper Mist platform are correlated with data from other discovery sources, providing a single, authoritative view of assets across campus, branch, and cloud environments. This unified perspective helps ensure asset accuracy, improves cross-system correlation, and strengthens overall asset visibility across the enterprise.

Enabling Juniper Mist discovery provides visibility into your Juniper Mist SD-WAN elements, such as:

- Gateways
- Switches
- Access Points
- Wired Clients
- Wireless Clients
- Sites, maps, and networks used as context for these assets.

Complete the following steps to configure discovery for Juniper Mist:

1. **Provider Type:** Select **Juniper Mist** to indicate that Juniper Mist is the discovery source.
2. **State:** Ensure the state is set to **Enabled** so that the discovery job runs according to the configured synchronization interval.
3. **Name:** Enter a unique and descriptive name to identify the discovery configuration, for example, `Juniper-Mist-Production`.
4. **Description:** (Optional) Provide additional information describing the purpose or scope of this discovery source.
5. **Sync Interval:** Select **Auto** to allow the system to manage the synchronization frequency automatically.
6. **Provider URL:** Enter the Juniper Mist API endpoint URL.  
The default value is `https://api.mist.com`.
7. **Account Preference:** Select **Single** to use one credential set for all discovery operations.
8. **Type of access:** Select **Static Credential** to authenticate using stored credentials.
9. **Credentials:** Select **Existing** to use a previously created credential
10. Alternatively, click **New** to create a new credential for this discovery source and configure the following:
  1. **Name:** Enter a unique and descriptive name to identify the credential.
  2. **Description:** (Optional) Provide additional information describing the purpose or usage of the credential.
  3. **Authentication Type:** Select **API Key** to authenticate with the Juniper Mist platform using token-based access.
  4. **API Key:** Specify the access key required to use Juniper Mist APIs. The Juniper Mist administrator must grant an **API key that provides at least observer-level access.**
  5. **Add Tags:** (Optional) Add tags to the credential to support classification, filtering, and governance.
  6. Click **Save** to save credentials and confirm that it is available for selection in the Credentials list.
11. **Organization ID:** Enter the Juniper Mist **Organization ID** associated with the Mist account.  
This value identifies the organization from which assets are discovered.
12. **Credential Permissions:** Verify that the selected credentials have sufficient permissions in Juniper Mist to access organization, device, and network inventory data.
13. **Discovery Scope:** Review this section and note that, by default, all asset types are included in discovery. Click **Manage** to include or exclude specific asset types from discovery, if required. The **Discovery Scope** defines the boundaries of what data is collected from an integrated provider during the discovery process. It allows administrators to control **which asset types are discovered and ingested** into Universal Asset Insights by selectively including or excluding specific categories of assets. This ensures that discovery is aligned with organizational requirements, reduces unnecessary data ingestion, and improves overall visibility and manageability. Within the Discovery Scope, administrators can configure **Include** or **Exclude** settings for various asset types. When an asset type is **included**, all corresponding data from that category is discovered and ingested. When an asset type is **excluded**, those assets are ignored during discovery. The following assets can be included for discovery:
  - **Organization:** Represents the top-level structure of the provider environment
    - Defines the overall hierarchy and administrative boundary for all discovered assets
  - **Networks:** Defines logical network groupings and configurations
    - Represents network segments, VLANs, or logical groupings
    - May also appear in hierarchical contexts within the discovery model
  - **Sites:** Represents physical or logical locations within the organization
    - Corresponds to branches, campuses, or deployment locations
    - Helps organize assets based on geographic or functional grouping
  - **Devices:** Includes network infrastructure components discovered in the environment
    - Access points
    - Switches
    - Gateways
  - **Wireless Clients:** Represents devices connected over Wi-Fi networks
    - End-user devices such as laptops, mobile phones, and tablets
    - Associated with SSIDs and access points
  - **Wired Clients:** Represents devices connected through physical (wired) network interfaces
    - Devices connected via Ethernet
    - Typically includes desktops, servers, or IoT devices
  - **Maps:** Provides visual representations of network layouts and topology
    - Displays spatial or logical relationships between network elements
    - Helps with visualization and troubleshooting of network environments
14. Ingestion Rules: The **Ingestion Rules** feature enables administrators to control which assets are discovered and ingested into Universal Asset Insights by applying specific filtering criteria. Using the **Add Rules** option, administrators can define rules that evaluate asset attributes and determine whether assets should be included or excluded during the discovery process. The **Include** option acts as a whitelist, allowing only assets that match the defined criteria to be ingested while ignoring all others. In contrast, the **Exclude** option functions as a blacklist, preventing assets that match the specified conditions from being ingested while allowing all other assets to pass through. Asset filters can be defined based on attributes such as **SSID**, which identifies the wireless network to which a device is connected. For example, administrators can include only devices connected to a corporate SSID to ensure that only relevant, managed assets are discovered, or exclude devices connected to guest or unmanaged networks to reduce noise and unnecessary data. By using ingestion rules with SSID-based filtering, organizations can maintain a more accurate and meaningful asset inventory, improve discovery efficiency, and ensure that ingested data aligns with operational and security requirements.
15. **Destinations**: Configure the following settings:
  - **IPAM Discovery**: To discover IPAM objects in Juniper Mist, toggle IPAM Discovery to **Enabled**.
  - **Federated Realm**: Choose **Existing** and select an available Federated Realm from the drop-down. Alternatively, click **New** and create a new Federated Realm. For more information on creating a Federated Realm, see <u>*[Creating a Federated Realm](https://infoblox-docs.atlassian.net/wiki/spaces/BloxOneDDI/pages/684327513)*</u>.
16. **User Defined Tags:** Review whether any tags are already associated with the discovery configuration.
17. **Manage Tags:** Add, edit, or remove tags to support classification, filtering, and governance.
18. Click **Save** to save the discovery configuration.

Go to *[Managed Assets](https://infoblox-docs.atlassian.net/wiki/spaces/BloxOneCloud/pages/1161494602)* to view the assets discovered from Juniper Mist. 

### IPAM / IP Space Behavior

When integrating with **Juniper Mist**, the discovery process automatically creates **IP spaces** in Infoblox to logically organize discovered network assets.

- For **each Mist site**, the system generates a **separate IP space**.
- The IP space follows a consistent naming pattern:  
`<org-name>-<site-name>-<DiscoveryJobName>`

This means that the structure of IP spaces directly reflects the hierarchy and segmentation of sites within the Mist organization.

#### What this means in practice

- If your Mist organization contains **multiple sites**, Infoblox will create a **corresponding IP space for each site**.
- For organizations with **large, distributed deployments** (for example, dozens or hundreds of branch locations), this behavior can result in a **significant number of IP spaces** being created automatically.
- Each IP space acts as an isolated container for IP address management, helping maintain clear separation of address data across sites.

#### Why this matters

- **Improved organization:** Each site’s network data is logically separated, making it easier to manage and troubleshoot.
- **Scalability impact:** A high number of sites leads to a large number of IP spaces, which may affect how administrators navigate and manage IPAM views.
- **Consistency:** The standardized naming convention ensures predictable identification and mapping between Mist sites and Infoblox IP spaces.