I'm seeing what looks like inconsistent information being reported by a route reflector client (192.168.100.14).
Below are two lines of output from debug ip bgp events and debug ip bgp updates: *Mar 3 09:06:26.265 UTC: BGP: 192.168.100.10 rcv UPDATE about 26.0.0.0/24 -- denied *Mar 3 09:06:26.265 UTC: BGP: 192.168.100.10 Prefix 26.0.0.0/24 rejected by inbound soft reconfiguration Notice that prefix 26.0.0.0/24 is received but is being denied/ rejected. This prefix is being advertised by this router to a route reflector (192.168.100.10), and it's being reflecting back (which appears to violate RFC 1996) Now, CCO reports that running the "show ip bgp neighbor received-routes" should show: "(Optional) Displays all received routes (both accepted and rejected) from the specified neighbor." When I run this command on the RR client and looking for the routes received from the RR, I see the following: rtr-2514#show ip bgp neighbors 192.168.100.10 received-routes BGP table version is 13, local router ID is 192.168.100.14 Status codes: s suppressed, d damped, h history, * valid, > best, i - internal Origin codes: i - IGP, e - EGP, ? - incomplete Network Next Hop Metric LocPrf Weight Path *>i22.0.0.0/24 192.168.100.10 0 100 0 i *>i24.0.0.0/24 192.168.100.5 0 100 0 i Notice that 26.0.0.0/24 is not present. Is there a difference between "denied" and "rejected" routes? If, on the route reflector, I run "show ip bgp neighbor 192.168.100.14 advertised- routes", I see that this route is in fact advertised: rtr-2610#show ip bgp neighbors 192.168.100.14 advertised-routes BGP table version is 17, local router ID is 192.168.100.10 Status codes: s suppressed, d damped, h history, * valid, > best, i - internal Origin codes: i - IGP, e - EGP, ? - incomplete Network Next Hop Metric LocPrf Weight Path *> 22.0.0.0/24 0.0.0.0 0 32768 i *>i24.0.0.0/24 192.168.100.5 0 100 0 i *>i25.0.0.0/24 192.168.100.14 0 100 0 i *>i26.0.0.0/24 192.168.100.14 0 100 0 i In order to be compliant with RFC 1996, when one does a "show ip bgp neighbor X advertised-routes", one should never see X as the next hop, right? THanks Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=62335&t=62335 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
