show route extensive

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

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

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 destination (for example: 10.0.0.1/24). The entry value is the number of route for this destination, and the announced value is the number of routes being announced for this destination. Sometimes the route destination is presented in another format, such as:

• MPLS-label (for example, 80001 ).

• interface-name (for example, ge-1/0/2).

• neighbor-address:control-word-status:encapsulation type:vc-id:source (Layer 2 circuit only; for example, 10.1.1.195:NoCtrlWord:1:1:Local/96).

  • neighbor-address—Address of the neighbor.

  • control-word-status—Whether the use of the control word has been negotiated for this virtual circuit: NoCtrlWord or CtrlWord.

  • encapsulation type—Type of encapsulation, represented by a number: (1) Frame Relay DLCI, (2) ATM AAL5 VCC transport, (3) ATM transparent cell transport, (4) Ethernet, (5) VLAN Ethernet, (6) HDLC, (7) PPP, (8) ATM VCC cell transport, (10) ATM VPC cell transport.

  • vc-id—Virtual circuit identifier.

  • source—Source of the advertisement: Local or Remote.

Protocol header information.

(Next-to-the-last-hop routing device for MPLS only) Depth of the MPLS label stack, where the label-popping operation is needed to remove one or more labels from the top of the stack. A pair of routes is displayed, because the pop operation is performed only when the stack depth is two or more labels.

• S=0 route indicates that a packet with an incoming label stack depth of two or more exits this router with one fewer label (the label-popping operation is performed).

• If there is no S= information, the route is a normal MPLS route, which has a stack depth of 1 (the label-popping operation is not performed).

Protocol from which the route was learned and the preference value for 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.

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.

(IS-IS only). In IS-IS, a single autonomous system (AS) can be divided into smaller groups called areas. Routing between areas is organized hierarchically, allowing a domain to be administratively divided into smaller areas. This organization is accomplished by configuring Level 1 and Level 2 intermediate systems. Level 1 systems route within an area. When the destination is outside an area, they route toward a Level 2 system. Level 2 intermediate systems route between areas and toward other ASs.

IP subnet augmented with a 64-bit prefix.

Provider multicast service interface (MVPN routing table).

Type of next hop.

Number of references made to the next hop.

Indicates that the number of flood next-hop branches exceeded the system limit of 32 branches, and only a subset of the flood next-hop branches were installed in the kernel.

IP address of the route source.

Network layer address of the directly reachable neighboring system.

Interface used to reach the next hop. If there is more than one interface available to the next hop, the name of the interface that is actually used is followed by the word Selected. This field can also contain the following information:

• Weight—Value used to distinguish primary, secondary, and fast reroute backup routes. Weight information is available when MPLS label-switched path (LSP) link protection, node-link protection, or fast reroute is enabled, or when the standby state is enabled for secondary paths. A lower weight value is preferred. Among routes with the same weight value, load balancing is possible.

• Balance—Balance coefficient indicating how traffic of unequal cost is distributed among next hops when a routing device is performing unequal-cost load balancing. This information is available when you enable BGP multipath load balancing.

Name of the LSP used to reach the next hop.

MPLS label and operation occurring at this routing device. The operation can be pop (where a label is removed from the top of the stack), push (where another label is added to the label stack), or swap (where a label is replaced by another label).

Whether the metric has been increased or decreased by an offset value.

(Local only) Local interface name.

Network layer address of the remote routing device that advertised the prefix. This address is used to recursively derive a forwarding next hop.

MPLS label and operation occurring at this routing device. The operation can be pop (where a label is removed from the top of the stack), push (where another label is added to the label stack), or swap (where a label is replaced by another label).

When present, a list of nodes that are used to resolve the path to the next-hop destination, in the order that they are resolved.

When BGP PIC Edge is enabled, the output lines that contain Indirect next hop: weight follow next hops that the software can use to repair paths where a link failure occurs. The next-hop weight has one of the following values:

• 0x1 indicates active next hops.

• 0x4000 indicates passive next hops.

State of the route (a route can be in more than one state).

The BFD session ID number that represents the protection using MPLS fast reroute (FRR) and loop-free alternate (LFA).

Weight for the backup path. If the weight of an indirect next hop is larger than zero, the weight value is shown.

If the route is inactive, the reason for its current state is indicated. Typical reasons include:

• Active preferred—Currently active route was selected over this route.

• Always compare MED—Path with a lower multiple exit discriminator (MED) is available.

• AS path—Shorter AS path is available.

• Cisco Non-deterministic MED selection—Cisco nondeterministic MED is enabled and a path with a lower MED is available.

• Cluster list length—Path with a shorter cluster list length is available.

• Forwarding use only—Path is only available for forwarding purposes.

• IGP metric—Path through the next hop with a lower IGP metric is available.

• IGP metric type—Path with a lower OSPF link-state advertisement type is available.

• Interior > Exterior > Exterior via Interior—Direct, static, IGP, or EBGP path is available.

• Local preference—Path with a higher local preference value is available.

• Next hop address—Path with a lower metric next hop is available.

• No difference—Paths from all neighbors are identical for all necessary route attributes in some special scenarios, such as BGP L2VPN/VPLS, and there is no difference.

• Not Best in its group—Occurs when multiple peers of the same external AS advertise the same prefix and are grouped together in the selection process. When this reason is displayed, an additional reason is provided (typically one of the other reasons listed).

• Number of gateways—Path with a higher number of next hops is available.

