IPAM for Juniper Mist networks, kept in sync automatically
Connect getIPAM to your Mist organisation, pick the sites to track, and every wireless client connected to them appears in your IPAM with its MAC, IP and hostname — refreshed every 2 hours, nothing to install. Stop maintaining a spreadsheet that's wrong before you save it.
Free Sandbox for manual IPAM · Mist sync on Small Business, 14-day trial
| IP Address | Status | Label | Asset | Source | Tags | Notes | |
|---|---|---|---|---|---|---|---|
| 10.0.50.1 | allocated | srx-hq | SRX gateway | manual | infra | Manual entry | |
| 10.0.50.2 | allocated | ap45-boardroom | Mist AP45 | manual | infra | Manual entry | |
| 10.0.50.21 | allocated | laptop-jsmith | Staff laptop | mist | staff | - | |
| 10.0.50.22 | allocated ⚠ Conflict | print-hq-01 | Wi-Fi printer | mist | printer | Also seen from label-printer-02 | |
| 10.0.50.23 | allocated | boardroom-display | Conference display | mist | av | - | |
| 10.0.50.40 | reserved | Visitor kiosk | - | - | - | Held for reception refit |
The Staff Wi-Fi subnet after a Mist sync.
Why Juniper Mist networks outgrow the spreadsheet
Mist already knows every wireless client on every site. The sheet only knows what someone typed.
Stale the moment you save it
A laptop joins the WLAN, picks up a lease, and the sheet never hears about it.
Conflicts you hear about from users
A printer gets a static in the DHCP range, and the first sign is a device that keeps dropping off Wi-Fi.
Five sites, five spreadsheets
Each site is documented differently, if at all, and nobody has the whole address plan in one place.
How getIPAM syncs with Mist
Three settings in the app. Nothing is installed on your network and nothing is imported until you confirm.
Connect
Create an organisation API token in the Mist portal (Organization → Settings → API Tokens), choose the Mist cloud your org lives on — Global, EU or any of the regional clouds — and paste the token into getIPAM. It reads your accessible organisations and you pick one. Nothing is installed and no port is opened: getIPAM talks only to the Mist cloud, and it only ever reads.
Discover
Tick the sites you want to track — each one counts as a site on your plan. For every site, getIPAM reads the wireless clients currently connected and turns each into an asset with its MAC, IP, hostname and name. Clients land in the subnets you've already defined; you own the structure, Mist fills it in. You review the list before anything is written, and you can save the connection without importing at all. Matching is by MAC, so a device you'd already added by hand is reused, not duplicated — and manual records are never overwritten.
Stay in sync
Every 2 hours, or on demand. New clients are added, moved IPs are updated, and a client whose IP is already allocated to something else is flagged as a conflict rather than silently reassigned. Every change sync makes is written to the audit trail, tagged as system so it's distinguishable from edits by people.
Connect through the Juniper Mist cloud API to import connected wireless clients as assets and keep their IP allocations in sync. Your hardware stays behind your firewall.
Create one in the Mist portal → Organization → Settings → API Tokens.
Pick the cloud your org lives on, or the token won't authenticate.
2 selected of 5 allowed by your plan
Review before anything is written to your IPAM. Nothing is imported until you confirm.
What gets synced
| From Mist | Becomes in getIPAM | Example |
|---|---|---|
| Wireless client — MAC | Asset (matched or created) | 9c:05:d6:1a:2b:3c |
| Wireless client — IP | IP allocation in the matching subnet | 10.0.50.21 |
| Wireless client — hostname, or username if no hostname | Asset hostname | laptop-jsmith |
| Wireless client — name, falling back to hostname | Asset name | "Staff laptop" |
| Organisation and sites | Used to choose what to sync; not stored on the asset | "HQ — Main office" |
getIPAM reads the wireless clients Mist reports as connected to each site. Wired clients, switches and gateways aren't read from Mist today — add them manually or by Excel import and they sit alongside the synced records. getIPAM also doesn't import your Mist networks or VLANs as subnets — you define those in getIPAM (or upload them from a spreadsheet) so the sync has somewhere to land each client.
Everything you need to run Mist IPAM without the busywork
| Subnet | Network | IP Usage | Utilization |
|---|---|---|---|
| Staff Wi-Fi | 10.0.50.0/24 | 61 avail3 res40 alloc150 dhcp | 76% |
| Guest Wi-Fi | 10.0.60.0/24 | 175 avail79 alloc | 31% |
| Free /24 | 10.0.21.0 – 10.0.49.255 | ||
| Servers | 10.0.20.0/24 | 96 avail158 alloc | 62% |
See your whole address space as a tree
Break a /16 into /24s and a /24 into /28s. Every level shows how full it is, so you know a subnet is filling up before it's full.
- Type
- Laptop
- Hostname
- laptop-jsmith
- Location
- HQ, 2nd floor
- Owner
- jsmith
- MAC Address
- 9c:05:d6:1a:2b:3c
- Source
- Mist integration
- Last updated
- Today, 09:15
- IP assigned 10.0.50.21by Mist Integration · Today, 09:15
- Asset updatedby andy · Yesterday, 18:02Location: — → HQ, 2nd floor
- Asset createdby Mist Integration · 12 Aug, 14:30
Every IP tied to a real device
Each synced client is an asset, not just a row: MAC, IP, the hostname the device reports — or the Wi-Fi username where it doesn’t — plus whatever you add: owner, location, tags. Manual and synced records sit side by side, and the source is shown on every one.
Conflicts flagged, never papered over
If a client shows up on an IP that's already allocated to something else, getIPAM records a conflict against the new client and leaves the existing allocation untouched. You get an email digest of new devices and conflicts after each sync.
Built for teams running Juniper Mist
Multi-site campus
You run a few Mist sites — an HQ, a second building, a warehouse — and need one address plan across them, not a spreadsheet per site.
MSP or Juniper partner
You look after Mist organisations for a handful of clients and want one place that shows what's actually on the Wi-Fi at each.
Growing IT team
You've inherited a Mist estate and an IP sheet that was last accurate the day it was made.
Planning a new VLAN or subnet split?
Use the free getIPAM Subnet Calculator to carve up a CIDR block, then create the subnets in getIPAM so the Mist sync has somewhere to land.
Pricing for Juniper Mist networks
Start free. Add Mist sync when you're ready to stop typing.
Small Business
Small IT teams and MSPs
- 5 users
- 5,000 IP addresses · 5,000 assets
- 5 sites — one per Mist site
- Mist sync every 2 hours
- Full REST API
- Excel import/export
- Email alerts for new devices and conflicts
- 12-month audit history
- 14-day free trial
Free Sandbox
Manual IPAM, no commitment
- 1 user
- 250 IPs
- Manual entry and Excel import/export
- 30-day audit history
- Mist sync
- API
Need more sites? Enterprise covers 10. Compare all plans →
Mist IPAM, common questions
How does getIPAM connect to my Mist organisation?
With an organisation API token you create in the Mist portal under Organization → Settings → API Tokens. You choose the Mist cloud your org is hosted on, paste the token, and pick the organisation from the ones it can see. getIPAM never connects to your access points or switches directly.
My org is on the EU cloud (or another regional cloud) — does that work?
Yes. getIPAM lets you choose the Mist cloud — Global, EU or any of the regional clouds — and talks only to that API host. Pick the one your org lives on; a token for one cloud won't authenticate against another.
Do I need to open a port or run an agent?
No. There's no inbound connection to your network and nothing to install. getIPAM reads from the Mist cloud your access points already report to.
Does getIPAM change anything in my Mist configuration?
No. getIPAM only ever reads from Mist: it lists your organisations and sites, and reads the connected-client list for the sites you selected. It never sends a write.
What does the Mist sync bring in?
The wireless clients currently connected to each selected site: MAC address, IP address, hostname and name. Each becomes an asset with an IP allocation in the matching subnet. Wired clients, switches and gateways aren’t read from Mist today, and networks, VLANs and DHCP settings are not imported — you define subnets in getIPAM.
Some of my assets have a person's name as the hostname — why?
When a client doesn't report a hostname, getIPAM uses the username Mist has for it, which on an 802.1X or PPSK network is often the person who signed in. You can rename the asset in getIPAM; sync will leave your edit alone.
How many sites can I sync?
As many as your plan allows: each Mist site counts as one site, so Small Business covers up to five and Enterprise up to ten under one integration.
What happens to records I've entered by hand?
They're never overwritten. Matching is by MAC, so a device you added manually is reused rather than duplicated, and its name and hostname are left as you set them. Subnets are never created or changed by sync.
What if a synced client's IP is already in use?
getIPAM records a conflict against the incoming client and leaves the existing allocation untouched, and includes it in your email digest. Nothing is reassigned automatically.
How often does it sync, and what if a sync fails?
Every 2 hours, plus on demand. A failed run is shown against the integration with the error; existing records are left as they were and the next run carries on.
Can I import my existing spreadsheet first?
Yes. Upload an Excel file to create subnets and assets, then connect Mist. Synced and manual records live side by side with the source shown on each.
Can I self-host getIPAM?
No, getIPAM is a hosted service. For systems without a cloud API, Excel import/export is the way to bring data in.
Connect your Mist sites and retire the spreadsheet.
Create your account, paste an organisation token, and watch the Staff Wi-Fi subnet fill itself in. Start a 14-day Small Business trial — cancel any time.
Also works with: Ubiquiti UniFi · Cisco Meraki