Monitoring Routes Originating from a BGP Neighbor Before Application of Inbound Policy

Purpose

Display routes originating from the specified BGP neighbor before inbound policy is applied. Report whether the indirect next hop of a route is unreachable; if not, display the IGP cost to the indirect next hop.

The show ip bgp neighbors received-routes and show bgp ipv6 neighbors received-routes commands display similar information.

Action

To display routes originating from the specified BGP neighbor before inbound policy is applied:

host1#show ip bgp neighbors 192.168.1.158 received-routes
Local BGP identifier 111.111.111.111, local AS 444
  0 routes (0 bytes used), 0 distinct destinations (0 bytes used)
  0 routes selected for route table installation
  0 path attribute entries (0 bytes used)

Status codes: > best, * invalid, s suppressed, d dampened, r rejected

Prefix          Peer           Next-hop      MED LocPrf Weight Origin
>0.0.0.0/0      192.168.1.158  192.168.1.158              0       IGP
>13.13.13.13/32 192.168.1.158  192.168.1.158       0      0       IGP

Meaning

Table 39 lists the show ip bgp neighbors received-routes command output fields.

Table 39: show ip bgp neighbors received-routes Output Fields

Field Name

Field Description

Local BGP identifier

BGP router ID of the local router

local AS

Local autonomous system number

routes

Total number of routes stored in the BGP routing table and amount of memory consumed by routes. If several peers have advertised a route to the same prefix, all routes are included in this count.

distinct destinations

Number of routes to unique prefixes stored in the BGP routing table. If several peers have advertised a route to the same prefix, only the best route is included in this count.

routes selected for route table installation

Number of routes in the BGP routing table that have been inserted into the IP routing table

path attribute entries

Number of distinct path attributes stored in BGP's internal path attributes table. If BGP receives two routes for different prefixes but with identical path attributes, BGP will create only one entry in its internal path attribute table and share it between the two routes to conserve memory.

Prefix

Prefix for the routing table entry

Peer

IP address of BGP peer

Next hop

IP address of the next hop

MED

Multiexit discriminator for the route

LocPrf

Local preference for the route

Weight

Assigned path weight

Origin

Origin of the route

Related Documentation