close

keyboard_arrow_left

Table of Contents Expand all

list Table of Contents

English

show route forwarding-table

date_range 19-Nov-23

arrow_backward

arrow_forward

Syntax

content_copy zoom_out_map
show route forwarding-table 
<detail | extensive | summary> 
<all>
<ccc interface-name>
<destination destination-prefix>
<family family | matching matching>
<interface-name interface-name>
<label name>
<matching matching> 
<multicast> 
<table (default | logical-system-name/routing-instance-name | routing-instance-name)>
<vlan (all | vlan-name)>
<vpn vpn>

Syntax (MX Series Routers)

content_copy zoom_out_map
show route forwarding-table 
<detail | extensive | summary> 
<all>
<bridge-domain (all | domain-name)>
<ccc interface-name>
<destination destination-prefix>
<family family | matching matching>
<interface-name interface-name>
<label name>
<learning-vlan-id learning-vlan-id>
<matching matching> 
<multicast> 
<table (default | logical-system-name/routing-instance-name | routing-instance-name)>
<vlan (all |  vlan-name)>
<vpn vpn>

Syntax (TX Matrix and TX Matrix Plus Routers)

content_copy zoom_out_map
show route forwarding-table 
<detail | extensive | summary> 
<all>
<ccc interface-name>
<destination destination-prefix>
<family family | matching matching>
<interface-name interface-name>
<matching matching> 
<label name>
<lcc number>
<multicast> 
<table routing-instance-name>
<vpn vpn>

Description

Display the Routing Engine's forwarding table, including the network-layer prefixes and their next hops. This command is used to help verify that the routing protocol process has relayed the correction information to the forwarding table. The Routing Engine constructs and maintains one or more routing tables. From the routing tables, the Routing Engine derives a table of active routes, called the forwarding table.

Note:

The Routing Engine copies the forwarding table to the Packet Forwarding Engine, the part of the router that is responsible for forwarding packets. To display the entries in the Packet Forwarding Engine's forwarding table, use the show pfe route command.

Options

none	Display the routes in the forwarding tables. By default, the `show route forwarding-table` command does not display information about private, or internal, forwarding tables.
detail \| extensive \| summary	(Optional) Display the specified level of output.
all	(Optional) Display routing table entries for all forwarding tables, including private, or internal, tables.
bridge-domain (all \| `bridge-domain-name`)	(MX Series routers only) (Optional) Display route entries for all bridge domains or the specified bridge domain.
ccc `interface-name`	(Optional) Display route entries for the specified circuit cross-connect interface.
destination `destination-prefix`	(Optional) Destination prefix.
family `family`	(Optional) Display routing table entries for the specified family: `bridge (ccc \| destination \| detail \| extensive \| interface-name \| label \| learning-vlan-id \| matching \| multicast \| summary \| table \| vlan \| vpn)`, `ethernet-switching`, `evpn`, `fibre-channel`, `fmembers`, `inet`, `inet6`, `iso`, `mcsnoop-inet`, `mcsnoop-inet6`, `mpls`, `satellite-inet`, `satellite-inet6`, `satellite-vpls`, `tnp`, `unix`, `vpls`, or `vlan-classification`.
interface-name `interface-name`	(Optional) Display routing table entries for the specified interface.
label `name`	(Optional) Display route entries for the specified label.
lcc `number`	(TX Matrix and TX matrix Plus routers only) (Optional) On a routing matrix composed of a TX Matrix router and T640 routers, display information for the specified T640 router (or line-card chassis) connected to the TX Matrix router. On a routing matrix composed of the TX Matrix Plus router and T1600 or T4000 routers, display information for the specified router (line-card chassis) connected to the TX Matrix Plus router. Replace `number` with the following values depending on the LCC configuration: 0 through 3, when T640 routers are connected to a TX Matrix router in a routing matrix. 0 through 3, when T1600 routers are connected to a TX Matrix Plus router in a routing matrix. 0 through 7, when T1600 routers are connected to a TX Matrix Plus router with 3D SIBs in a routing matrix. 0, 2, 4, or 6, when T4000 routers are connected to a TX Matrix Plus router with 3D SIBs in a routing matrix.
learning-vlan-id `learning-vlan-id`	(MX Series routers only) (Optional) Display learned information for all VLANs or for the specified VLAN.
matching `matching`	(Optional) Display routing table entries matching the specified prefix or prefix length.
multicast	(Optional) Display routing table entries for multicast routes.
table	(Optional) Display route entries for all the routing tables in the main routing instance or for the specified routing instance. If your device supports logical systems, you can also display route entries for the specified logical system and routing instance. To view the routing instances on your device, use the `show route instance` command.
vlan (all \| `vlan-name`)	(Optional) Display information for all VLANs or for the specified VLAN.
vpn `vpn`	(Optional) Display routing table entries for a specified VPN.

