pjhtech Tools
Juniper · Junos OS

Junos Route Lookup and VRF Routing Table Commands

Quick answer #

For the default IPv4 table, start with show route table inet.0 203.0.113.25. For a customer instance, specify its table, for example show route table CUSTOMER-A.inet.0 203.0.113.25. A route in the wrong table cannot explain the customer's actual forwarding decision.

Scope: Junos OS routing CLI, primarily MX. Applicable to supported EX/SRX routing features; SRX session policy and NAT require separate checks. Examples use the default routing context and an existing CUSTOMER-A instance.

Commands #

Read-only operational commands; addresses and instance names are examples:

Commands
Junos OS · Operational CLI

Read-only
show route summary
Read-only

Replace these example values: 203.0.113.25.

show route table inet.0 203.0.113.25
Read-only

Replace these example values: 203.0.113.0/24.

show route table inet.0 203.0.113.0/24 exact
Read-only

Replace these example values: 203.0.113.0/24.

show route table inet.0 203.0.113.0/24 exact extensive
Read-only

Replace these example values: CUSTOMER-A, 203.0.113.25.

show route table CUSTOMER-A.inet.0 203.0.113.25
Read-only

Replace these example values: 2001:db8:100::25.

show route table inet6.0 2001:db8:100::25
Read-only

Replace these example values: 203.0.113.25.

show route forwarding-table destination 203.0.113.25

The final command examines the default forwarding context. Do not use that result as evidence for CUSTOMER-A. Forwarding-table names and selectors are distinct from RIB names; inspect show route forwarding-table ? when working in another context.

Interpret the lookup #

A host-address lookup answers which matching route the routing table offers for that destination. An exact-prefix query answers a different question: whether that precise network and mask exist. A covering route can explain reachability even when the exact prefix is absent.

Read the protocol, preference, selected next hop and outgoing logical interface together. Several paths may exist for one prefix. The presence of a BGP path does not mean it is the active path. Extensive output supplies the detail needed to investigate why the router selected another candidate.

The routing table is the control-plane view. show route forwarding-table shows the Routing Engine's forwarding table; it is useful corroboration but is not a complete hardware forwarding validation on every platform. Do not describe it as direct proof that every Packet Forwarding Engine has programmed the path correctly.

Workflow for a missing customer route #

Write down the ingress interface, routing instance, address family and destination first. Run the lookup in that table. If the expected prefix is missing, follow its source: connected interface, static configuration or routing protocol. If it exists, inspect selection and next-hop resolution, then test the reverse path from the far end.

Pitfalls #

Avoid dumping a full Internet table when an exact query will do. A successful router-originated test can use a different source or instance than customer traffic. On SRX, a correct route is only one prerequisite; security policy, session state and translation can still determine the outcome. Preserve the original destination when investigating NAT.

Continue with #

Junos BGP Troubleshooting: Neighbors and Advertised Routes follows BGP advertisements; Junos OSPF Troubleshooting Commands and Neighbor States and Junos IS-IS Commands: Adjacencies, Levels and Metrics examine IGP learning. Use the subnet tools to confirm the prefix boundary before searching for an exact route.

Sources

Documentation reviewed: 8 October 2026