Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

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

    Purpose

    Display all routes that originate from the specified BGP neighbor after 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 routes and show bgp ipv6 neighbors routes commands display similar information.

    Action

    To all routes that originate from the specified BGP neighbor after inbound policy is applied:

    host1#show bgp ipv6 neighbors 12.12.12.12 routes
    Local BGP identifier 11.11.11.11, local AS 400
      5 routes (200 bytes)
      5 destinations (360 bytes) of which 5 have a route
      5 routes selected for route table installation
      4 path attribute entries (608 bytes)
      Local-RIB version 33. FIB version 33.
    
    Status codes: > best, * invalid, s suppressed, d dampened, r rejected,
                  a auto-summarized
    
      Prefix               Peer           Next-hop            MED LocPrf Weight Origin
    > 3ffe:0:1:1::/64      12.12.12.12    ::102.102.102.2       0    100      0 inc. 

    Meaning

    Table 1 lists the show bgp ipv6 neighbors routes command output fields.

    Table 1: show bgp ipv6 neighbors 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.

    destinations

    Number of routes to unique prefixes stored in the BGP routing table and amount of memory consumed by routes. 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, plus prefixes for which there are currently no routes but which have had to be withdrawn from peers to which these prefixes may been previously advertised.

    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.

    Local-RIB version

    Number that is increased by one each time a route in that RIB is added, removed or modified.

    FIB version

    Number that is increased by one each time BGP updates the routes in the IP routing table based on changes in the local RIB. The FIB version matches the local-RIB version when BGP has finished updating the routes in the IP route table. The FIB version is less than the local-RIB version when BGP is still in the process of updating the IP routing table.

    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

    Published: 2014-08-18