Mist Wired Assurance Configuration and Deployment
Domain overview
Mist Wired Assurance Configuration and Deployment tests how you bring EX switches into the Mist cloud and standardize their configuration: claiming, ZTP, org/site hierarchy, switch templates, port profiles, switch profiles, site variables, and firmware policy.
Core rules
- Mist manages configuration at organization and site scope. A switch must be claimed into the org and assigned to a site before site-level templates apply.
- ZTP lets a factory-default switch contact Mist and receive its configuration; DHCP option 43 or a cloud redirect can point it to Mist. Manual claim by MAC or serial is the fallback.
- Switch templates define Junos configuration in reusable form; port profiles define per-port settings such as access/trunk mode, VLANs, PoE, 802.1X, and storm control; switch profiles define device-level settings such as NTP, DNS, syslog, and RADIUS.
- Site variables parameterize templates, so one template can serve multiple sites with different VLAN IDs, subnets, or RADIUS servers.
- Firmware policies control which Junos release switches run; do not mix unplanned upgrades with a template rollout.
Worked example
A company has two sites. The template uses {{vlan_data}} and {{radius_server}}. Site A sets vlan_data=10 and radius_server=10.1.1.10; Site B sets vlan_data=20 and radius_server=10.2.2.10. A port profile called AP-Trunk allows the data VLAN plus a management VLAN, enables PoE, and sets 802.1X. After claiming the switch and assigning it to Site A, Mist renders the template with Site A's variables. If the switch shows the template but ports are wrong, check that the port profile is attached to the correct ports and that the switch is assigned to the intended site.
Traps
A claimed but unassigned switch will not receive site configuration. Variable names are case-sensitive, and a missing value can break rendering. Local CLI changes can be overwritten by Mist; make changes in templates unless you have a deliberate override.