Study guide

6.2 Routing Instances and RIB Groups

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

6.2 Routing Instances and RIB Groups

Key Takeaways Explain This Topic AI

Routing instances virtualize Layer 3 routing environments on a single Junos device, isolating routing tables, protocols, and interfaces into discrete security and administrative domains.

The primary routing instance types in enterprise networks are virtual-router (independent routing tables and protocols without MPLS overhead), vrf (MPLS Layer 3 VPNs requiring RD and RT), and forwarding (used exclusively for Filter-Based Forwarding).

Junos stores global IPv4 unicast routes in inet.0, while custom routing instances maintain dedicated routing tables designated as <instance-name> .inet.0 and <instance-name> .inet6.0.

RIB groups provide a controlled mechanism to duplicate and import routes from an originating routing table into one or more destination routing tables simultaneously.

In a RIB group import-rib list, the first table listed must strictly be the primary table where the routes originate, followed by the target secondary tables.

Last updated: October 2026

Routing Instances and RIB Groups

Enterprise campus backbones and data center fabrics frequently demand strict traffic separation across departmental tenants, guest users, out-of-band management systems, and regulatory environments. Junos OS addresses these multi-tenancy requirements through Routing Instances , which virtualize routing tables and protocols on a single physical chassis. To facilitate controlled communication between isolated instances without deploying external physical loopback cables, Junos provides Routing Information Base (RIB) Groups to selectively replicate and leak routes between tables.

1. Virtualization of Routing & Instance Architecture

A routing instance is a collection of routing tables, interfaces, and routing protocol processes running inside an isolated administrative domain. In the default configuration, all physical and logical interfaces belong to the global default routing instance , whose primary IPv4 unicast routing table is inet.0 .

Junos Standard Routing Tables

Junos OS organizes routes into distinct tables based on protocol family and forwarding purpose: +---------------------------------------------------------------------------------------------------+

  • | JUNOS STANDARD ROUTING INFORMATION BASES (RIBS) |
  • +-----------------------+---------------------------------------------------------------------------+
  • | Routing Table Name | Primary Protocol / Forwarding Purpose |
  • +-----------------------+---------------------------------------------------------------------------+
  • | inet.0 | Default global IPv4 unicast routing table |
  • | inet6.0 | Default global IPv6 unicast routing table |
  • | inet.1 | IPv4 multicast forwarding cache (reverse-path forwarding checks) |
  • | inet.2 | IPv4 multicast BGP (MBGP) routes used for RPF verification |
  • | inet.3 | MPLS path calculation table storing RSVP/LDP Label Switched Paths (LSPs) |
  • | mpls.0 | MPLS label switching and swap/pop operations |
  • | <instance>.inet.0 | Custom IPv4 unicast routing table for the specified user routing instance |
  • | <instance>.inet6.0 | Custom IPv6 unicast routing table for the specified user routing instance |
  • +-----------------------+---------------------------------------------------------------------------+

When a user creates a routing instance named corp-vr , Junos automatically instantiates a dedicated routing table named corp-vr.inet.0 . Routes inside corp-vr.inet.0 are completely hidden from inet.0 and from any other custom routing instance, ensuring complete tenant isolation.

2. Routing Instance Types

Junos OS supports multiple routing instance types, each tailored to specific networking architectures. The three instance types tested heavily on the JNCIS-ENT examination are virtual-router , vrf , and forwarding :

Instance Type Protocol Support Requires MPLS? Requires RD / RT? Primary Enterprise Application

virtual-router Runs independent instances of OSPF, BGP, IS-IS, RIP, and static routing. No No Enterprise campus segmentation, departmental segregation, guest Wi-Fi isolation, and security perimeter zoning.

vrf Runs independent routing protocols across customer sites. Yes Yes (Route Distinguisher and Route Targets mandatory) MPLS Layer 3 VPNs (RFC 4364) deployed over service provider cores or large enterprise MPLS backbones.

forwarding No dynamic routing protocols. Contains only static routes and leaked RIB entries. No No Filter-Based Forwarding (FBF) . Used strictly to direct classified packets to alternative next-hops.

Configuring a virtual-router Instance

In campus networks, virtual-router is the most common deployment model because it does not require configuring MPLS signaling, BGP Route Distinguishers (RD), or Route Targets (RT): [edit routing-instances guest-network]

  • user@router# set instance-type virtual-router
  • user@router# set interface ge-0/0/2.0
  • user@router# set interface irb.200
  • user@router# set routing-options static route 0.0.0.0/0 next-hop 192.168.200.254
  • user@router# set protocols ospf area 0.0.0.0 interface irb.200

