show route resolution
Syntax
show route resolution <brief | detail | extensive | summary> <index index> <logical-system (all | logical-system-name)> <prefix> <table routing-table-name> <unresolved>
Syntax (EX Series Switches)
show route resolution <brief | detail | extensive | summary> <index index> <prefix> <table routing-table-name> <unresolved>
Description
Display the entries in the next-hop resolution database. This database provides for recursive resolution of next hops through other prefixes in the routing table.
Options
none | Display standard information about all entries in the next-hop resolution database. |
brief | detail | extensive | summary | (Optional) Display the specified level of output. |
index index | (Optional) Show the index of the resolution tree. |
logical-system (all | logical-system-name) | (Optional) Perform this operation on all logical systems or on a particular logical system. |
prefix network/destination-prefix | (Optional) Display database entries for the specified address. |
table routing-table-name | (Optional) Display information about a particular routing table (for example, inet.0) where policy-based export is currently enabled. |
unresolved | (Optional) Display routes that could not be resolved. |
Required Privilege Level
view
Output Fields
Table 1 describes the output fields for the show route resolution
command. Output fields are listed in the approximate order in which
they appear.
Field Name |
Field Description |
---|---|
routing-table-name |
Name of the routing table whose prefixes are resolved using the entries in the route resolution database. For routing table groups, this is the name of the primary routing table whose prefixes are resolved using the entries in the route resolution database. |
Tree index |
Tree index identifier. |
Nodes |
Number of nodes in the tree. |
Reference count |
Number of references made to the next hop. |
Contributing routing tables |
Routing tables used for next-hop resolution. |
Originating RIB |
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. |
Metric |
Metric associated with the forwarding next hop. |
Node path count |
Number of nodes in the path. |
Forwarding next hops |
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. Merged—Merged next hops when recursive resolution of multipath is configured. |
Sample Output
- show route resolution detail
- show route resolution (Multipath Resolution)
- show route resolution summary
- show route resolution unresolved
show route resolution detail
user@host> show route resolution detail Tree Index: 1, Nodes 0, Reference Count 1 Contributing routing tables: inet.3 Tree Index: 2, Nodes 23, Reference Count 1 Contributing routing tables: inet.0 inet.3 10.10.0.0/16 Originating RIB: inet.0 Node path count: 1 Forwarding nexthops: 1 10.31.1.0/30 Originating RIB: inet.0 Node path count: 1 Forwarding nexthops: 1 10.31.1.1/32 Originating RIB: inet.0 Node path count: 1 Forwarding nexthops: 0 10.31.1.4/30 Originating RIB: inet.0 Node path count: 1 Forwarding nexthops: 1 10.31.1.5/32 Originating RIB: inet.0 Node path count: 1 Forwarding nexthops: 0 10.31.2.0/30 Originating RIB: inet.0 Metric: 2 Node path count: 1 Forwarding nexthops: 2 10.31.11.0/24 Originating RIB: inet.0 Node path count: 1 Forwarding nexthops: 1
show route resolution (Multipath Resolution)
user@host> show route resolution detail user@host> show route resolution detail 10.1.1.2 Tree Index: 1, Nodes 36, Reference Count 3 Contributing routing tables: inet.0 inet.3 Policy: [ abc ] 10.1.1.2/32 Originating RIB: inet.0 Node path count: 1 Next hop subtype: INDIRECT Indirect next hops: 2 Protocol next hop: 10.1.1.1 Inode flags: 0x206 path flags: 0x08 Path fnh link: 0xc9321c0 path inh link: 0x0 Indirect next hop: 0xb2b20f0 1048574 INH Session ID: 0x143 Indirect path forwarding next hops: 1 Next hop type: Router Next hop: 12.1.1.2 via ge-2/0/1.0 Session Id: 0x144 Next hop: 13.1.1.2 via ge-2/0/2.0 Session Id: 0x145 10.1.1.1/32 Originating RIB: inet.0 Node path count: 1 Node flags: 1 Forwarding nexthops: 1 (Merged) Nexthop: 12.1.1.2 via ge-2/0/1.0 Nexthop: 13.1.1.2 via ge-2/0/2.0 user@host> show route resolution summary Tree Index: 1, Nodes 7, Reference Count 2 Contributing routing tables: inet.3 Tree Index: 2, Nodes 7, Reference Count 8213 Contributing routing tables: inet.3 Policy: [ RRwM ] Tree Index: 3, Nodes 7, Reference Count 2 Contributing routing tables: inet6.3 Tree Index: 4, Nodes 1, Reference Count 1 Contributing routing tables: iso.0 Tree Index: 5, Nodes 1000061, Reference Count 13 Contributing routing tables: inet.0 inet.3 Policy: [ Community-RRwM ] Tree Index: 6, Nodes 2013, Reference Count 6 Contributing routing tables: inet6.0 inet6.3 Policy: [ RRwM ] Tree Index: 7, Nodes 7, Reference Count 1501 Contributing routing tables: inet6.3 Policy: [ RRwM ] Tree Index: 8, Nodes 1000061, Reference Count 2 Contributing routing tables: inet.0 inet.3 Policy: [ RRwM ]
show route resolution summary
user@host> show route resolution summary Tree Index: 1, Nodes 24, Reference Count 1 Contributing routing tables: :voice.inet.0 :voice.inet.3 Tree Index: 2, Nodes 2, Reference Count 1 Contributing routing tables: inet.3 Tree Index: 3, Nodes 43, Reference Count 1 Contributing routing tables: inet.0 inet.3
show route resolution unresolved
user@host> show route resolution unresolved Tree Index 1 vt-3/2/0.32769.0 /16 Protocol Nexthop: 10.255.71.238 Push 800000 Indirect nexthop: 0 - vt-3/2/0.32772.0 /16 Protocol Nexthop: 10.255.70.103 Push 800008 Indirect nexthop: 0 - Tree Index 2
Release Information
Command introduced before Junos OS Release 7.4.