Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

TechLibrary
Navigation

Supported Platforms

 

Related Documentation

 

show route table

List of Syntax

Syntax
Syntax (EX Series Switches)

Syntax

show route table routing-table-name <brief | detail | extensive | terse><logical-system (all | logical-system-name)>

Syntax (EX Series Switches)

show route table routing-table-name <brief | detail | extensive | terse>

Release Information

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.

Description

Display the route entries in a particular routing table.

Options

brief | detail | extensive | terse
—

(Optional) Display the specified level of output.

logical-system (all | logical-system-name)
—

(Optional) Perform this operation on all logical systems or on a particular logical system.

routing-table-name
—

Display route entries for all routing tables whose name begins with this string (for example, inet.0 and inet6.0 are both displayed when you run the show route table inet command).

Required Privilege Level

view

 

Related Documentation

 

List of Sample Output

show route table bgp.l2.vpn
show route table bgp.l3vpn.0
show route table bgp.l3vpn.0 detail
show route table bgp.rtarget.0 (When Proxy BGP Route Target Filtering Is Configured)
show route table inet.0
show route table inet6.0
show route table inet6.3
show route table inetflow detail
show route table l2circuit.0
show route table mpls
show route table mpls extensive
show route table mpls.0
show route table mpls.0 (RSVP Route—Transit LSP)
show route table vpls_1 detail
show route table vpn-a
show route table vpn-a.mdt.0
show route table VPN-A detail
show route table VPN-AB.inet.0
show route table VPN_blue.mvpn-inet6.0
show route table VPN-A detail
show route table inetflow detail

Output Fields

Table 1 describes the output fields for the show route table command. Output fields are listed in the approximate order in which they appear.

Table 1: show route table Output Fields

Field Name

Field Description

routing-table-name

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

Restart complete

All protocols have restarted for this routing table.

Restart state:

  • Pending:protocol-name—List of protocols that have not yet completed graceful restart for this routing table.
  • Complete—All protocols have restarted for this routing table.

For example, if the output shows-

  • LDP.inet.0             : 5 routes (4 active, 1 holddown, 0 hidden)
    Restart Pending: OSPF LDP VPN
    This indicates that OSPF, LDP, and VPN protocols did not restart for LDP.inet.0 routing table.
  • vpls_1.l2vpn.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
Restart Complete
    This indicates that all protocols have restarted for vpls_1.l2vpn.0 routing table.

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:

  • 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 (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:

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

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.

  • 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, preference]

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.

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.

PMSI

Provider multicast service interface (MVPN routing table).

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:

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

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.

Task

Name of the protocol that has added the route.

Announcement bits

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

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.

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.

validation-state

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

FECs bound to route

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

Primary Upstream

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.

RPF Nexthops

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.

Label

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.

weight

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.

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 LongLivedStale

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.

Accepted LongLivedStaleImport

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

ImportAccepted LongLivedStaleImport

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.

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:

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

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:

  • The route is damped.
  • The route is rejected by an import policy.
  • The route is unresolved.

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 table bgp.l2.vpn

user@host> show route table bgp.l2.vpn 
bgp.l2vpn.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

192.168.24.1:1:4:1/96
                   *[BGP/170] 01:08:58, localpref 100, from 192.168.24.1
                      AS path: I
                    > to 10.0.16.2 via fe-0/0/1.0, label-switched-path am

show route table bgp.l3vpn.0

user@host> show route table bgp.l3vpn.0 
      bgp.l3vpn.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden) 
      + = Active Route, - = Last Active, * = Both 
     
      10.255.71.15:100:10.255.71.17/32 
                         *[BGP/170] 00:03:59, MED 1, localpref 100, from 
      10.255.71.15 
                            AS path: I 
                          > via so-2/1/0.0, Push 100020, Push 100011(top) 
      10.255.71.15:200:10.255.71.18/32 
                         *[BGP/170] 00:03:59, MED 1, localpref 100, from 
      10.255.71.15 
                            AS path: I 
                          > via so-2/1/0.0, Push 100021, Push 100011(top)

show route table bgp.l3vpn.0 detail

user@host> show route table bgp.l3vpn.0 detail 
bgp.l3vpn.0: 8 destinations, 8 routes (8 active, 0 holddown, 0 hidden)

