Supported Platforms
show route detail
Syntax
Syntax (EX Series Switches)
Release Information
Command introduced before Junos OS Release 7.4.
Command introduced in Junos OS Release 9.0 for EX Series switches.
Description
Display detailed information about the active entries in the routing tables.
Options
none | — | Display all active entries in the routing table on all systems. |
destination-prefix | — | (Optional) Display active entries for the specified address or range of addresses. |
logical-system (all | logical-system-name) | — | (Optional) Perform this operation on all logical systems or on a particular logical system. |
Required Privilege Level
view
List of Sample Output
show route detailshow route detail (with BGP Multipath)
Output Fields
Table 1 describes the output fields for the show route detail command. Output fields are listed in the approximate order in which they appear.
Table 1: show route detail Output Fields
Field Name | Field Description |
|---|---|
routing-table-name | 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:
|
route-destination (entry, announced) | 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:
|
label stacking | (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.
|
[protocol, preference] | Protocol from which the route was learned and the preference value for 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. |
Level | (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. |
Route Distinguisher | IP subnet augmented with a 64-bit prefix. |
Next-hop type | Type of next hop. For a description of possible values for this field, see Table 2. |
Next-hop reference count | Number of references made to the next hop. |
Flood nexthop branches exceed maximum message | 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. |
Source | IP address of the route source. |
Next hop | Network layer address of the directly reachable neighboring system. |
via | 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:
|
Label-switched-path lsp-path-name | Name of the LSP used to reach the next hop. |
Label operation | 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). |
Interface | (Local only) Local interface name. |
Protocol next hop | Network layer address of the remote routing device that advertised the prefix. This address is used to derive a forwarding next hop. |
Indirect next hop | Index designation used to specify the mapping between protocol next hops, tags, kernel export policy, and the forwarding next hops. |
State | State of the route (a route can be in more than one state). See Table 3. |
Local AS | AS number of the local routing device. |
Age | How long the route has been known. |
AIGP | Accumulated interior gateway protocol (AIGP) BGP attribute. |
Metricn | 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. |
MED-plus-IGP | Metric value for BGP path selection to which the IGP cost to the next-hop destination has been added. |
TTL-Action | 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. |
Task | Name of the protocol that has added the route. |
Announcement bits | List of protocols that announce this route. 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 | 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:
When AS path numbers are included in the route, the format is as follows:
Note: In Junos OS Release 10.3 and later, the AS path field displays an unrecognized attribute and associated hexadecimal value if BGP receives attribute 128 (attribute set) and you have not configured an independent domain in any routing instance. |
VC Label | MPLS label assigned to the Layer 2 circuit virtual connection. |
MTU | Maximum transmission unit (MTU) of the Layer 2 circuit. |
VLAN ID | VLAN identifier of the Layer 2 circuit. |
Prefixes bound to route | Forwarding equivalent class (FEC) bound to this route. Applicable only to routes installed by LDP. |
Communities | Community path attribute for the route. See Table 4 for all possible values for this field. |
Layer2-info: encaps | Layer 2 encapsulation (for example, VPLS). |
control flags | Control flags: none or Site Down. |
mtu | Maximum transmission unit (MTU) information. |
Label-Base, range | 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. |
status vector | Layer 2 VPN and VPLS network layer reachability information (NLRI). |
Accepted Multipath | Current active path when BGP multipath is configured. |
Accepted MultipathContrib | Path currently contributing to BGP multipath. |
Localpref | Local preference value included in the route. |
Router ID | BGP router ID as advertised by the neighbor in the open message. |
Primary Routing Table | In a routing table group, the name of the primary routing table in which the route resides. |
Secondary Tables | In a routing table group, the name of one or more secondary tables in which the route resides. |
Table 2 describes all possible values for the Next-hop Types output field.
Table 2: Next-hop Types Output Field Values
Next-Hop Type | Description |
|---|---|
Broadcast (bcast) | Broadcast next hop. |
Deny | Deny next hop. |
Discard | Discard next hop. |
Flood | 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. |
Hold | Next hop is waiting to be resolved into a unicast or multicast type. |
Indexed (idxd) | Indexed next hop. |
Indirect (indr) | 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. |
Interface | 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 (locl) | Local address on an interface. This next-hop type causes packets with this destination address to be received locally. |
Multicast (mcst) | Wire multicast next hop (limited to the LAN). |
Multicast discard (mdsc) | Multicast discard. |
Multicast group (mgrp) | Multicast group member. |
Receive (recv) | Receive. |
Reject (rjct) | Discard. An ICMP unreachable message was sent. |
Resolve (rslv) | Resolving next hop. |
Routed multicast (mcrt) | Regular multicast next hop. |
Router | 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:
|
Table | Routing table next hop. |
Unicast (ucst) | Unicast. |
Unilist (ulst) | List of unicast next hops. A packet sent to this next hop goes to any next hop in the list. |
Table 3 describes all possible values for the State output field. A route can be in more than one state (for example, <Active NoReadvrt Int Ext>).
Table 3: State Output Field Values
Value | Description |
|---|---|
Accounting | Route needs accounting. |
Active | Route is active. |
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. |
Clone | Route is a clone. |
Cluster list length | Length of cluster list sent by the route reflector. |
Delete | Route has been deleted. |
Ex | Exterior route. |
Ext | BGP route received from an external BGP neighbor. |
FlashAll | 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. |
Hidden | Route not used because of routing policy. |
IfCheck | Route needs forwarding RPF check. |
IGP metric | Path through next hop with lower IGP metric is available. |
Inactive reason | Flags for this route, which was not selected as best for a particular destination. |
Initial | Route being added. |
Int | Interior route. |
Int Ext | BGP route received from an internal BGP peer or a BGP confederation peer. |
Interior > Exterior > Exterior via Interior | Direct, static, IGP, or EBGP path is available. |
Local Preference | Path with a higher local preference value is available. |
Martian | Route is a martian (ignored because it is obviously invalid). |
MartianOK | Route exempt from martian filtering. |
Next hop address | Path with lower metric next hop is available. |
No difference | Path from neighbor with lower IP address is available. |
NoReadvrt | Route not to be advertised. |
NotBest | Route not chosen because it does not have the lowest MED. |
Not Best in its group | Incoming BGP AS is not the best of a group (only one AS can be the best). |
NotInstall | Route not to be installed in the forwarding table. |
Number of gateways | Path with a greater number of next hops is available. |
Origin | Path with a lower origin code is available. |
Pending | Route pending because of a hold-down configured on another route. |
Release | Route scheduled for release. |
RIB preference | Route from a higher-numbered routing table is available. |
Route Distinguisher | 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 lower preference value is available |
Router ID | Path through a neighbor with lower ID is available. |
Secondary | Route not a primary route. |
Unusable path | Path is not usable because of one of the following conditions:
|
Update source | Last tiebreaker is the lowest IP address value. |
Table 4 describes the possible values for the Communities output field.
Table 4: Communities Output Field Values
Value | Description |
|---|---|
area-number | 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. |
bandwidth: local AS number:link-bandwidth-number | 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. |
domain-id | Unique configurable number that identifies the OSPF domain. |
domain-id-vendor | Unique configurable number that further identifies the OSPF domain. |
link-bandwidth-number | Link-bandwidth number: from 0 through 4,294,967,295 (bytes per second). |
local AS number | Local AS number: from 1 through 65,535. |
options | 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. |
origin | (Used with VPNs) Identifies where the route came from. |
ospf-route-type | 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. |
route-type-vendor | 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. |
rte-type | 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. |
target | 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. |
unknown IANA | 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. |
unknown OSPF vendor community | Incoming IANA codes with a value above 0x8000. This code of the BGP extended community attribute is accepted, but it is not recognized. |
Sample Output
show route detail
user@host> show route detail
inet.0: 22 destinations, 23 routes (21 active, 0 holddown, 1 hidden)
10.10.0.0/16 (1 entry, 1 announced)
*Static Preference: 5
Next-hop reference count: 29
Next hop: 192.168.71.254 via fxp0.0, selected
State: <Active NoReadvrt Int Ext>
Local AS: 69
Age: 1:31:43
Task: RT
Announcement bits (2): 0-KRT 3-Resolve tree 2
AS path: I
10.31.1.0/30 (2 entries, 1 announced)
*Direct Preference: 0
Next hop type: Interface
Next-hop reference count: 2
Next hop: via so-0/3/0.0, selected
State: <Active Int>
Local AS: 69
Age: 1:30:17
Task: IF
Announcement bits (1): 3-Resolve tree 2
AS path: I
OSPF Preference: 10
Next-hop reference count: 1
Next hop: via so-0/3/0.0, selected
State: <Int>
Inactive reason: Route Preference
Local AS: 69
Age: 1:30:17 Metric: 1
Area: 0.0.0.0
Task: OSPF
AS path: I
10.31.1.1/32 (1 entry, 1 announced)
*Local Preference: 0
Next hop type: Local
Next-hop reference count: 7
Interface: so-0/3/0.0
State: <Active NoReadvrt Int>
Local AS: 69
Age: 1:30:20
Task: IF
Announcement bits (1): 3-Resolve tree 2
AS path: I
...
10.31.2.0/30 (1 entry, 1 announced)
*OSPF Preference: 10
Next-hop reference count: 9
Next hop: via so-0/3/0.0
Next hop: 10.31.1.6 via ge-3/1/0.0, selected
State: <Active Int>
Local AS: 69
Age: 1:29:56 Metric: 2
Area: 0.0.0.0
Task: OSPF
Announcement bits (2): 0-KRT 3-Resolve tree 2
AS path: I
...
224.0.0.2/32 (1 entry, 1 announced)
*PIM Preference: 0
Next-hop reference count: 18
State: <Active NoReadvrt Int>
Local AS: 69
Age: 1:31:45
Task: PIM Recv
Announcement bits (2): 0-KRT 3-Resolve tree 2
AS path: I
...
224.0.0.22/32 (1 entry, 1 announced)
*IGMP Preference: 0
Next-hop reference count: 18
State: <Active NoReadvrt Int>
Local AS: 69
Age: 1:31:43
Task: IGMP
Announcement bits (2): 0-KRT 3-Resolve tree 2
AS path: I
inet.3: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
10.255.70.103/32 (1 entry, 1 announced)
State: <FlashAll>
*RSVP Preference: 7
Next-hop reference count: 6
Next hop: 10.31.1.6 via ge-3/1/0.0 weight 0x1, selected
Label-switched-path green-r1-r3
Label operation: Push 100096
State: <Active Int>
Local AS: 69
Age: 1:25:49 Metric: 2
Task: RSVP
Announcement bits (2): 1-Resolve tree 1 2-Resolve tree 2
AS path: I
10.255.71.238/32 (1 entry, 1 announced)
State: <FlashAll>
*RSVP Preference: 7
Next-hop reference count: 6
Next hop: via so-0/3/0.0 weight 0x1, selected
Label-switched-path green-r1-r2
State: <Active Int>
Local AS: 69
Age: 1:25:49 Metric: 1
Task: RSVP
Announcement bits (2): 1-Resolve tree 1 2-Resolve tree 2
AS path: I
private__.inet.0: 2 destinations, 3 routes (2 active, 0 holddown, 0 hidden)
iso.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
47.0005.80ff.f800.0000.0108.0001.0102.5507.1052/152 (1 entry, 0 announced)
*Direct Preference: 0
Next hop type: Interface
Next-hop reference count: 1
Next hop: via lo0.0, selected
State: <Active Int>
Local AS: 69
Age: 1:31:44
Task: IF
AS path: I
mpls.0: 5 destinations, 5 routes (5 active, 0 holddown, 0 hidden)
0 (1 entry, 1 announced)
*MPLS Preference: 0
Next hop type: Receive
Next-hop reference count: 6
State: <Active Int>
Local AS: 69
Age: 1:31:45 Metric: 1
Task: MPLS
Announcement bits (1): 0-KRT
AS path: I
...
mpls.0: 5 destinations, 5 routes (5 active, 0 holddown, 0 hidden)
299776 (1 entry, 1 announced)
TSI:
KRT in-kernel 299776 /52 -> {Flood}
*RSVP Preference: 7
Next hop type: Flood
Next-hop reference count: 130
Flood nexthop branches exceed maximum
Address: 0x8ea65d0
...
800010 (1 entry, 1 announced)
*VPLS Preference: 7
Next-hop reference count: 2
Next hop: via vt-3/2/0.32769, selected
Label operation: Pop
State: <Active Int>
Age: 1:29:30
Task: Common L2 VC
Announcement bits (1): 0-KRT
AS path: I
vt-3/2/0.32769 (1 entry, 1 announced)
*VPLS Preference: 7
Next-hop reference count: 2
Next hop: 10.31.1.6 via ge-3/1/0.0 weight 0x1, selected
Label-switched-path green-r1-r3
Label operation: Push 800012, Push 100096(top)
Protocol next hop: 10.255.70.103
Push 800012
Indirect next hop: 87272e4 1048574
State: <Active Int>
Age: 1:29:30 Metric2: 2
Task: Common L2 VC
Announcement bits (2): 0-KRT 1-Common L2 VC
AS path: I
Communities: target:11111:1 Layer2-info: encaps:VPLS,
control flags:, mtu: 0
inet6.0: 5 destinations, 5 routes (5 active, 0 holddown, 0 hidden)
abcd::10:255:71:52/128 (1 entry, 0 announced)
*Direct Preference: 0
Next hop type: Interface
Next-hop reference count: 1
Next hop: via lo0.0, selected
State: <Active Int>
Local AS: 69
Age: 1:31:44
Task: IF
AS path: I
fe80::280:42ff:fe10:f179/128 (1 entry, 0 announced)
*Direct Preference: 0
Next hop type: Interface
Next-hop reference count: 1
Next hop: via lo0.0, selected
State: <Active NoReadvrt Int>
Local AS: 69
Age: 1:31:44
Task: IF
AS path: I
ff02::2/128 (1 entry, 1 announced)
*PIM Preference: 0
Next-hop reference count: 18
State: <Active NoReadvrt Int>
Local AS: 69
Age: 1:31:45
Task: PIM Recv6
Announcement bits (1): 0-KRT
AS path: I
ff02::d/128 (1 entry, 1 announced)
*PIM Preference: 0
Next-hop reference count: 18
State: <Active NoReadvrt Int>
Local AS: 69
Age: 1:31:45
Task: PIM Recv6
Announcement bits (1): 0-KRT
AS path: I
ff02::16/128 (1 entry, 1 announced)
*MLD Preference: 0
Next-hop reference count: 18
State: <Active NoReadvrt Int>
Local AS: 69
Age: 1:31:43
Task: MLD
Announcement bits (1): 0-KRT
AS path: I
private.inet6.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
fe80::280:42ff:fe10:f179/128 (1 entry, 0 announced)
*Direct Preference: 0
Next hop type: Interface
Next-hop reference count: 1
Next hop: via lo0.16385, selected
State: <Active NoReadvrt Int>
Age: 1:31:44
Task: IF
AS path: I
green.l2vpn.0: 4 destinations, 4 routes (4 active, 0 holddown, 0 hidden)
10.255.70.103:1:3:1/96 (1 entry, 1 announced)
*BGP Preference: 170/-101
Route Distinguisher: 10.255.70.103:1
Next-hop reference count: 7
Source: 10.255.70.103
Protocol next hop: 10.255.70.103
Indirect next hop: 2 no-forward
State: <Secondary Active Int Ext>
Local AS: 69 Peer AS: 69
Age: 1:25:49 Metric2: 1
AIGP 210
Task: BGP_69.10.255.70.103+179
Announcement bits (1): 0-green-l2vpn
AS path: I
Communities: target:11111:1 Layer2-info: encaps:VPLS,
control flags:, mtu: 0
Label-base: 800008, range: 8
Localpref: 100
Router ID: 10.255.70.103
Primary Routing Table bgp.l2vpn.0
10.255.71.52:1:1:1/96 (1 entry, 1 announced)
*L2VPN Preference: 170/-1
Next-hop reference count: 5
Protocol next hop: 10.255.71.52
Indirect next hop: 0 -
State: <Active Int Ext>
Age: 1:31:40 Metric2: 1
Task: green-l2vpn
Announcement bits (1): 1-BGP.0.0.0.0+179
AS path: I
Communities: Layer2-info: encaps:VPLS, control flags:Site-Down, mtu: 0
Label-base: 800016, range: 8, status-vector: 0x9F
10.255.71.52:1:5:1/96 (1 entry, 1 announced)
*L2VPN Preference: 170/-101
Next-hop reference count: 5
Protocol next hop: 10.255.71.52
Indirect next hop: 0 -
State: <Active Int Ext>
Age: 1:31:40 Metric2: 1
Task: green-l2vpn
Announcement bits (1): 1-BGP.0.0.0.0+179
AS path: I
Communities: Layer2-info: encaps:VPLS, control flags:, mtu: 0
Label-base: 800008, range: 8, status-vector: 0x9F
...
l2circuit.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
10.245.255.63:CtrlWord:4:3:Local/96 (1 entry, 1 announced)
*L2CKT Preference: 7
Next hop: via so-1/1/2.0 weight 1, selected
Label-switched-path my-lsp
Label operation: Push 100000[0]
Protocol next hop: 10.245.255.63 Indirect next hop: 86af000 296
State: <Active Int>
Local AS: 99
Age: 10:21
Task: l2 circuit
Announcement bits (1): 0-LDP
AS path: I
VC Label 100000, MTU 1500, VLAN ID 512
show route detail (with BGP Multipath)
user@host> show route detail
10.1.1.8/30 (2 entries, 1 announced)
*BGP Preference: 170/-101
Next hop type: Router, Next hop index: 262142
Address: 0x901a010
Next-hop reference count: 2
Source: 10.1.1.2
Next hop: 10.1.1.2 via ge-0/3/0.1, selected
Next hop: 10.1.1.6 via ge-0/3/0.5
State: <Active Ext>
Local AS: 1 Peer AS: 2
Age: 5:04:43
Task: BGP_2.10.1.1.2+59955
Announcement bits (1): 0-KRT
AS path: 2 I
Accepted Multipath
Localpref: 100
Router ID: 1.1.1.2
BGP Preference: 170/-101
Next hop type: Router, Next hop index: 678
Address: 0x8f97520
Next-hop reference count: 9
Source: 10.1.1.6
Next hop: 10.1.1.6 via ge-0/3/0.5, selected
State: <NotBest Ext>
Inactive reason: Not Best in its group - Active preferred
Local AS: 1 Peer AS: 2
Age: 5:04:43
Task: BGP_2.10.1.1.6+58198
AS path: 2 I
Accepted MultipathContrib
Localpref: 100
Router ID: 1.1.1.3
