Check on routes announced by peer

[Arnold Nipper]

Simone,

on 09.02.2011 18:32 Simone Morandini wrote:
> Hi all,
>>>
>>> In the scenario where filters was applied on pipes, not on BGP
>>> protocols,
>>> all received routes can be viewed via CLI:
>>> show route protocol <PEER> table <TABLE_FOR_THAT_PEER>.
>>>
>>>
> 
> apologies for "upping" my thread, but I'd like to solve this issue...
> With the above suggested command, "show route protocol <PEER> table
> <TABLE_FOR_THAT_PEER>", I do see the networks of that peer, so it looks
> like he is announcing correctly to the route server.
> Anyway, I don't see these routes propagated to the peers, neither with
> "show route where bgp_path.first=<peeras>" from birdc, nor from the
> peering router...
> 
> Where should I look for those "lost" networks? Filtering is done the
> very same way as for the other peers, as the config file is generated
> through a script.
> 

did you check manually that these networks would really pass all your
filters (as-path, prefix, whatever you are applying).

From my experience 100% the cases come from customers not having
registered their prefixes with RIPE.


HTH, Arnold
-- 
Arnold Nipper / nIPper consulting, Sandhausen, Germany
email: arnold at nipper.de       phone: +49 6224 9259 299
mobile: +49 152 53717690      fax:   +49 6224 9259 333

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 260 bytes
Desc: OpenPGP digital signature
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20110210/a6a06d95/attachment-0001.asc>