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
     

    Related Documentation

     

    Monitoring BGP Routes with Nonnatural Network Masks

    Purpose

    Display information about routes that have nonnatural network masks. Report whether the indirect next hop of a route is unreachable; if not, display the IGP cost to the indirect next hop.

    Action

    To display information about routes that have nonnatural network masks:

    host1#show ip bgp cidr-only
    
    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
      33.0.0.0/24   5.72.1.1   5.72.1.1     1           0       inc.
    > 44.44.0.0/24  0.0.0.0    192.168.1.1  1           32768   inc.

    Meaning

    Table 1 lists the show ip bgp cidr-only command output fields.

    Table 1: show ip bgp cidr-only 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

    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

     

    Published: 2014-08-18