[c-nsp] Good practices for peering

[Paul Stewart]

I'd say this is pretty common.. One thing I'd add is to check if the
remote AS you are peering with has downstream AS's and to permit them as
well if you want to take full advantage of the peering...:)

Some people use RAToolset and other utilities to build access lists etc.
from radb.  This is only useful if the information at radb is up to date
and accurate...

All the best,

Paul Stewart
IP Routing/Switching
Nexicom Inc.
http://www.nexicom.net/  

-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net
[mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Vincent De
Keyzer
Sent: Wednesday, December 28, 2005 10:54 AM
To: cisco-nsp at puck.nether.net
Subject: [c-nsp] Good practices for peering

Hi,

 

what are the configuration good practices when setting-up a peering with
another AS ?

 

I would do something like this:

 

router bgp <my_as>

 neighbor 194.88.108.33 remote-as <his_as>

 neighbor 194.88.108.33 password <some-password>

 neighbor 194.88.108.33 soft-reconfiguration inbound

 neighbor 194.88.108.33 filter-list 1 out

 neighbor 194.88.108.33 filter-list 2 in

 

ip as-path access-list 1 permit ^$

 

ip as-path access-list 2 permit ^<his_as>$

 

List 1 is to announce only my routes; list 2 is to make sure that the
other guy does not leak any route towards me.

 

Does it look good?

 

Vincent

 

_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/