10.255.245.12:1:4.0.0.0/8 (1 entry, 1 announced)
  *BGP   Preference: 170/-101
         Route Distinguisher: 10.255.245.12:1
         Source: 10.255.245.12
         Next hop: 192.168.208.66 via fe-0/0/0.0, selected
         Label operation: Push 182449
         Protocol next hop: 10.255.245.12
         Push 182449
         Indirect next hop: 863a630 297
         State: <Active Int Ext>
         Local AS:    35 Peer AS:    35
         Age: 12:19      Metric2: 1 
         Task: BGP_35.10.255.245.12+179
         Announcement bits (1): 0-BGP.0.0.0.0+179 
         AS path: 30 10458 14203 2914 3356 I (Atomic) Aggregator: 3356 4.68.0.11
         Communities: 2914:420 target:11111:1 origin:56:78
         VPN Label: 182449
         Localpref: 100
          Router ID: 10.255.245.12

10.255.245.12:1:4.17.225.0/24 (1 entry, 1 announced)
  *BGP   Preference: 170/-101
         Route Distinguisher: 10.255.245.12:1
         Source: 10.255.245.12
         Next hop: 192.168.208.66 via fe-0/0/0.0, selected
         Label operation: Push 182465
         Protocol next hop: 10.255.245.12
         Push 182465
         Indirect next hop: 863a8f0 305
         State: <Active Int Ext>
         Local AS:    35 Peer AS:    35
         Age: 12:19      Metric2: 1 
         Task: BGP_35.10.255.245.12+179
         Announcement bits (1): 0-BGP.0.0.0.0+179 
AS path: 30 10458 14203 2914 11853 11853 11853 6496 6496 6496 6496 6496 6496 I
                Communities: 2914:410 target:12:34 target:11111:1 origin:12:34
                VPN Label: 182465  
                Localpref: 100
                Router ID: 10.255.245.12

10.255.245.12:1:4.17.226.0/23 (1 entry, 1 announced)
  *BGP   Preference: 170/-101
         Route Distinguisher: 10.255.245.12:1
         Source: 10.255.245.12
         Next hop: 192.168.208.66 via fe-0/0/0.0, selected
         Label operation: Push 182465
         Protocol next hop: 10.255.245.12
         Push 182465
         Indirect next hop: 86bd210 330
         State: <Active Int Ext>
         Local AS:    35 Peer AS:    35
         Age: 12:19      Metric2: 1 
         Task: BGP_35.10.255.245.12+179
         Announcement bits (1): 0-BGP.0.0.0.0+179 
         AS path: 30 10458 14203 2914 11853 11853 11853 6496 6496 6496 6496 6496 
         6496 I
         Communities: 2914:410 target:12:34 target:11111:1 origin:12:34
         VPN Label: 182465
         Localpref: 100
         Router ID: 10.255.245.12

10.255.245.12:1:4.17.251.0/24 (1 entry, 1 announced)
  *BGP   Preference: 170/-101
         Route Distinguisher: 10.255.245.12:1
         Source: 10.255.245.12
         Next hop: 192.168.208.66 via fe-0/0/0.0, selected
         Label operation: Push 182465
         Protocol next hop: 10.255.245.12
         Push 182465
         Indirect next hop: 86bd210 330
         State: <Active Int Ext>
         Local AS:    35 Peer AS:    35
         Age: 12:19      Metric2: 1 
         Task: BGP_35.10.255.245.12+179
         Announcement bits (1): 0-BGP.0.0.0.0+179 
         AS path: 30 10458 14203 2914 11853 11853 11853 6496 6496 6496 6496 6496 
         6496 I
         Communities: 2914:410 target:12:34 target:11111:1 origin:12:34
         VPN Label: 182465
         Localpref: 100

show route table bgp.rtarget.0 (When Proxy BGP Route Target Filtering Is Configured)

user@host> show route table bgp.rtarget.o
bgp.rtarget.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

100:100:100/96                
                   *[RTarget/5] 00:03:14
                      Type Proxy
                        for 10.255.165.103
                        for 10.255.166.124
                      Local

show route table inet.0

user@host> show route table inet.0 
inet.0: 12 destinations, 12 routes (11 active, 0 holddown, 1 hidden)
+ = Active Route, - = Last Active, * = Both

