Yes... I would probably not bother to filter every peer, but just set max prefix (if they are an IXP peer for example) or otherwise you could end up with a lot of prefix lists and I think the router can only hold so many prefix list entries.
Not every peer is going to have info in the db and/or it may not be up to date etc. This approach would be suitable for where you have downstream customers and you want to filter what they can announce to you, and you want a way to automate the updating of prefix lists accepted from customers (Many transit providers do it this way) Regards, Rob -- Robert Lister On 3 Aug 2011, at 06:51, Martin T <m4rtn...@gmail.com> wrote: > As I understand, in case ISP-A would like to peer with ISP-B, the > ISP-A usually specifies it's AS-set it will announce to ISP-B? For > example in case XS4ALL(xs4all.nl) would like to set up a peering with > some other ISP, it will announce AS-ACCESSFORALL, which contains all > XS4ALL ASN's. ISP-B should be able to find all those ASN's which are > under the AS-set called AS-ACCESSFORAL by: _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
