Mist Cloud Organization, Site, and Subscription Administration
Mist Cloud Organization, Site, and Subscription Administration
This domain tests how you structure a Mist tenant and make licensed features usable. Expect questions on the organization-to-site hierarchy, inventory claiming, subscription assignment, templates, and role-based access.
Core rules
- The organization is the top-level tenant. Sites are logical or physical locations under it. Org settings cover admins, SSO, API tokens, inventory, subscriptions, and org-level templates; site settings cover local WLANs, RF, and site variables.
- Claiming adds a device to org inventory. It does not place the device at a site or attach an entitlement. You must assign the device to a site and ensure the site or device has the right subscription.
- Subscriptions such as Wireless Assurance, Wired Assurance, WAN Assurance, Marvis VNA, and Premium Analytics gate features. If a dashboard is empty or a feature is greyed out, check entitlement assignment before troubleshooting the device.
- Org-level WLAN, RF, switch, and device-profile templates must be applied to a site to take effect. Site variables let one template serve many sites.
- RBAC uses predefined or custom roles scoped to org or site. A site admin cannot change org templates.
Worked example
A new branch site has two APs and one EX switch claimed and assigned. The switch appears in inventory but the Wired Assurance dashboard is empty. Reasoning: claiming and site assignment are done, so the missing piece is the Wired Assurance entitlement. Check Organization > Subscriptions and assign Wired Assurance to the site or device; after sync, switch telemetry and SLEs appear.
Traps
- Assuming a claimed device is automatically licensed.
- Editing an org WLAN template and expecting an unapplied site to change.
- Giving a site admin an org-scoped task.
- Confusing inventory assignment with subscription assignment.