0.0.0.0/0          *[Static/5] 00:51:57
                    > to 111.222.5.254 via fxp0.0
1.0.0.1/32         *[Direct/0] 00:51:58
                    > via at-5/3/0.0
1.0.0.2/32         *[Local/0] 00:51:58
                     Local
12.12.12.21/32     *[Local/0] 00:51:57
                     Reject
13.13.13.13/32     *[Direct/0] 00:51:58
                    > via t3-5/2/1.0
13.13.13.14/32     *[Local/0] 00:51:58
                     Local
13.13.13.21/32     *[Local/0] 00:51:58
                     Local
13.13.13.22/32     *[Direct/0] 00:33:59
                    > via t3-5/2/0.0
127.0.0.1/32        [Direct/0] 00:51:58
                    > via lo0.0
111.222.5.0/24     *[Direct/0] 00:51:58
                    > via fxp0.0
111.222.5.81/32    *[Local/0] 00:51:58
                     Local

show route table inet6.0

user@host> show route table inet6.0 
inet6.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Route, * = Both

fec0:0:0:3::/64 *[Direct/0] 00:01:34
>via fe-0/1/0.0

fec0:0:0:3::/128 *[Local/0] 00:01:34
>Local

fec0:0:0:4::/64 *[Static/5] 00:01:34
>to fec0:0:0:3::ffff via fe-0/1/0.0

show route table inet6.3

user@router> show route table inet6.3
inet6.3: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

::10.255.245.195/128
                   *[LDP/9] 00:00:22, metric 1
                    > via so-1/0/0.0
::10.255.245.196/128
                   *[LDP/9] 00:00:08, metric 1
                    > via so-1/0/0.0, Push 100008

show route table inetflow detail

user@host> show route table inetflow detail 
inetflow.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
10.12.44.1,*/48 (1 entry, 1 announced) 
        *BGP    Preference: 170/-101
                Next-hop reference count: 2
                State: **Active Ext>
                Local AS: 65002 Peer AS: 65000
                Age: 4 
                Task: BGP_65000.10.12.99.5+3792
                Announcement bits (1): 0-Flow 
                AS path: 65000 I
                Communities: traffic-rate:0:0
                Validation state: Accept, Originator: 10.12.99.5
                Via: 10.12.44.0/24, Active
                Localpref: 100
                Router ID: 10.255.71.161

10.12.56.1,*/48 (1 entry, 1 announced)  
        *Flow   Preference: 5
                Next-hop reference count: 2
                State: **Active>
                Local AS: 65002 
                Age: 6:30 
                Task: RT Flow
                Announcement bits (2): 0-Flow 1-BGP.0.0.0.0+179 
                AS path: I
                Communities: 1:1

show route table l2circuit.0

