Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


show route terse


Syntax (EX Series Switches)


Display a high-level summary of the routes in the routing table.


For BGP routes, the show route terse command displays the local preference attribute and MED instead of the metric1 and metric2 values. This is mostly due to historical reasons.

To display the metric1 and metric2 value of a BGP route, use the show route extensive command.



Display a high-level summary of the routes in the routing table.

logical-system (all | logical-system-name)

(Optional) Perform this operation on all logical systems or on a particular logical system.

Required Privilege Level


Output Fields

Table 1 describes the output fields for the show route terse command. Output fields are listed in the approximate order in which they appear.

Table 1: show route terse Output Fields

Field Name

Field Description


Name of the routing table (for example, inet.0).

number destinations

Number of destinations for which there are routes in the routing table.

number routes

Number of routes in the routing table and total number of routes in the following states:

  • active (routes that are active)

  • holddown (routes that are in the pending state before being declared inactive)

  • hidden (routes that are not used because of a routing policy)

route key

Key for the state of the route:

  • +—A plus sign indicates the active route, which is the route installed from the routing table into the forwarding table.

  • - —A hyphen indicates the last active route.

  • *—An asterisk indicates that the route is both the active and the last active route. An asterisk before a to line indicates the best subpath to the route.


Active route. An asterisk (*) indicates this is the active route.


Validation status of the route:

  • ?—Not evaluated. Indicates that the route was not learned through BGP.

  • I—Invalid. Indicates that the prefix is found, but either the corresponding AS received from the EBGP peer is not the AS that appears in the database, or the prefix length in the BGP update message is longer than the maximum length permitted in the database.

  • N—Unknown. Indicates that the prefix is not among the prefixes or prefix ranges in the database.

  • V—Valid. Indicates that the prefix and autonomous system pair are found in the database.


Destination of the route.


Protocol through which the route was learned:

  • A—Aggregate

  • B—BGP

  • C—CCC

  • D—Direct


  • I—IS-IS

  • L—L2CKT, L2VPN, LDP, Local

  • K—Kernel


  • O—OSPF

  • P—PIM

  • R—RIP, RIPng

  • S—Static

  • T—Tunnel


Preference value of the route. In every routing metric except for the BGP LocalPref attribute, a lesser value is preferred. In order to use common comparison routines, Junos OS stores the 1's complement of the LocalPref value in the Preference2 field. For example, if the LocalPref value for Route 1 is 100, the Preference2 value is -101. If the LocalPref value for Route 2 is 155, the Preference2 value is -156. Route 2 is preferred because it has a higher LocalPref value and a lower Preference2 value.

Metric 1

First metric value in the route. For routes learned from BGP, this is the MED metric.

Metric 2

Second metric value in the route. For routes learned from BGP, this is the IGP metric.

Next hop

Next hop to the destination. An angle bracket (>) indicates that the route is the selected route.

AS path

AS path through which the route was learned. The letters at the end of the AS path indicate the path origin, providing an indication of the state of the route at the point at which the AS path originated:

  • I—IGP.

  • E—EGP.

  • ?—Incomplete; typically, the AS path was aggregated.

Sample Output

show route terse

Release Information

Command introduced before Junos OS Release 7.4.