D-Link DXS-5000-54S Emulator - Page 1134

5000 Series Layer 2/3 Managed Data Center Switch CLI Reference Guide Peer (Peer ID 200.1.1.1 (18.24.1.3) BGP Next Hop 200.1.1.1 Extended Community RT:3:300 Display Parameters BGP table version Status codes Route Distinguisher Network Next Hop Metric LocPrf Path Prefix/Prefix Length Generation ID Forwarding Advertised To Update Groups Local Preference AS Path Origin Metric Type IGP Cost Peer (Peer ID) BGP Next Hop Atomic Aggregate Aggregator Communities Each time phase 2 of the BGP decision process runs to select new BGP routes, this number is incremented. One of the following: • s: The route is aggregated into an aggregate address configured with the summary-only option. • *: D-LINK OS never displays invalid routes; so this code is always displayed (to maintain consistency with the industw standard). • >: lndicates that BGP has selected this path as the best path to the destination. • i: The route is learned from an internal peer. The RD associated with the VRF. Destination prefix. The route's BGP next hop. Displays the BGP metric. The local preference. The AS-PATH per route. The destination prefix and prefix length. The version of the BGP routing table when this route last changed. If this BGP route is used for forwarding. The outbound update groups to which this route is advertised. The local preference, either as received from the peer or as set according to local policy. The AS-PATH. This form ofthe command displays AS-PATHs as long as allowed by bgp maxas-limit. Value of the ORIGIN attribute. Value of the MED attribute, if included. If the path is received from an internal or external peer. The interior gateway cost (e.g., OSPF cost) to the BGP NEXT HOP. The lP address of the peer that sent this route, and its router ID. The BGP NEXT HOP attribute. If the ATOMIC AGGEGATE attribute is attached to the path. The AS number and router ID of the speaker that aggregated the route. The BGP communities attached to the path. 1128