user@host> show route table l2circuit.0 
l2circuit.0: 4 destinations, 4 routes (4 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

10.1.1.195:NoCtrlWord:1:1:Local/96
                   *[L2CKT/7] 00:50:47
                    > via so-0/1/2.0, Push 100049
                      via so-0/1/3.0, Push 100049
10.1.1.195:NoCtrlWord:1:1:Remote/96
                   *[LDP/9] 00:50:14
                      Discard
10.1.1.195:CtrlWord:1:2:Local/96
                   *[L2CKT/7] 00:50:47
                    > via so-0/1/2.0, Push 100049
                      via so-0/1/3.0, Push 100049
10.1.1.195:CtrlWord:1:2:Remote/96
                   *[LDP/9] 00:50:14
                      Discard

show route table mpls

user@host> show route table mpls 
mpls.0: 4 destinations, 4 routes (4 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

0                  *[MPLS/0] 00:13:55, metric 1
                      Receive
1                  *[MPLS/0] 00:13:55, metric 1
                      Receive
2                  *[MPLS/0] 00:13:55, metric 1
                      Receive
1024               *[VPN/0] 00:04:18 
                      to table red.inet.0, Pop

show route table mpls extensive

user@host> show route table mpls extensive 
100000 (1 entry, 1 announced)
TSI:
KRT in-kernel 100000 /36 -> {so-1/0/0.0}
        *LDP    Preference:   9
                Next hop:  via so-1/0/0.0, selected
                Pop
                State: <Active Int>
                Age: 29:50      Metric: 1
                Task: LDP
                Announcement bits (1): 0-KRT
                AS path: I
                Prefixes bound to route: 10.0.0.194/32

show route table mpls.0

user@host> show route table mpls.0 
mpls.0: 11 destinations, 11 routes (11 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

0                  *[MPLS/0] 00:45:09, metric 1
                      Receive
1                  *[MPLS/0] 00:45:09, metric 1
                      Receive
2                  *[MPLS/0] 00:45:09, metric 1
                      Receive
100000             *[L2VPN/7] 00:43:04
                    > via so-0/1/0.1, Pop
100001             *[L2VPN/7] 00:43:03
                    > via so-0/1/0.2, Pop       Offset: 4
100002             *[LDP/9] 00:43:22, metric 1
                      via so-0/1/2.0, Pop
                    > via so-0/1/3.0, Pop
100002(S=0)        *[LDP/9] 00:43:22, metric 1
                      via so-0/1/2.0, Pop
                    > via so-0/1/3.0, Pop
100003             *[LDP/9] 00:43:22, metric 1
                    > via so-0/1/2.0, Swap 100002
                      via so-0/1/3.0, Swap 100002
100004             *[LDP/9] 00:43:16, metric 1
                      via so-0/1/2.0, Swap 100049
                    > via so-0/1/3.0, Swap 100049
so-0/1/0.1         *[L2VPN/7] 00:43:04
                    > via so-0/1/2.0, Push 100001, Push 100049(top)
                      via so-0/1/3.0, Push 100001, Push 100049(top)
so-0/1/0.2         *[L2VPN/7] 00:43:03
                      via so-0/1/2.0, Push 100000, Push 100049(top) Offset: -4
                    > via so-0/1/3.0, Push 100000, Push 100049(top) Offset: -4

show route table mpls.0 (RSVP Route—Transit LSP)

user@host> show route table mpls.0 
mpls.0: 8 destinations, 8 routes (8 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

0                  *[MPLS/0] 00:37:31, metric 1
                      Receive
1                  *[MPLS/0] 00:37:31, metric 1
                      Receive
2                  *[MPLS/0] 00:37:31, metric 1
                      Receive
13                 *[MPLS/0] 00:37:31, metric 1
                      Receive
300352             *[RSVP/7/1] 00:08:00, metric 1
                    > to 8.64.0.106 via ge-1/0/1.0, label-switched-path lsp1_p2p
300352(S=0)        *[RSVP/7/1] 00:08:00, metric 1
                    > to 8.64.0.106 via ge-1/0/1.0, label-switched-path lsp1_p2p
300384             *[RSVP/7/2] 00:05:20, metric 1
                    > to 8.64.1.106 via ge-1/0/0.0, Pop      
300384(S=0)        *[RSVP/7/2] 00:05:20, metric 1
                    > to 8.64.1.106 via ge-1/0/0.0, Pop

show route table vpls_1 detail

user@host> show route table vpls_1 detail 
vpls_1.l2vpn.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
Restart Complete

1.1.1.11:1000:1:1/96 (1 entry, 1 announced)
*L2VPN Preference: 170/-1
Receive table: vpls_1.l2vpn.0
Next-hop reference count: 2
State: <Active Int Ext>
Age: 4:29:47 Metric2: 1
Task: vpls_1-l2vpn
Announcement bits (1): 1-BGP.0.0.0.0+179
AS path: I
Communities: Layer2-info: encaps:VPLS, control flags:Site-Down
Label-base: 800000, range: 8, status-vector: 0xFF

show route table vpn-a

user@host> show route table vpn-a 
vpn-a.l2vpn.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)

+ = Active Route, - = Last Active, * = Both
192.168.16.1:1:1:1/96
                   *[VPN/7] 05:48:27
                     Discard
192.168.24.1:1:2:1/96
                   *[BGP/170] 00:02:53, localpref 100, from 192.168.24.1
                      AS path: I
                    > to 10.0.16.2 via fe-0/0/1.0, label-switched-path am
192.168.24.1:1:3:1/96
                   *[BGP/170] 00:02:53, localpref 100, from 192.168.24.1
                      AS path: I
                    > to 10.0.16.2 via fe-0/0/1.0, label-switched-path am

show route table vpn-a.mdt.0

user@host> show route table vpn-a.mdt.0 
vpn-a.mdt.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

1:1:0:10.255.14.216:232.1.1.1/144               
                   *[MVPN/70] 01:23:05, metric2 1
                      Indirect
1:1:1:10.255.14.218:232.1.1.1/144               
                   *[BGP/170] 00:57:49, localpref 100, from 10.255.14.218
                      AS path: I
                    > via so-0/0/0.0, label-switched-path r0e-to-r1
1:1:2:10.255.14.217:232.1.1.1/144               
                   *[BGP/170] 00:57:49, localpref 100, from 10.255.14.217
                      AS path: I
> via so-0/0/1.0, label-switched-path r0-to-r2

show route table VPN-A detail

user@host> show route table VPN-A detail 
VPN-AB.inet.0: 8 destinations, 8 routes (8 active, 0 holddown, 0 hidden)
10.255.179.9/32 (1 entry, 1 announced)
        *BGP    Preference: 170/-101
                Route Distinguisher: 10.255.179.13:200
                Next hop type: Indirect
                Next-hop reference count: 5
                Source: 10.255.179.13
                Next hop type: Router, Next hop index: 732
                Next hop: 10.39.1.14 via fe-0/3/0.0, selected
                Label operation: Push 299824, Push 299824(top)
                Protocol next hop: 10.255.179.13
                Push 299824
                Indirect next hop: 8f275a0 1048574
                State: (Secondary Active Int Ext)
                Local AS: 1 Peer AS: 1
                Age: 3:41:06 Metric: 1 Metric2: 1 
                Task: BGP_1.10.255.179.13+64309
                Announcement bits (2): 0-KRT 1-BGP RT Background 
                AS path: I
                Communities: target:1:200 rte-type:0.0.0.0:1:0
                Import Accepted
                VPN Label: 299824 TTL Action: vrf-ttl-propagate
                Localpref: 100
                Router ID: 10.255.179.13
                Primary Routing Table bgp.l3vpn.0

show route table VPN-AB.inet.0

user@host> show route table VPN-AB.inet.0 
      VPN-AB.inet.0: 8 destinations, 8 routes (8 active, 0 holddown, 0 hidden) 
      + = Active Route, - = Last Active, * = Both 
     
      10.39.1.0/30       *[OSPF/10] 00:07:24, metric 1 
                          > via so-7/3/1.0 
      10.39.1.4/30       *[Direct/0] 00:08:42 
                          > via so-5/1/0.0 
      10.39.1.6/32       *[Local/0] 00:08:46 
                           Local 
      10.255.71.16/32    *[Static/5] 00:07:24 
                          > via so-2/0/0.0 
      10.255.71.17/32    *[BGP/170] 00:07:24, MED 1, localpref 100, from 
      10.255.71.15 
                            AS path: I 
                          > via so-2/1/0.0, Push 100020, Push 100011(top) 
      10.255.71.18/32    *[BGP/170] 00:07:24, MED 1, localpref 100, from 
      10.255.71.15 
                            AS path: I 
                          > via so-2/1/0.0, Push 100021, Push 100011(top) 
      10.255.245.245/32  *[BGP/170] 00:08:35, localpref 100 
                            AS path: 2 I 
                          > to 10.39.1.5 via so-5/1/0.0 
      10.255.245.246/32  *[OSPF/10] 00:07:24, metric 1 
                          > via so-7/3/1.0

show route table VPN_blue.mvpn-inet6.0

user@host> show route table VPN_blue.mvpn-inet6.0 
vpn_blue.mvpn-inet6.0: 6 destinations, 6 routes (6 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

1:10.255.2.202:65535:10.255.2.202/432
                   *[BGP/170] 00:02:37, localpref 100, from 10.255.2.202
                      AS path: I
                    > via so-0/1/3.0
1:10.255.2.203:65535:10.255.2.203/432
                   *[BGP/170] 00:02:37, localpref 100, from 10.255.2.203
                      AS path: I
                    > via so-0/1/0.0
1:10.255.2.204:65535:10.255.2.204/432
                   *[MVPN/70] 00:57:23, metric2 1
                      Indirect
5:10.255.2.202:65535:128:::192.168.90.2:128:ffff::1/432
                   *[BGP/170] 00:02:37, localpref 100, from 10.255.2.202
                      AS path: I
                    > via so-0/1/3.0
6:10.255.2.203:65535:65000:128:::10.12.53.12:128:ffff::1/432
                   *[PIM/105] 00:02:37
                      Multicast (IPv6)
7:10.255.2.202:65535:65000:128:::192.168.90.2:128:ffff::1/432
                   *[MVPN/70] 00:02:37, metric2 1
                      Indirect

show route table VPN-A detail

user@host> show route table VPN-A detail 
VPN-AB.inet.0: 8 destinations, 8 routes (8 active, 0 holddown, 0 hidden)
10.255.179.9/32 (1 entry, 1 announced)
        *BGP    Preference: 170/-101
                Route Distinguisher: 10.255.179.13:200
                Next hop type: Indirect
                Next-hop reference count: 5
                Source: 10.255.179.13
                Next hop type: Router, Next hop index: 732
                Next hop: 10.39.1.14 via fe-0/3/0.0, selected
                Label operation: Push 299824, Push 299824(top)
                Protocol next hop: 10.255.179.13
                Push 299824
                Indirect next hop: 8f275a0 1048574
                State: (Secondary Active Int Ext)
                Local AS: 1 Peer AS: 1
                Age: 3:41:06 Metric: 1 Metric2: 1 
                Task: BGP_1.10.255.179.13+64309
                Announcement bits (2): 0-KRT 1-BGP RT Background 
                AS path: I
                Communities: target:1:200 rte-type:0.0.0.0:1:0
                Import Accepted
                VPN Label: 299824 TTL Action: vrf-ttl-propagate
                Localpref: 100
                Router ID: 10.255.179.13
                Primary Routing Table bgp.l3vpn.0

show route table inetflow detail

user@host> show route table inetflow detail 
inetflow.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
10.12.44.1,*/48 (1 entry, 1 announced) 
        *BGP    Preference: 170/-101
                Next-hop reference count: 2
                State: **Active Ext>
                Local AS: 65002 Peer AS: 65000
                Age: 4 
                Task: BGP_65000.10.12.99.5+3792
                Announcement bits (1): 0-Flow 
                AS path: 65000 I
                Communities: traffic-rate:0:0
                Validation state: Accept, Originator: 10.12.99.5
                Via: 10.12.44.0/24, Active
                Localpref: 100
                Router ID: 10.255.71.161

10.12.56.1,*/48 (1 entry, 1 announced)  
        *Flow   Preference: 5
                Next-hop reference count: 2
                State: **Active>
                Local AS: 65002 
                Age: 6:30 
                Task: RT Flow
                Announcement bits (2): 0-Flow 1-BGP.0.0.0.0+179 
                AS path: I
                Communities: 1:1
user@PE1> show route table green.l2vpn.0 (VPLS Multihoming with FEC 129)
green.l2vpn.0: 6 destinations, 6 routes (6 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

1.1.1.2:100:1.1.1.2/96 AD             
                   *[VPLS/170] 1d 03:11:03, metric2 1
                         Indirect
1.1.1.4:100:1.1.1.4/96 AD             
                   *[BGP/170] 1d 03:11:02, localpref 100, from 1.1.1.4
                      AS path: I, validation-state: unverified
                    >    via ge-1/2/1.5
1.1.1.2:100:1:0/96 MH             
                   *[VPLS/170] 1d 03:11:03, metric2 1
                         Indirect
1.1.1.4:100:1:0/96 MH             
                   *[BGP/170] 1d 03:11:02, localpref 100, from 1.1.1.4
                      AS path: I, validation-state: unverified
                    >    via ge-1/2/1.5
1.1.1.4:NoCtrlWord:5:100:100:1.1.1.2:1.1.1.4/176               
                   *[VPLS/7] 1d 03:11:02, metric2 1
                    >    via ge-1/2/1.5
1.1.1.4:NoCtrlWord:5:100:100:1.1.1.4:1.1.1.2/176               
                   *[LDP/9] 1d 03:11:02
                         Discard

Modified: 2015-06-24

Supported Platforms

 

Related Documentation

 

Modified: 2015-06-24

Previous Page Next Page