07-04-2018 11:53 PM - edited 03-05-2019 10:43 AM
Hi expert,
can you explain what exactly of the value 146 state/pfxrcd from show ip bgp summary?
I know there is number of receiving prefix from neighbor 10.251.1.62, but its not same value of total number of prefixes .
And if you said the value 146 is the number network on routing table, its not true.
Please explain to me what is the value 146 and how i confirm that value on routing table?
Thanks
07-05-2018 04:57 AM
Both values should match. Which platform is this on, and which IOS are you using ?
07-05-2018 05:37 AM
07-05-2018 05:54 AM
It actually looks more like a bug such as the one below. Version 15.4 and 15.5 are affected, try and upgrade to a 15.6 release...
Incorrect prefix count upon clearing bgp peering
CSCuy03504
Description
Symptom:
The number of prefixes received from a peer displayed in "show ip bgp summary" is more than the actual number of prefixes received from that peer.
Conditions:
Graceful restart is enabled.
An event on the router causes the session to go down.
Peer sends router a TCP FIN before the router sends out a TCP FIN.
Workaround:
No workaround
Further Problem Description:
The "event" seen in this DDTS is issuing a "clear ip bgp "
This behavior is more likely to be seen with a higher number of prefixes on the router.
07-05-2018 05:03 AM - edited 07-05-2018 05:03 AM
Hi
As Georg mentioned, it usually is the same value, have you executed: clear ip bgp * soft, previously?
07-05-2018 05:38 AM
07-05-2018 05:49 AM
Hello,
actually, I tested that exact same thing, but before and after applying an inbound route map filtering, both values still match, so i don't think that is the reason...
07-05-2018 06:15 AM - edited 07-05-2018 06:17 AM
Hi
Are you using any kind of filtering method (prefix list, route-map, etc)? It will show you that behavior,
The show ip bgp summary will show you the allowed Prefixes to be received only.
The show ip bgp neighbor x.x.x.x received-routes will show you the total of the received prefixes, but you will see the symbol (>) for the allowed networks in your filter method.
To avoid this behavior and extra processing, you could configure BGP ORF if you are filtering with prefix list.
Hope it is useful
:-)
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide