If you also use the optional
longer-prefixes
parameter, then all statistics for routes that match the specified route or have a longer prefix
than the specified route are displayed. For example, if you specify 10.157.0.0 longer, then all routes with the prefix 10.157 or that have
a longer prefix (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 reconfiguration, 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
Dynamically requesting a route refresh from a BGP4 neighbor
You can easily apply changes to filters 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 prefix list that denies specific
routes received from a neighbor, you can apply the filter 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 specifications:
•
RFC 2842. This RFC specifies 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
Summary of Contents for FastIron SX 1600
Page 2: ...FastIron Ethernet Switch Layer 3 Routing 2 53 1003627 04 ...
Page 16: ...FastIron Ethernet Switch Layer 3 Routing 16 53 1003627 04 ...
Page 20: ...FastIron Ethernet Switch Layer 3 Routing 20 53 1003627 04 ...
Page 142: ...FastIron Ethernet Switch Layer 3 Routing 142 53 1003627 04 ...
Page 150: ...FastIron Ethernet Switch Layer 3 Routing 150 53 1003627 04 ...
Page 200: ...FastIron Ethernet Switch Layer 3 Routing 200 53 1003627 04 ...
Page 214: ...FastIron Ethernet Switch Layer 3 Routing 214 53 1003627 04 ...
Page 350: ...FastIron Ethernet Switch Layer 3 Routing 350 53 1003627 04 ...
Page 476: ...FastIron Ethernet Switch Layer 3 Routing 476 53 1003627 04 ...
Page 588: ...FastIron Ethernet Switch Layer 3 Routing 588 53 1003627 04 ...