Projects › Junos Access Switch: Naming VLANs and Committing the Candidate
Junos Access Switch: Naming VLANs and Committing the Candidate
An accountancy practice is standardising on Juniper EX switches. Build VLAN 30 (Partners) and VLAN 40 (Reception) in the candidate configuration and commit them.
Difficulty: foundation · Time: about 40 minutes
Why it matters
Junos does nothing until you commit. An engineer who types commands and walks away leaves a switch that has not changed at all, which is a genuinely disorienting first experience.
Technologies
- Juniper Junos
- Junos Commit Model
- VLANs
Related projects
- Dual-Stack Collapsed-Core Campus with Per-VLAN Root Placement
- Campus Gateway High Availability with HSRPv2 and Uplink Tracking
- Campus Automation & Assurance Deployment via Catalyst Center
- Cross-Switch LACP EtherChannel & PortFast BPDU Guard
- Enterprise Wireless LAN with Catalyst 9800 WLC & FlexConnect
- Network Observability: Secure SNMPv3, Remote Syslog, and Flexible NetFlow
- IPv6-Only Multi-Area OSPFv3 for a Research Campus
- Capstone: Multi-Tier Global Enterprise Network Architecture