Juniper ACX1000 Configuration Manual page 3062

ACX Series Universal Access Router Configuration Guide
Table 216: show route detail Output Fields (continued)
Field Name Field Description
Cost value of the indicated route. For routes within an AS, the cost is determined by IGP and the
Metricn
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.
For MPLS LSPs, state of the TTL propagation attribute. Can be enabled or disabled for all
TTL-Action
RSVP-signaled and LDP-signaled LSPs or for specific VRF routing instances.
For sample output, see
Name of the protocol that has added the route.
Task
The number of BGP peers or protocols to which Junos OS has announced this route, followed by the
Announcement bits
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,
found in the routing table.
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.
3004
show route table
indicates that the specified route is used for route resolution for next hops
n-Resolve inet
—An index used by Juniper Networks customer support only.
n
I —IGP.
—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
.
Copyright © 2017, Juniper Networks, Inc.