Study guide
2.3 IRB Architecture and Interface Families
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.3 IRB Architecture and Interface Families
Key Takeaways Explain This Topic AI
Intra-VLAN bridging uses the destination MAC without decrementing the IP TTL.
A frame addressed to the gateway MAC can enter the hardware Layer 3 lookup path.
ELS uses irb units for VLAN gateways; legacy non-ELS examples use vlan units.
Last updated: October 2026
The Architectural Need for Layer 3 Inter-VLAN Routing
Virtual Local Area Networks enforce hard Layer 2 boundaries. Inside a switch, the Packet Forwarding Engine maintains an isolated Filtering Database (FDB)—also called a MAC address table—for each configured VLAN. When a host in VLAN 10 transmits a frame toward an IP address residing in VLAN 20, the switch cannot bridge that frame across broadcast domains. Bridging between VLANs would collapse their broadcast isolation, undermine security boundaries, and cause IP subnetting conflicts. Therefore, any communication between distinct VLANs mandates a Layer 3 routing function.
The Evolution of Inter-VLAN Routing Architecture
Router-on-a-Stick (Legacy Approach) :
In early campus networks, Layer 2 switches lacked routing capabilities. To route between VLANs, the switch connected via an 802.1Q trunk link to an external router. The router created logical subinterfaces (one per VLAN), each acting as the default gateway for its respective subnet. While functional, this design created a severe architectural bottleneck: every inter-VLAN packet had to travel up the physical trunk link to the router and immediately traverse back down the same trunk link to the switch. This "hairpinning" consumed double the trunk bandwidth and introduced significant forwarding latency.
Multilayer Switching with Internal Gateways (Modern Standard) :
Modern enterprise switches—such as Juniper Networks EX and QFX series—integrate full Layer 3 routing logic directly into their switching silicon. The switch hardware contains specialized Application-Specific Integrated Circuits (ASICs) capable of performing Layer 2 frame switching and Layer 3 IP routing concurrently at line rate. Instead of exiting the chassis to an external router, inter-VLAN traffic is routed internally across the switch backplane through internal logical routing interfaces, eliminating external bottlenecks and delivering hardware forwarding without the external router-on-a-stick path.
Junos Integrated Routing & Bridging (IRB) Architecture
Junos OS executes routing and switching through a rigorous separation of the Control Plane (managed by the Routing Engine, or RE) and the Forwarding Plane (managed by the Packet Forwarding Engine, or PFE). In multilayer switches, the RE runs routing protocols (such as OSPF, IS-IS, and BGP), resolves ARP requests, and populates the master routing table ( inet.0 ). The RE then compiles this routing state into an optimized Forwarding Information Base (FIB) and downloads it directly into the PFE's Layer 3 forwarding ASICs.
PFE Packet Processing Mechanics
When an Ethernet frame ingresses a physical switch port, the PFE performs an instantaneous Layer 2 hardware lookup on the frame's Destination MAC (DMAC) address:
Intra-VLAN Bridging : If the DMAC matches another host's MAC address learned within that same VLAN, the switch bridges the frame directly out the associated egress port. The Layer 3 IP header remains untouched, and the Time-to-Live (TTL) is not decremented.
Inter-VLAN Routing : If the DMAC matches the switch's own internal Layer 3 interface MAC address (the default gateway MAC), the PFE hardware recognizes that the frame is addressed to the switch itself for routing. The PFE strips the incoming Layer 2 Ethernet header and passes the decapsulated IP packet to the Layer 3 FIB lookup engine. The FIB determines the egress route, identifies the outbound VLAN, decrements the TTL, recomputes the checksum, encapsulates the packet in a new Layer 2 header, and transmits it toward the destination host.
Platform Evolution: Legacy RVI ( vlan.unit ) vs. Modern ELS IRB ( irb.unit )
Candidates studying for the JNCIS-ENT examination must understand the platform evolution between legacy Junos switching platforms and modern Enhanced Layer 2 Software (ELS) architectures:
1. Legacy Non-ELS Platforms (EX2200, EX3200, EX3300, EX4200, EX8200)
On original EX series switches running non-ELS Junos code, Layer 3 VLAN interfaces were designated as Routed VLAN Interfaces (RVIs) and configured under the vlan interface hierarchy: [edit interfaces]
user@legacy-switch# set vlan unit 10 family inet address 192.168.10.1/24
- [edit vlans]
- user@legacy-switch# set SALES vlan-id 10 l3-interface vlan.10
- 2. Modern ELS Platforms (EX2300, EX3400, EX4300, EX4400, EX4600, QFX, MX)
Modern enterprise and data center switches running ELS, as well as Juniper MX Series 5G Universal Routing Platforms, standardized on Integrated Routing and Bridging (IRB) interfaces. The interface name is explicitly irb followed by a logical unit number: [edit interfaces]
user@EX4400# set irb unit 10 family inet address 192.168.10.1/24
- [edit vlans]
- user@EX4400# set SALES vlan-id 10 l3-interface irb.10
- Why Juniper Transitioned to ELS IRB
The shift from vlan.unit to irb.unit was driven by architectural standardization. In large-scale enterprise and service provider networks, engineers frequently deploy both EX enterprise switches, QFX data center fabrics, and MX edge routers. By unifying the switching and routing syntax under irb , Junos OS enforces identical configuration hierarchies, operational verification commands, and automation scripts across all platforms. Furthermore, irb interfaces natively integrate with advanced architectures such as Virtual Routing and Forwarding (VRF) instances, EVPN-VXLAN overlays, and sophisticated firewall filter policies.