show route detail

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

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

( 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 2 or more exits this routing device 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.

Preference2 values are signed integers, that is, Preference2 values can be either positive or negative values. However, Junos OS evaluates Preference2 values as unsigned integers that are represented by positive values. Based on the Preference2 values, Junos OS evaluates a preferred route differently in the following scenarios:

• Both Signed Preference2 values

  • Route A = -101

  • Route B = -156

  Where both the Preference2 values are signed, Junos OS evaluates only the unsigned value of Preference2 and Route A, which has a lower Preference2 value is preferred.

• Unsigned Preference2 values

  Now consider both unsigned Preference2 values:

  • Route A = 4294967096

  • Route B = 200

  Here, Junos OS considers the lesser Preference2 value and Route B with a Preference2 value of 200 is preferred because it is less than 4294967096.

• Combination of signed and unsigned Preference2 values

  When Preference2 values of two routes are compared, and for one route the Preference2 is a signed value, and for the other route it is an unsigned value, Junos OS prefers the route with the positive Preference2 value over the negative Preference2 value. For example, consider the following signed and unsigned Preference2 values:

  • Route A = -200

  • Route B = 200

  In this case, Route B with a Preference2 value of 200 is preferred although this value is greater than -200, because Junos OS evaluates only the unsigned value of the Preference2 value.

(IS-IS only). In IS-IS, a single 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. For a description of possible values for this field, see Table 2.

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

(Local only) Local interface name.

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

Index designation used to specify the mapping between protocol next hops, tags, kernel export policy, and the forwarding next hops.

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

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.

For sample output, see show route table .

Name of the protocol that has added the route.

The number of BGP peers or protocols to which Junos OS has announced this route, followed by the list of the recipients of the announcement. Junos OS can also announce the route to the KRT for installing the route into the Packet Forwarding Engine, to a resolve tree, a L2 VC, or even a VPN. For example, n-Resolve inet indicates that the specified route is used for route resolution for next hops found in the routing table.

• n—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 number that precedes the AS path. This number represents the number of ASs present in the AS path, when calculated as defined in RFC 4271. This value is used in the AS-path merge process, as defined in RFC 4893.

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

• { }—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 the origin of the prefix is not verified against the database. This is because the database got populated and the validation is not called for in the BGP import policy, although origin validation is enabled, or the origin validation is not enabled for the BGP peers.

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

Displays the optimal route reflection (ORR) generation identifier. ISIS and OSPF interior gateway protocol (IGP) updates filed whenever any of the corresponding ORR route has its metric valued changed, or if the ORR route is added or deleted.

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

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.

Forwarding equivalent class (FEC) bound to this route. Applicable only to routes installed by LDP.

Community path attribute for the route. See Table 4 for all possible values for this field.

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

Current active path when BGP multipath is configured.

The LongLivedStale flag indicates that the route was marked LLGR-stale by this router, as part of the operation of LLGR receiver mode. Either this flag or the LongLivedStaleImport flag may be displayed for a route. Neither of these flags are displayed at the same time as the Stale (ordinary GR stale) flag.

The LongLivedStaleImport flag indicates that the route was marked LLGR-stale when it was received from a peer, or by import policy. Either this flag or the LongLivedStale flag may be displayed for a route. Neither of these flags are displayed at the same time as the Stale (ordinary GR stale) flag.

Accept all received BGP long-lived graceful restart (LLGR) and LLGR stale routes learned from configured neighbors and import into the inet.0 routing table

Accept all received BGP long-lived graceful restart (LLGR) and LLGR stale routes learned from configured neighbors and imported into the inet.0 routing table

The LongLivedStaleImport flag indicates that the route was marked LLGR-stale when it was received from a peer, or by import policy.

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

Path currently contributing to BGP multipath.

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.

Indicates the Kernel ID number and Statistics ID number.

Indicates the number of packets and data transferred.

Broadcast next hop.

Deny next hop.

Discard next hop.

Dynamic list next hop

Flood next hop. Consists of components called branches, up to a maximum of 32 branches. Each flood next-hop branch sends a copy of the traffic to the forwarding interface. Used by point-to-multipoint RSVP, point-to-multipoint LDP, point-to-multipoint CCC, and multicast.

Next hop is waiting to be resolved into a unicast or multicast type.

Indexed next hop.

Used with applications that have a protocol next hop address that is remote. You are likely to see this next-hop type for internal BGP (IBGP) routes when the BGP next hop is a BGP neighbor that is not directly connected.

Used for a network address assigned to an interface. Unlike the router next hop, the interface next hop does not reference any specific node on the network.

Local address on an interface. This next-hop type causes packets with this destination address to be received locally.

Wire multicast next hop (limited to the LAN).

Multicast discard.

Multicast group member.

Receive.

Discard. An ICMP unreachable message was sent.

Resolving next hop.

Regular multicast next hop.

A specific node or set of nodes to which the routing device forwards packets that match the route prefix.

To qualify as next-hop type router, the route must meet the following criteria:

• Must not be a direct or local subnet for the routing device.

• Must have a next hop that is directly connected to the routing device.

Next hop added to the Routing Engine forwarding table for remote IP addresses with prefix /32 for Junos OS Evolved only.

Routing table next hop.

Unicast.

List of unicast next hops. A packet sent to this next hop goes to any next hop in the list.

Route needs accounting.

Route is active.

Path with a lower multiple exit discriminator (MED) is available.

Shorter AS path is available.

Cisco nondeterministic MED is enabled, and a path with a lower MED is available.

Route is a clone.

Length of cluster list sent by the route reflector.

Route has been deleted.

Exterior route.

BGP route received from an external BGP neighbor.

Forces all protocols to be notified of a change to any route, active or inactive, for a prefix. When not set, protocols are informed of a prefix only when the active route changes.

Route not used because of routing policy.

Route needs forwarding RPF check.

Path through next hop with lower IGP metric is available.

Flags for this route, which was not selected as best for a particular destination.

Route being added.

Interior route.

BGP route received from an internal BGP peer or a BGP confederation peer.

Direct, static, IGP, or EBGP path is available.

Path with a higher local preference value is available.

Route is a martian (ignored because it is obviously invalid).

Route exempt from martian filtering.

Path with lower metric next hop is available.

Path from neighbor with lower IP address is available.

Route not to be advertised.

Route not chosen because it does not have the lowest MED.

Incoming BGP AS is not the best of a group (only one AS can be the best).

Route not to be installed in the forwarding table.

Route added by non-NSR supported protocols.

Path with a greater number of next hops is available.

Path with a lower origin code is available.

Route pending because of a hold-down configured on another route.

Route installed programatically by on-box or off-box applications using API.

Indicates paths requesting protection.

Indicates the route entry that can be used as a protection path.

Route scheduled for release.

Route from a higher-numbered routing table is available.

64-bit prefix added to IP subnets to make them unique.

Route with a lower metric or MED is available.

Route with lower preference value is available

Path through a neighbor with lower ID is available.

Route not a primary route.

Path is not usable because of one of the following conditions:

• The route is damped.

• The route is rejected by an import policy.

• The route is unresolved.

Last tiebreaker is the lowest IP address value.

4 bytes, encoding a 32-bit area number. For AS-external routes, the value is 0. A nonzero value identifies the route as internal to the OSPF domain, and as within the identified area. Area numbers are relative to a particular OSPF domain.

Link-bandwidth community value used for unequal-cost load balancing. When BGP has several candidate paths available for multipath purposes, it does not perform unequal-cost load balancing according to the link-bandwidth community unless all candidate paths have this attribute.

Unique configurable number that identifies the OSPF domain.

Unique configurable number that further identifies the OSPF domain.

Link-bandwidth number: from 0 through 4,294,967,295 (bytes per second).

Local AS number: from 1 through 65,535.

1 byte. Currently this is only used if the route type is 5 or 7. Setting the least significant bit in the field indicates that the route carries a type 2 metric.

(Used with VPNs) Identifies where the route came from.

1 byte, encoded as 1 or 2 for intra-area routes (depending on whether the route came from a type 1 or a type 2 LSA); 3 for summary routes; 5 for external routes (area number must be0); 7 for NSSA routes; or 129 for sham link endpoint addresses.

Displays the area number, OSPF route type, and option of the route. This is configured using the BGP extended community attribute 0x8000. The format is area-number:ospf-route-type:options.

Displays the area number, OSPF route type, and option of the route. This is configured using the BGP extended community attribute 0x0306. The format is area-number:ospf-route-type:options.

Defines which VPN the route participates in; target has the format 32-bit IP address:16-bit number. For example, 10.19.0.0:100.

Defines the source of the IPv6 unicast address in a policy match condition.

Defines the VPN IPv6 target unicast address used in a policy match condition. The target has the 128-bit IP address:16-bit number format.

For example, 2001:db8:9999::9.

Defines the extended format of the IPv6 unicast address in a policy match. For example, ipv6-extended:203:<2001:db8::7>:67

Incoming IANA codes with a value between 0x1 and 0x7fff. This code of the BGP extended community attribute is accepted, but it is not recognized.

Incoming IANA codes with a value above 0x8000. This code of the BGP extended community attribute is accepted, but it is not recognized.

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.