Guys Thanks for all the advice, I'll be hitting google/cisco for more info, a common piece of advice is to use route-maps so I'll look into that more closely
Cheers On Feb 19, 2008 2:30 AM, David Barak <[EMAIL PROTECTED]> wrote: > --- On Mon, 2/18/08, Wayne Lee <[EMAIL PROTECTED]> wrote: > > > I've had a crack at the config and was hoping you guys > > could point me > > in the correct direction or point out any errors. > > > > router bgp 29xxx > > network 217.xxx.xxx.0 mask 255.255.240.0 <----- Get rid of this line > > The customer should originate their own BGP network, and you, as the transit > provider, should just pass their route on to your upstreams. > > > > neighbor 82.xxx.xxx.162 remote-as 20xxx > > neighbor 82.xxx.xxx.162 description eBGP transit for > > customer > > neighbor 82.xxx.xxx.162 password ************ > > neighbor 82.xxx.xxx.162 prefix-list AS20xxx-in in > > neighbor 82.xxx.xxx.162 distribute-list 190 out > > neighbor 82.xxx.xxx.162 filter-list 10 out > > > > ip prefix-list AS20xxx-in seq 5 permit 217.xxx.xxx.0/20 > > ip prefix-list AS20xxx-in seq 10 deny 0.0.0.0/0 <--- not needed, there's an > > implicit deny at the end. > > You might want to modify your prefix list to permit a small deaggregation for > traffic engineering (217.x.x.0/20 le 22 for instance), and something which is > probably worth putting into place now (before you've got a zillion BGP > transit customers) is "neighbor 217.x.x.0 max-prefix x". > > > Thanks in advance for your time. > > you're welcome, > > David Barak > Need Geek Rock? Try The Franchise: > http://www.listentothefranchise.com > > > > ____________________________________________________________________________________ > Never miss a thing. Make Yahoo your home page. > http://www.yahoo.com/r/hs > _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
