I've been spending the last week or so troubleshooting some (maybe related, but probably not) issues with Quagga. I have a test router – 7204VXR-NPEG2 running 12.4(24)T6 – with a single BGP session to a Quagga host. The only BGP session on the 7204 is with the Quagga box. This is an eBGP session. There is literally zero policy configured on either side, yet I get this without fail in show ip bgp neighbor x.x.x.x
output:
Outbound Inbound
Local Policy Denied Prefixes: -------- -------
Bestpath from this peer: 19270 n/a
Total: 19270 0
Coincidentally (or maybe not?) this number is always the same as the number of prefixes that I am receiving from the peer (show ip bgp summary
) There's a couple reasons why this is really puzzling:
1) Like I said, there is no policy. This is my BGP/neighbor config:
router bgp XXXXX
no synchronization
bgp router-id X.X.X.X
no bgp enforce-first-as
bgp log-neighbor-changes
neighbor X.X.X.X remote-as XXXXX
neighbor X.X.X.X next-hop-self
neighbor X.X.X.X soft-reconfiguration inbound
no auto-summary
2) The 7204 is not announcing anything – it's only meant to receive prefixes.
Anyone care to shed some light on what this means? Is this normal/expected output? A google search only yielded me one tidbit of information pulled from CCO:
- Bestpath from this peer
Displays inbound denials because the bestpath came from the local router.
This would make sense … for inbound. What about outbound? I can easily see this being a stupid bug, but figured I'd reach out to other folks to see if they'd seen this before.
Best Answer
This is most probably because of EBGP split horizon kicking in... i.e. 7204 router receives those prefixes from Quagga, selects best path, and attempts to advertise them. Since the only neighbor is the neighbor the best path was received from, it filters the advertisements. The counter above shows that.