Users Guide

Layer 3 Routing Commands 1418
• No “IPv4 Outbound Update Group” is listed.
• No IPv4 prefix statistics are shown, since this implementation does not
support advertisement of IPv4 prefixes over IPv6 transport.
• “RFC 5549 Support” is displayed only if the BGP neighbor is peered over
IPv6 network.
• If the peer is configured as “autodetect”, the “Remote Address” shows
detected IPv6 address or “Unresolved” if the peer is not detected by the
autodetect feature.
• The “Autodetect Status” field is displayed only if the peer is configured as
“autodetect”. The field shows one of the following status’: “Peer is
detected”, “Peer is not detected” or “Multiple peers are detected”.
The command output provides the following information.
Term Description
BGP table version Each time phase 2 of the BGP decision process runs to select
new BGP routes, this number is incremented
Status codes One of the following:
• s: The route is aggregated into an aggregate address configured
with the summary-only option.
• *: BGP never displays invalid routes; so this code is always
displayed (to maintain consistency with the industry
standard).
• >: Indicates that BGP has selected this path as the best path
to the destination.
• i: If the route is learned from an internal peer
.
Route Distinguisher The RD associated with the VRF.
Network The destination prefix.
Next Hop The route’s BGP NEXT HOP.
Metric BGP metric.
LocPrf The local preference.
Path The AS path per route.
Prefix/Prefix Length The destination prefix and prefix length.