When ge-0/0/2.0 and irb.200 are bound to guest-network , their connected subnet routes are automatically placed into guest-network.inet.0 rather than the global inet.0 . OSPF protocol packets received on irb.200 are processed strictly within the guest-network OSPF database.

3. RIB Groups: Architecture and Route Leaking Mechanics

While instance isolation provides strong network boundaries, real-world enterprise architectures often require controlled inter-instance communication. For instance, isolated departmental virtual routers may require access to shared corporate DNS, Active Directory, or central internet proxy services located in inet.0 .

A RIB Group is a Junos configuration structure that intercepts routes learned by a protocol, static route definition, or interface discovery process and inserts copies of those routes into multiple routing tables simultaneously.

The import-rib Statement and The Golden Ordering Rule

A RIB group is declared under the [edit routing-options rib-groups] hierarchy: [edit routing-options rib-groups share-internet]

user@router# set import-rib [ inet.0 corp-vr.inet.0 guest-network.inet.0 ]

The Mandatory Golden Ordering Rule: The first table declared in the import-rib list must strictly be the primary routing table where the routes originate! If you are leaking routes from inet.0 into corp-vr.inet.0 , inet.0 must be the first element in the bracketed list. If you reverse the order, Junos will attempt to import routes from the secondary table into the primary table, resulting in commit failures or severe route propagation anomalies.

Controlling Leaked Routes with import-policy

Without an import policy, a RIB group duplicates all routes learned by the parent protocol into every listed table. To maintain the principle of least privilege, an import-policy should always be applied to filter specifically permitted prefixes: [edit policy-options policy-statement permit-dns-proxy]

  • user@router# set term allow-shared from route-filter 192.168.100.0/24 exact
  • user@router# set term allow-shared then accept
  • user@router# set term reject-others then reject
  • [edit routing-options rib-groups share-internet]
  • user@router# set import-policy permit-dns-proxy
  • 4. Leaking Interface Routes and Protocol Routes

A critical trap on the JNCIS-ENT exam involves interface routes ( direct and local ). When a static route is leaked from inet.0 into corp-vr.inet.0 , the router in corp-vr may know the remote prefix, but it cannot resolve the next-hop IP address if the connected interface subnet resides only in inet.0 .

Sharing Connected Subnets via interface-routes

To ensure next-hop ARP resolution succeeds across instances, interface routes must be added to the RIB group via the interface-routes hierarchy: [edit routing-options]

  • user@router# set rib-groups leak-interfaces import-rib [ inet.0 corp-vr.inet.0 ]
  • user@router# set interface-routes rib-group inet leak-interfaces

This configuration ensures that all directly connected subnets in inet.0 are mirrored into corp-vr.inet.0 , allowing the Packet Forwarding Engine to construct valid Layer 2 frame headers for leaked transit next-hops.

Applying RIB Groups to Dynamic Routing Protocols

RIB groups can also be attached directly to dynamic routing protocols to mirror protocol-learned routes into secondary tables: [edit protocols ospf]

user@router# set rib-group ospf-to-corp

  • [edit protocols bgp group external-peers]
  • user@router# set family inet unicast rib-group bgp-to-corp
  • 5. Architectural Gotchas & Troubleshooting

Asymmetric Routing and One-Way Leaking: Leaking routes from inet.0 into corp-vr.inet.0 allows hosts in corp-vr to send packets toward global servers. However, unless reverse routes pointing back to corp-vr subnets are leaked into inet.0 (or a default gateway is present), return traffic from the global servers will be discarded. A valid return route is required; it can be learned or configured without necessarily using a second leak in every design.

Hidden Routes: If a leaked route does not appear in show route table <instance>.inet.0 , issue show route table <instance>.inet.0 hidden detail . An unresolved next-hop (due to missing interface routes) is the most frequent cause of hidden leaked routes.

Instance Deletion Traps: Removing an interface from a routing instance immediately returns that interface to the default global instance ( inet.0 ), which may unintentionally expose sensitive networks to global traffic.

  • Operational Verification Commands user@router> show route table corp-vr.inet.0
  • user@router> show route instance detail corp-vr
  • user@router> show configuration routing-options rib-groups share-internet
  • user@router> show interfaces terse routing-instance guest-network

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.

Loading diagram... Junos RIB Group Route Leaking Architecture