• Origin—Path with a lower origin code is available.

• OSPF version—Path does not support the indicated OSPF version.

• RIB preference—Route from a higher-numbered routing table is available.

• Route destinguisher—64-bit prefix added to IP subnets to make them unique.

• Route metric or MED comparison—Route with a lower metric or MED is available.

• Route preference—Route with a lower preference value is available.

• Router ID—Path through a neighbor with a lower ID is available.

• Unusable path—Path is not usable because of one of the following conditions: the route is damped, the route is rejected by an import policy, or the route is unresolved.

• Update source—Last tiebreaker is the lowest IP address value.

Autonomous system (AS) number of the local routing device.

How long the route has been known.

Accumulated interior gateway protocol (AIGP) BGP attribute.

Cost value of the indicated route. For routes within an AS, the cost is determined by IGP and the individual protocol metrics. For external routes, destinations, or routing domains, the cost is determined by a preference value.

Metric value for BGP path selection to which the IGP cost to the next-hop destination has been added.

For MPLS LSPs, state of the TTL propagation attribute. Can be enabled or disabled for all RSVP-signaled and LDP-signaled LSPs or for specific VRF routing instances.

Name of the protocol that has added the route.

List of protocols that are consumers of the route. Using the following output as an example, Announcement bits (3): 0-KRT 5-Resolve tree 2 8-BGP RT Background there are (3) announcement bits to reflect the three clients (protocols) that have state for this route: Kernel (0-KRT), 5 (resolution tree process 2), and 8 (BGP).

The notation n-Resolve inet indicates that the route is used for route resolution for next hops found in the routing table. n is an index used by Juniper Networks customer support only.

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.

• Recorded—The AS path is recorded by the sample process (sampled).

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

When AS path numbers are included in the route, the format is as follows:

• [ ]—Brackets enclose the local AS number associated with the AS path if more than one AS number is configured on the routing device, or if AS path prepending is configured.

• { }—Braces enclose AS sets, which are groups of AS numbers in which the order does not matter. A set commonly results from route aggregation. The numbers in each AS set are displayed in ascending order.

• ( )—Parentheses enclose a confederation.

• ( [ ] )—Parentheses and brackets enclose a confederation set.

(BGP-learned routes) Validation status of the route:

• 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.

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

• Unverified—Indicates that origin validation is not enabled for the BGP peers.

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

Point-to-multipoint root address, multicast source address, and multicast group address when multipoint LDP (M-LDP) inband signaling is configured.

(For route reflected output only) Originator ID attribute set by the route reflector.

Indicates the status of a BGP route:

• Accepted—The specified BGP route is imported by the default BGP policy.

• Import—The route is imported into a Layer 3 VPN routing instance.

• Import-Protect—A remote instance egress that is protected.

• Multipath—A BGP multipath active route.

• MultipathContrib—The route is not active but contributes to the BGP multipath.

• Protect—An egress route that is protected.

• Stale—A route that is marked stale due to graceful restart.

When multipoint LDP with multicast-only fast reroute (MoFRR) is configured, the primary upstream path. MoFRR transmits a multicast join message from a receiver toward a source on a primary path, while also transmitting a secondary multicast join message from the receiver toward the source on a backup path.

When multipoint LDP with MoFRR is configured, the reverse-path forwarding (RPF) next-hop information. Data packets are received from both the primary path and the secondary paths. The redundant packets are discarded at topology merge points due to the RPF checks.

Multiple MPLS labels are used to control MoFRR stream selection. Each label represents a separate route, but each references the same interface list check. Only the primary label is forwarded while all others are dropped. Multiple interfaces can receive packets using the same label.

Value used to distinguish MoFRR primary and backup routes. A lower weight value is preferred. Among routes with the same weight value, load balancing is possible.

MPLS label assigned to the Layer 2 circuit virtual connection.

Maximum transmission unit (MTU) of the Layer 2 circuit.

VLAN identifier of the Layer 2 circuit.

(For route reflected output only) Cluster ID sent by the route reflector.

(For route reflected output only) Address of router that originally sent the route to the route reflector.

Forwarding Equivalent Class (FEC) bound to this route. Applicable only to routes installed by LDP.

Community path attribute for the route.

The DeletePending flag indicates that a BGP route needs to be processed due to a BGP peer down event.

Layer 2 encapsulation (for example, VPLS).

Control flags: none or Site Down.

Maximum transmission unit (MTU) information.

First label in a block of labels and label block size. A remote PE routing device uses this first label when sending traffic toward the advertising PE routing device.

Layer 2 VPN and VPLS network layer reachability information (NLRI).

Local preference value included in the route.

BGP router ID as advertised by the neighbor in the open message.

In a routing table group, the name of the primary routing table in which the route resides.

In a routing table group, the name of one or more secondary tables in which the route resides.

Name of the routing table whose active route was used to determine the forwarding next-hop entry in the resolution database. For example, in the case of inet.0 resolving through inet.0 and inet.3, this field indicates which routing table, inet.0 or inet.3, provided the best path for a particular prefix.

Number of nodes in the path.

Number of forwarding next hops. The forwarding next hop is the network layer address of the directly reachable neighboring system (if applicable) and the interface used to reach it.

Indicates the Kernel ID number and Statistics ID number.

Indicates the number of packets and data transferred.

Displays the origin validation information for each route entry and a reason code if the route is marked invalid. The possible reasons for an invalid route entry include mismatch due to origin-as or due to maximum-length.