If you also use the optional longer-prexes parameter, then all statistics for routes that match the specied route or have a longer prex
than the specied route are displayed. For example, if you specify 10.157.0.0 longer, then all routes with the prex 10.157 or that have
a longer prex (such as 10.157.22) are displayed.
Displaying all the routes received from the neighbor
To display all the route information received in route updates from a neighbor since you enabled soft reconguration, enter a command
such as the following at any level of the CLI.
device# show ip bgp neighbor 192.168.4.106 routes
There are 97345 received routes from neighbor 192.168.4.106
Searching for matching routes, use ^C to quit...
Status A:AGGREGATE B:BEST b:NOT-INSTALLED-BEST C:CONFED_EBGP D:DAMPED
E:EBGP H:HISTORY I:IBGP L:LOCAL M:MULTIPATH m:NOT-INSTALLED-MULTIPATH
S:SUPPRESSED F:FILTERED s:STALE
Prefix Next Hop MED LocPrf Weight Status
1 10.3.0.0/8 192.168.4.106 100 0 BE
AS_PATH: 65001 4355 701 80
2 10.4.0.0/8 192.168.4.106 100 0 BE
AS_PATH: 65001 4355 1
3 10.60.212.0/22 192.168.4.106 100 0 BE
AS_PATH: 65001 4355 701 1 189
4 10.6.0.0/8 192.168.4.106 0 BE
device# show ip bgp neighbor 192.168.4.106 routes
There are 97345 received routes from neighbor 192.168.4.106
Searching for matching routes, use ^C to quit...
tatus A:AGGREGATE B:BEST b:NOT-INSTALLED-BEST C:CONFED_EBGP D:DAMPED
E:EBGP H:HISTORY I:IBGP L:LOCAL M:MULTIPATH S:SUPPRESSED F:FILTEREDtatus A:AGGREGATE B:BEST b:NOT-
INSTALLED-BEST C:CONFED_EBGP D:DAMPED
E:EBGP H:HISTORY I:IBGP L:LOCAL M:MULTIPATH S:SUPPRESSED F:FILTERED
Prefix Next Hop MED LocPrf Weight Status
1 10.3.0.0/8 192.168.4.106 100 0 BE
AS_PATH: 65001 4355 701 8
2 10.4.0.0/8 192.168.4.106 100 0 BE
AS_PATH: 65001 4355 1
3 10.60.212.0/22 192.168.4.106 100 0 BE
AS_PATH: 65001 4355 701 1 189
4 10.6.0.0/8 192.168.4.106 100 0 BE
Syntax: show ip bgp neighbors ip-addr received-routes [ detail ]
The detail parameter displays detailed information for the routes. This example shows summary information.
NOTE
The syntax for displaying received routes is shown. For complete command syntax, refer to Displaying BGP4 neighbor
information on page 443.
Dynamically requesting a route refresh from a BGP4 neighbor
You can easily apply changes to
lters that control BGP4 routes received from or advertised to a neighbor, without resetting the BGP4
session between the device and the neighbor. For example, if you add, change, or remove a BGP4 IP prex list that denies specic
routes received from a neighbor, you can apply the lter change by requesting a route refresh from the neighbor. If the neighbor also
supports dynamic route refreshes, the neighbor resends its Adj-RIB-Out, its table of BGP4 routes. Using the route refresh feature, you
do not need to reset the session with the neighbor.
The route refresh feature is based on the following specications:
• RFC 2842. This RFC species the Capability Advertisement, which a BGP4 device uses to dynamically negotiate a capability
with a neighbor.
• RFC 2858 for Multi-protocol Extension.
Displaying BGP4 information
FastIron Ethernet Switch Layer 3 Routing
53-1003627-04 471
To Next Page
Loading...
Need help?
General
