Juniper Mist Configuration Basics · Topic 3 of 4
Organizations, Sites, Templates, Labels and Policies
Learn Mist structure for the JN0-253: orgs, sites, site groups, WLAN, RF and switch templates, device profiles, and WxLAN labels and policies.
- 6 min
- Includes a diagram
- Org holds admins, inventory and subscriptions; sites hold devices; site groups bundle sites.
- New org gets a Primary Site automatically; it can be renamed or deleted.
- Sites: Organization > Site Configuration; name, time zone and location at minimum; Site ID cannot change; Clone Site copies settings.
What it is
An organization is the top of the Mist hierarchy: it holds the admins, inventory, subscriptions and org-wide settings. A site is a physical location inside it, such as a building or a branch, and every managed device is assigned to one site. Site groups bundle similar sites so they can share configuration.
Templates hold configuration once at org level and apply it to many sites. Labels name groups of users or resources, and WxLAN policies use those labels to allow or block traffic.
How it works
Organizations
An organization is created after the first account, with Create Organization. Mist automatically creates a site named Primary Site in every new org. It has no special status: rename it, set its location, or delete it like any other site.
One account can be an admin of several organizations. An existing user can create another organization from the account menu.
Sites
Sites are managed on Organization > Site Configuration.
| Action | How |
|---|---|
| Create | Click Create Site; at a minimum enter the name, time zone and location |
| Edit | Click the site and change its settings |
| Copy | Click the site, then Clone Site |
| Remove | Click the site, then Delete Site |
Mist generates a Site ID that uniquely identifies the site and cannot be changed. Set the country correctly, because it makes the APs follow that country's radio regulations, and pick the time zone that matches the site.
Site variables are defined per site at Organization > Site Configuration > Site Variables. A template can refer to a variable instead of a fixed value, so one template produces the right value at every site.
Templates and where they apply
| Template | Configured at | Holds |
|---|---|---|
| WLAN template | Organization > Wireless > WLAN Templates | WLANs (SSIDs) and their WxLAN policies |
| RF template | Organization level | Radio settings per band; every site should have one |
| Device profile | Organization level | AP settings for a subset of APs |
| Switch template | Switch Templates page at org level | Switch configuration such as VLANs and port profiles |
| WAN Edge template | Organization level | WAN edge configuration for branch routers |
A WLAN template is applied to the entire organization, to site groups or to sites, and individual sites can be marked as exceptions. A site can receive more than one template, and local site WLANs can be added on top.
Which setting wins
The narrower setting always overrides the broader one.
| Area | Precedence, lowest to highest |
|---|---|
| Switches | Organization template, then site configuration, then device configuration |
| AP radios | RF template (site), then device profile, then settings on the AP itself |
| Variables | Site variable, then device variable with the same name |
In the AP view, a value inherited from the RF template shows Use site setting, and a value that overrides a device profile shows Overriding Profile.
Put common settings in templates and keep device-level overrides rare. Changes then happen once at org level instead of on every device.
Labels
A label represents a collection of users or resources. Each label has a type, and the type decides which side of a policy it can be used on.
| Side | Label types |
|---|---|
| User | AAA Attribute, Access Point, Wi-Fi Client, WLAN |
| Resource | Application, Hostname, IP Address, Port |
Organization labels are created at Organization > Wireless > Labels and are used in WLAN template policies. Site labels are created at Site > Wireless > Labels and are used in site policies.
WxLAN policies
A WxLAN policy rule pairs users (user labels) with an action, Allow or Block, and resources (resource labels). Template policies live in the WLAN template; site policies live on Site > Wireless > Policy.
- Template (org) policies are checked first; a user that matches none of them is checked against site policies.
- Rules are read top down; a user matches the first rule whose user labels all apply to it.
- The resources in that matched rule decide what is allowed or blocked.
- A site policy ends with a default row for all users and all resources, set to allow or block.
| Rule contents | Result for anything not listed |
|---|---|
| Only allow resources | Denied |
| Only block resources | Allowed |
| A mix of allow and block | Must be listed explicitly; add a catch all such as block 0.0.0.0/0 if needed |
A rule with only allow resources quietly blocks everything else for those users. A guest rule that allows just a printer label also removes internet access unless an internet label is allowed too.
Common mistakes
Treating Primary Site as special. It is just the first site Mist creates; it can be renamed or deleted.
Expecting an org template to beat a device setting. The narrowest level wins: device beats site, and site beats the org template.
Using a site label in a WLAN template policy. Only organization labels appear in WLAN template policies; site labels are for site policies.
Putting a resource label on the user side. Application, Hostname, IP Address and Port labels describe resources, not users.
What to remember for the exam
- Org holds admins, inventory and subscriptions; sites hold devices; site groups bundle sites.
- New org gets a Primary Site automatically; it can be renamed or deleted.
- Sites: Organization > Site Configuration; name, time zone and location at minimum; Site ID cannot change; Clone Site copies settings.
- Country makes the AP radios follow that country's regulations; set the site's own time zone.
- WLAN templates apply to the entire org, site groups or sites, with site exceptions.
- Switch precedence: org template, then site, then device; device wins.
- AP radio precedence: RF template, then device profile, then AP.
- User labels: AAA Attribute, Access Point, Wi-Fi Client, WLAN. Resource labels: Application, Hostname, IP Address, Port.
- WxLAN: template rules first, then site rules; first matching rule; Allow or Block.
Check yourself
A VLAN is set in the switch template and a different VLAN is set on one switch. Which applies to that switch?
The device-level setting, because the narrower level overrides the organization template.
A WLAN template applies to the entire org, but one site needs different SSIDs. How do you handle it?
Mark that site as an exception in the template's scope and give it its own template or site WLANs.
A rule for guest users lists only one allow resource, a printer label. What else can guests reach?
Nothing else, because a rule with only allow resources denies everything not listed.
Topic 3 of 4 in Juniper Mist Configuration Basics
Test yourself on Juniper Mist Configuration Basics
The full Juniper JNCIA-MistAI JN0-253 question bank has 668 questions, with timed practice exams and an explanation for every answer.
This study guide is independent and is not affiliated with, endorsed by, or sponsored by Juniper. Vendor names, certification names and exam codes are trademarks of their respective owners and are used for identification only.