Wired Assurance and Switch Configuration
Wired Assurance and Switch Configuration
This domain tests how Mist configures and monitors Juniper EX switches. Expect port profiles, switch templates, site variables, claiming and adoption, and Wired Assurance health evidence.
Core rules
- Claim the switch into org inventory, assign it to a site, and confirm Wired Assurance entitlement. Adoption establishes management; it does not configure ports by itself.
- Switch templates and port profiles define configuration. A port profile sets access or trunk mode, VLAN membership, native VLAN, PoE, speed and duplex, and authentication. A switch template maps profiles to port ranges.
- Use site variables for VLAN IDs and other per-site values so one template can serve many sites. Undefined variables produce failed or incomplete configuration.
- Wired Assurance surfaces switch and port health, insights, and SLEs. Use port status, LLDP neighbors, PoE budget, and events to verify that the intended profile is active.
- Virtual Chassis and uplink ports need explicit trunk and native VLAN design; an AP uplink is not an access port.
Worked example
An AP connected to an EX switch does not get an IP address. The port profile is access VLAN 10, but the AP needs a trunk with native VLAN 100 for management. Reasoning: the AP is powered but management traffic is tagged incorrectly. Change the port profile to trunk, set native VLAN 100 and allowed VLANs, then re-check LLDP and the AP's DHCP event.
Traps
- Mixing up a port profile with a device profile.
- Leaving a site variable undefined.
- Mismatching native VLAN on a trunk.
- Forgetting PoE budget on high-density ports.
- Assuming claiming a switch applies a template.