Study guide
2.5 VLAN Configuration, Verification & Troubleshooting
JNCIS-ENT Enterprise Routing and Switching Study Guide 2026 Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Exam Overview & Junos Enterprise Fundamentals
1.1 JNCIS-ENT Exam Logistics & Blueprint Breakdown 1.2 Junos CLI, Enterprise Platforms & Interface Families 1.3 Layer 2 Bridging Mechanics & Packet Forwarding
2 Chapter 2: VLANs & Inter-VLAN Routing
2.1 VLAN Segmentation and 802.1Q Tags 2.2 Access, Trunk, Native and Voice VLANs 2.3 IRB Architecture and Interface Families 2.4 IRB Configuration and Packet Walk 2.5 VLAN Configuration, Verification & Troubleshooting
3 Chapter 3: Spanning Tree Protocols
3.1 Layer 2 Loops and Root Bridge Election 3.2 STP Costs, Port Roles, States and BPDUs 3.3 RSTP Rapid Convergence & Link Types 3.4 MSTP Architecture & Spanning Tree Operations
4 Chapter 4: Layer 2 Security & Feature Protection
4.1 Edge BPDU and Root Protection 4.2 Loop Protection and Diagnostic States 4.3 Port Security, MAC Limiting & Persistent MAC Learning 4.4 DHCP Snooping, Dynamic ARP Inspection (DAI) & IP Source Guard 4.5 Layer 2 Firewall Filters: Types, Order and Actions
5 Chapter 5: Advanced Layer 2 Features & Storm Control
5.1 Storm Control & Broadcast/Multicast Suppression 5.2 MACsec Link Security and Key Agreement 5.3 LLDP and LLDP-MED Operations & Verification
6 Chapter 6: Protocol-Independent Routing & Load Balancing
6.1 Static, Aggregate, and Generated Routes 6.2 Routing Instances and RIB Groups 6.3 Junos Load Balancing & Filter-Based Forwarding (FBF) 6.4 Martian Routes and Route Acceptance
7 Chapter 7: Junos Routing Policy & Firewall Filters
7.1 Routing Policy Framework & Term Evaluation 7.2 Prefix Lists & Route Filters 7.3 Firewall Filters & Policers
8 Chapter 8: Open Shortest Path First (OSPF) Operation
8.1 OSPF Architecture & Neighbor Adjacency Formation 8.2 OSPF Areas & LSA Types 8.3 OSPFv2 & OSPFv3 Configuration and Verification
9 Chapter 9: Advanced OSPF Features & Routing Policies
9.1 OSPF Special Area Types 9.2 Route Summarization & OSPF Authentication 9.3 OSPF Diagnostics & Common Failure Scenarios
10 Chapter 10: Intermediate System to Intermediate System (IS-IS)
10.1 IS-IS Encapsulation and NET Identity 10.2 IS-IS Levels, Areas and Default Routing 10.3 IS-IS PDU Families and Neighbor Exchange 10.4 IS-IS Database Synchronization and DIS 10.5 IS-IS Configuration, Metrics & Troubleshooting
11 Chapter 11: Border Gateway Protocol (BGP)
11.1 BGP Roles, AS Numbers and TCP Transport 11.2 EBGP/IBGP Sessions, State Machine and Messages 11.3 BGP Attributes & Junos Path Selection Algorithm 11.4 BGP Configuration & Policy Implementation 11.5 BGP Scaling with Route Reflection & Diagnostics
12 Chapter 12: IP Tunneling & High Availability
12.1 GRE & IP-IP Tunneling Architecture 12.2 Link Aggregation (LAG/LACP) & Redundant Trunk Groups (RTG) 12.3 Virtual Chassis Roles and Elections 12.4 Virtual Chassis Links, Splits and Provisioning 12.5 Routing Engine Redundancy: GRES, NSR, NSB and GR 12.6 BFD Detection and VRRP Gateway Redundancy 12.7 Unified ISSU: Requirements and Verification
2.5 VLAN Configuration, Verification & Troubleshooting
Key Takeaways Explain This Topic AI
Verification of Junos VLAN operations requires multi-layer inspection using 'show vlans detail', 'show ethernet-switching interfaces', and 'show arp'.
Native VLAN mismatches can place untagged traffic in different broadcast domains at opposite ends; standard RSTP does not negotiate native VLAN IDs.
If an active VLAN is omitted from the trunk's 'vlan members' allowed list, the switch silently discards that VLAN's frames at the Layer 2 ingress pipeline without generating interface errors.
A structured troubleshooting workflow maps symptoms—such as unreachable gateways or intermittent packet loss—to Layer 1 physical faults, Layer 2 tag mismatches, or Layer 3 IRB binding omissions.
Duplex mismatches resulting from disabled auto-negotiation cause late collisions, frame check sequence (FCS) errors, and severe application throughput degradation.
Last updated: October 2026
Enterprise Multi-VLAN Configuration Template
To establish a baseline for enterprise switching operations and troubleshooting, consider the following end-to-end configuration template for a Junos Enhanced Layer 2 Software (ELS) switch. This template incorporates distinct corporate data, voice, guest, and native transit VLANs, configured alongside access edge ports, 802.1Q trunk uplinks, and Integrated Routing and Bridging (IRB) Layer 3 interfaces. [edit]
- # 1. Define Layer 2 VLANs
- set vlans DATA-CORP vlan-id 10
- set vlans VOICE-CORP vlan-id 20
- set vlans GUEST-NET vlan-id 30
- set vlans NATIVE-TRANSIT vlan-id 99
- # 2. Bind Layer 3 IRB Interfaces to VLANs
- set vlans DATA-CORP l3-interface irb.10
- set vlans VOICE-CORP l3-interface irb.20
- set vlans GUEST-NET l3-interface irb.30
- # 3. Configure Layer 3 Gateway IP Addresses
- set interfaces irb unit 10 description "Default Gateway - Corporate Data"
- set interfaces irb unit 10 family inet address 10.10.10.1/24
- set interfaces irb unit 20 description "Default Gateway - Corporate Voice"
- set interfaces irb unit 20 family inet address 10.10.20.1/24
- set interfaces irb unit 30 description "Default Gateway - Guest Wi-Fi"
- set interfaces irb unit 30 family inet address 172.16.30.1/24
- # 4. Configure Inter-Switch 802.1Q Trunk Uplink
- set interfaces ge-0/0/0 description "Trunk Uplink to Distribution Switch"
- set interfaces ge-0/0/0 native-vlan-id 99
- set interfaces ge-0/0/0 unit 0 family ethernet-switching interface-mode trunk
set interfaces ge-0/0/0 unit 0 family ethernet-switching vlan members [ DATA-CORP VOICE-CORP GUEST-NET NATIVE-TRANSIT ]
- # 5. Configure User Edge Access Port with Voice VLAN & LLDP-MED
- set interfaces ge-0/0/1 description "Workstation + IP Phone Access Port"
- set interfaces ge-0/0/1 unit 0 family ethernet-switching interface-mode access
- set interfaces ge-0/0/1 unit 0 family ethernet-switching vlan members DATA-CORP
- set switch-options voip interface ge-0/0/1.0 vlan VOICE-CORP
- set switch-options voip interface ge-0/0/1.0 forwarding-class expedited-forwarding
- set protocols lldp interface ge-0/0/1
- set protocols lldp-med interface ge-0/0/1
- Essential Monitoring & Verification Commands
Troubleshooting Layer 2 and Layer 3 switching issues in Junos requires mastering four fundamental CLI verification commands:
1. show vlans and show vlans detail
The primary command to verify VLAN status, 802.1Q tags, and interface associations across the switch fabric: user@EX4400> show vlans detail
VLAN: DATA-CORP, Shared VLAN ID: 0, Tag: 10, State: Active
Active interfaces:
- ge-0/0/0.0 (tagged)
- ge-0/0/1.0 (untagged)
- Layer 3 interface: irb.10
- VLAN: GUEST-NET, Shared VLAN ID: 0, Tag: 30, State: Inactive
Active interfaces:
- none
- Layer 3 interface: irb.30
Operational Analysis :
State: Active vs. Inactive : A VLAN is marked Active only when at least one assigned physical or aggregated interface is in the operational up state. Notice that GUEST-NET displays State: Inactive because no active interfaces belong to it ( Active interfaces: none ).
Impact on IRB : When a VLAN transitions to Inactive , its bound IRB interface remains operationally down ( Link: Down ), preventing the switch from routing traffic for that subnet or responding to local pings.
2. show ethernet-switching interfaces
Displays the operational port mode, native VLAN ID, active VLAN memberships, and Spanning Tree Protocol (STP) state for every switched port on Junos ELS switches: user@EX4400> show ethernet-switching interfaces
- Interface State VLAN members Tag Tagging Blocking
- ge-0/0/0.0 up DATA-CORP 10 tagged Forwarding
- VOICE-CORP 20 tagged Forwarding
- NATIVE-TRANSIT 99 untagged Forwarding
- ge-0/0/1.0 up DATA-CORP 10 untagged Forwarding
- VOICE-CORP 20 tagged Forwarding
Operational Analysis :
Inspect the Tagging column: On trunk port ge-0/0/0.0 , NATIVE-TRANSIT is listed as untagged , illustrating a trunk explicitly configured for untagged native egress; verify that behavior on the actual platform. On access port ge-0/0/1.0 , DATA-CORP is untagged while VOICE-CORP is tagged .
Inspect the Blocking column: If Spanning Tree has blocked a port to prevent a bridging loop, the state displays Discarding or Blocking , explaining why all frame transmission has halted on that link.
- 3. show arp
- Inspects Layer 3 IPv4-to-MAC resolution on IRB routing interfaces: user@EX4400> show arp
- MAC Address Address Name Interface Flags
- aa:aa:aa:11:11:11 10.10.10.50 host-a.corp irb.10 none
- 00:05:86:71:00:01 10.10.10.1 switch-gw irb.10 permanent
- incomplete 172.16.30.45 guest-tablet irb.30 none
Operational Analysis :
A flag of none indicates dynamically resolved ARP entries.
An entry displaying incomplete indicates the switch issued an ARP request for the target IP address out the designated IRB interface, but received no ARP reply. This occurs when the client is powered off, firewalled against ARP, or connected to a port assigned to the wrong VLAN.
4. show ethernet-switching table
Displays the switch's Layer 2 Filtering Database (MAC address table): user@EX4400> show ethernet-switching table
- Ethernet switching table : 3 entries, 3 learned
- Routing instance : default-switch
- VLAN MAC address Type Age Interfaces
- DATA-CORP aa:aa:aa:11:11:11 Learn 0 ge-0/0/1.0
- VOICE-CORP cc:cc:cc:33:33:33 Learn 12 ge-0/0/1.0
- DATA-CORP b8:bb:bb:22:22:22 Learn 5 ge-0/0/0.0
Operational Analysis : If a MAC rapidly alternates between ports, investigate a Layer 2 loop, host mobility, multihoming, or spoofing. MAC flapping is evidence to investigate, not proof of one cause.
- Common Exam Traps & Troubleshooting Scenarios
- Trap 1: Native VLAN Mismatch across Trunk Links
A classic enterprise misconfiguration occurs when two interconnected switches are configured with mismatched native VLAN IDs on their interconnecting trunk port:
- Switch-01: set interfaces ge-0/0/0 native-vlan-id 10
- Switch-02: set interfaces ge-0/0/0 native-vlan-id 20
Failure Mechanism :
If Switch-01’s egress configuration transmits VLAN 10 frames untagged across the trunk, Switch-02 receives them untagged and immediately assigns them to its local native VLAN (VLAN 20). As a result, traffic leaks between unrelated broadcast domains, creating a major security violation.
Verification : Standard RSTP BPDUs do not carry a native-VLAN negotiation TLV. A mismatched native VLAN can misclassify untagged user traffic without RSTP reporting a PVID inconsistency. Compare native-vlan-id and allowed membership on both ends, and inspect ingress/egress tagging. Do not rely on a spanning-tree alarm to enforce VLAN consistency.
Trap 2: Trunk Pruning Drops (Missing VLAN in Allowed List)
An engineer provisions a new VLAN (e.g., VLAN 40, DEV-OPS ) on both access and distribution switches, but forgets to update the trunk allowed list on the interconnecting link: user@EX4400# set interfaces ge-0/0/0 unit 0 family ethernet-switching vlan members [ DATA-CORP VOICE-CORP ]
# Missing DEV-OPS!
Diagnostic Gotcha :
Frames tagged with VLAN 40 arriving at trunk port ge-0/0/0 are dropped immediately by the PFE ingress parser. However, running show interfaces ge-0/0/0 shows zero input errors, zero CRC errors, and normal link carrier! The physical port appears perfectly healthy because the frames are structurally valid Ethernet; the drop occurs purely at the Layer 2 parser level. Only running show ethernet-switching interfaces ge-0/0/0 detail will reveal that VLAN 40 is absent from the active membership list.
Trap 3: Missing l3-interface Association
An administrator configures interfaces irb unit 20 family inet address 10.10.20.1/24 , but omits set vlans VOICE-CORP l3-interface irb.20 under the vlans hierarchy.
Symptom & Root Cause :
Hosts in VLAN 20 cannot reach their default gateway ( 10.10.20.1 ) or any remote subnets. When viewing show interfaces terse irb.20 , do not assume an operationally up IRB proves the VLAN association is correct. However, running show vlans VOICE-CORP detail reveals: Layer 3 interface: none
Because the IRB interface is not bound to the Layer 2 broadcast domain, the switch never binds its MAC address to VLAN 20 and ignores all incoming ARP requests for 10.10.20.1 .
Trap 4: Port Assigned to Wrong Access VLAN
A technician connects a new workstation to port ge-0/0/5 . The client receives an IP address in the 172.16.30.0/24 range instead of the corporate 10.10.10.0/24 range, and cannot access internal databases. Running show ethernet-switching interfaces ge-0/0/5 immediately reveals VLAN members: GUEST-NET instead of DATA-CORP . The fix is a simple reassignment under family ethernet-switching vlan members .
Trap 5: Duplex and Speed Mismatches
When connecting a switch trunk or server port, an administrator hardcodes the switch port to speed 100m and link-mode full-duplex , while leaving the connecting endpoint configured for auto-negotiation .
IEEE 802.3u Rule :
Under IEEE 802.3u auto-negotiation rules, if a port fails to receive auto-negotiation FLP (Fast Link Pulses) from its partner, it utilizes parallel detection. Parallel detection can reliably detect speed (100 Mbps), but standard rules mandate that duplex must fall back to half-duplex .
Symptom :
One side operates at full-duplex while the other operates at half-duplex. Under light traffic, pings succeed. However, when large data transfers commence, the full-duplex end transmits while the half-duplex end is sending, triggering collisions on the half-duplex port. Running show interfaces ge-0/0/0 extensive reveals mounting Late Collisions and FCS / CRC Errors , severely degrading application performance.
Comprehensive Troubleshooting Reference
Symptom / Failure Probable Root Cause Verification CLI Command Junos CLI Remediation
Hosts in VLAN cannot ping default gateway; remote routing fails IRB logical unit is not bound to the VLAN hierarchy show vlans detail (Inspect Layer 3 interface ) set vlans <vlan-name> l3-interface irb.<unit> followed by commit
VLAN traffic fails to cross trunk link; no errors on physical port VLAN is missing from the trunk's vlan members allowed list show ethernet-switching interfaces <if-name> set interfaces <if-name> unit 0 family ethernet-switching vlan members <vlan-name>
Untagged traffic enters the wrong VLAN across a trunk Native VLAN ID mismatch between interconnected switches show ethernet-switching interfaces (Compare native VLAN on both sides) Configure identical native-vlan-id <id> and matching vlan members on both switches
High packet loss during file transfers; late collisions incrementing Duplex mismatch (one side hardcoded full, partner auto-negotiating) show interfaces <if-name> extensive (Look for late collisions & duplex) Set both sides to auto-negotiate, or hardcode matching speed and link-mode on both ends
IRB interface reports Down/Down; cannot route traffic All physical ports assigned to the VLAN are unplugged or down show vlans <vlan-name> (Inspect State: Inactive ) Ensure at least one physical access or trunk member port is administratively and operationally up
Output note: Command output shown here is a schematic teaching example, not a captured device session. Field names and feature support depend on platform and Junos release.