On Mon, Nov 30, 2009 at 11:41:51PM +0100, Martin Kraus wrote:
On Mon, Nov 30, 2009 at 09:08:14PM +0100, Ondrej Zajicek wrote:
On Mon, Nov 30, 2009 at 06:20:58PM +0100, Martin Kraus wrote:
On Mon, Nov 30, 2009 at 06:11:22PM +0100, Wolfgang Hennerbichler wrote:
yes. use birdc and the 'show route' command including it's parameters. (protocol & table)
I didn't mean routes imported from bgp into bird routing table but the statistics of the bgp protocol itself, the similar thing as show ospf topology does for ospf.
There is no command for bgp-specific protocol information, but command 'show protocols all' shows statistics of exported and imported routes between the core and the protocol (which is almost the same as routes sent and received from BGP peer): ... So I guess that means there is no plan to implement some more detailed bgp information?
There are some plans, but i don't see what kind of information would help you in the mentioned case. I would rather suggest to use logs (with enabled appropriate logging using 'debug' option) to examine that problem. -- Elen sila lumenn' omentielvo Ondrej 'SanTiago' Zajicek (email: santiago@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."