Juniper ACX1000 Configuration Manual page 3178

ACX Series Universal Access Router Configuration Guide
Table 226: show route table Output Fields (continued)
Field Name Field Description
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:
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:
FECs bound to route Indicates 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, indicates 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, indicates 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.
3120
—IGP.
I
—EGP.
E
—The AS path is recorded by the sample process (sampled).
Recorded
? —Incomplete; typically, the AS path was aggregated.
[ ] —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.
In Junos OS Release 10.3 and later, the AS path field displays an unrecognized attribute and
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.
—Indicates that the prefix is not among the prefixes or prefix ranges in the database.
Unknown
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.
Copyright © 2017, Juniper Networks, Inc.