Required Privilege Level

view

Output Fields

Table 1 lists the output fields for the show route forwarding-table command. Output fields are listed in the approximate order in which they appear. Field names might be abbreviated (as shown in parentheses) when no level of output is specified, or when the detail keyword is used instead of the extensive keyword.

Table 1: show route forwarding-table Output Fields
Field Name	Field Description	Level of Output
Logical system	Name of the logical system. This field is displayed if you specify the `table logical-system-name/routing-instance-name` option on a device that is configured for and supports logical systems.	All levels
Routing table	Name of the routing table (for example, inet, inet6, mpls).	All levels
Enabled protocols	The features and protocols that have been enabled for a given routing table. This field can contain the following values: BUM hashing—BUM hashing is enabled. MAC Stats—Mac Statistics is enabled. Bridging—Routing instance is a normal layer 2 bridge. No VLAN—No VLANs are associated with the bridge domain. All VLANs—The `vlan-id all` statement has been enabled for this bridge domain. Single VLAN—Single VLAN ID is associated with the bridge domain. MAC action drop—New MACs will be dropped when the MAC address limit is reached. Dual VLAN—Dual VLAN tags are associated with the bridge domain No local switching—No local switching is enabled for this routing instance.. Learning disabled—Layer 2 learning is disabled for this routing instance. MAC limit reached—The maximum number of MAC addresses that was configured for this routing instance has been reached. VPLS—The VPLS protocol is enabled. No IRB l2-copy—The no-irb-layer-2-copy feature is enabled for this routing instance. ACKed by all peers—All peers have acknowledged this routing instance. BUM Pruning—BUM pruning is enabled on the VPLS instance. Def BD VXLAN—VXLAN is enabled for the default bridge domain. EVPN—EVPN protocol is enabled for this routing instance. Def BD OVSDB—Open vSwitch Database (OVSDB) is enabled on the default bridge domain. Def BD Ingress replication—VXLAN ingress node replication is enabled on the default bridge domain. L2 backhaul—Layer 2 backhaul is enabled. FRR optimize—Fast reroute optimization MAC pinning—MAC pinning is enabled for this bridge domain. MAC Aging Timer—The MAC table aging time is set per routing instance. EVPN VXLAN—This routing instance supports EVPN with VXLAN encapsulation. PBBN—This routing instance is configured as a provider backbone bridged network. PBN—This routing instance is configured as a provider bridge network. ETREE—The ETREE protocol is enabled on this EVPN routing instance. ARP/NDP suppression—EVPN ARP NDP suppression is enabled in this routing instance. Def BD EVPN VXLAN—EVPN VXLAN is enabled for the default bridge domain. MPLS control word—Control word is enabled for this MPLS routing instance.	All levels
Address family	Address family (for example, `IP`, `IPv6`, `ISO`, `MPLS`, and `VPLS`).	All levels
Destination	Destination of the route.	`detail extensive`
Route Type (Type)	How the route was placed into the forwarding table. When the `detail` keyword is used, the route type might be abbreviated (as shown in parentheses): `cloned` (`clon`)—(TCP or multicast only) Cloned route. `destination` (`dest`)—Remote addresses directly reachable through an interface. `destination down` (`iddn`)—Destination route for which the interface is unreachable. `interface cloned` (`ifcl`)—Cloned route for which the interface is unreachable. `route down` (`ifdn`)—Interface route for which the interface is unreachable. `ignore` (`ignr`)—Ignore this route. `interface` (`intf`)—Installed as a result of configuring an interface. `permanent` (`perm`)—Routes installed by the kernel when the routing table is initialized. `user`—Routes installed by the routing protocol process or as a result of the configuration.	All levels
Route Reference (RtRef)	Number of routes to reference.	`detail extensive`
Flags	Route type flags: `none`—No flags are enabled. `accounting`—Route has accounting enabled. `cached`—Cache route. `incoming-iface interface-number`—Check against incoming interface. `prefix load balance`—Load balancing is enabled for this prefix. `rt nh decoupled`—Route has been decoupled from the next hop to the destination. `sent to PFE`—Route has been sent to the Packet Forwarding Engine. `static`—Static route.	`extensive`
Next hop	IP address of the next hop to the destination. Note: For static routes that use point-to-point (P2P) outgoing interfaces, the next-hop address is not displayed in the output.	`detail extensive`
Next hop Type (Type)	Next-hop type. When the `detail` keyword is used, the next-hop type might be abbreviated (as indicated in parentheses): `broadcast (bcst)`—Broadcast. `deny`—Deny. `discard (dscd)` —Discard. `hold`—Next hop is waiting to be resolved into a unicast or multicast type. `indexed (idxd)`—Indexed next hop. `indirect (indr)`—Indirect next hop. `local (locl)`—Local address on an interface. `routed multicast (mcrt)`—Regular multicast next hop. `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 the 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. `VxLAN Local`—EVPN Type 5 route in kernel.	`detail extensive`
Index	Software index of the next hop that is used to route the traffic for a given prefix.	`detail extensive` none
Route interface-index	Logical interface index from which the route is learned. For example, for interface routes, this is the logical interface index of the route itself. For static routes, this field is zero. For routes learned through routing protocols, this is the logical interface index from which the route is learned.	`extensive`
Reference (NhRef)	Number of routes that refer to this next hop.	`detail extensive` none
Next-hop interface (Netif)	Interface used to reach the next hop.	`detail extensive` none
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 (see the `Balance` field description).	`extensive`
Balance	Balance coefficient indicating how traffic of unequal cost is distributed among next hops when a router is performing unequal-cost load balancing. This information is available when you enable BGP multipath load balancing.	`extensive`
RPF interface	List of interfaces from which the prefix can be accepted. Reverse path forwarding (RPF) information is displayed only when `rpf-check` is configured on the interface.	`extensive`
sftw	On Junos OS Evolved devices, `sftw` is another type of next-hop. A software next-hop can contain a link to another single next-hop, and hence it often works as an indirect next-hop. The usage of `sftw` helps to reduce churn in Junos OS Evolved objects by providing a common object where topology updates can be reflected. Further MPLS states can also be attached to these software next-hops. When a route is created, a `sftw` next-hop seems to be created whether it is the management port or the loopback interface.	`detail extensive` none
Alternate forward nh index	Index number of the alternate next hop interface. Seen with multicast option only.	extensive
Next-hop L3 Interface	The next hop layer 3 interface. This option can be expressed as a VLAN name and is only seen with the multicast option.	extensive
Next-hop L2 Interfaces	The next hop layer 2 interfaces. Seen with multicast option only.	extensive

Sample Output

show route forwarding-table
show route forwarding-table detail
show route forwarding-table summary
show route forwarding-table extensive
show route forwarding-table ccc
show route forwarding-table family (MPLS)
show route forwarding-table family (IPv6)
show route forwarding-table label
show route forwarding-table matching
show route forwarding-table multicast