[c-nsp] BGP Configuration

[Mark Tohill]

Paul,

Thanks for that!

This would also work with an outbound prefix-list (as opposed to
distribute-list) and a outbound route-map?

Thanks,
Mark


-----Original Message-----
From: Paul Stewart [mailto:pstewart at nexicomgroup.net] 
Sent: 03 August 2005 14:16
To: Mark Tohill; cisco-nsp at puck.nether.net
Subject: RE: [c-nsp] BGP Configuration

Yes.... 

Here's part of our config:

 neighbor 216.168.xxx.xx remote-as 12345
 neighbor 216.168.xxx.xx description xxxxxxxxxxxxx
 neighbor 216.168.xxx.xx password 7 xxxxxxxxxxxx
 neighbor 216.168.xxx.xx distribute-list 50 out
 neighbor 216.168.xxx.xx route-map inbound-puc in
 neighbor 216.168.xxx.xx route-map outbound-puc out
 neighbor 216.168.xxx.xx filter-list 9 out 

ip as-path access-list 22 permit ^12345_[0-9]*$

access-list 50 remark AS12345
access-list 50 permit 216.168.xxx.xxx

route-map inbound-puc permit 15
 description AS12345 - Close Destinations
 match as-path 22
 set local-preference 300
!
route-map inbound-puc permit 30
 description AS12345 - Default Weight
 set local-preference 100

route-map outbound-puc permit 10
 match as-path 22
!
route-map outbound-puc permit 15
set as-path prepend 11666 11666



So, here we are using a distribute-list to limit what we advertise to
this particular eBGP peer.  Then in our inbound-puc route map, we are
setting our local-preference (or weight) to 300 for closer destinations
and a default of 100 for everything else.  This allows us to fine tune
our peers when multiple peers are equal or close distance to remote
destinations.  Then we can also prepend using our outbound-puc route
maps if needed too....

Take a look at http://www.accelinetworks.com/bgp-load-balancing.shtml
which has an excellent example as well...:)

Paul



-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net
[mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Mark Tohill
Sent: Wednesday, August 03, 2005 8:01 AM
To: cisco-nsp at puck.nether.net
Subject: [c-nsp] BGP Configuration

 

 

Hi,

 

When declaring a EBGP peer, can you have something like the following?

Maybe the route map and prefix-list can be merged?

 

Thanks,

Mark

 

!

! External BGP Peers

!

 neighbor <EBGP Peer 1> remote-as 65123

 neighbor < EBGP Peer 1> version 4

 neighbor < EBGP Peer 1> password <password required>

 neighbor < EBGP Peer 1> route-map Prov1_ASPRE_OUT out

 neighbor < EBGP Peer 1> prefix-list Prov1_OUT out

!

! ROUTE MAP 

route-map Prov1_ASPRE_OUT permit 10

 match ip address 30

 set as-path prepend 65123 65123 65123

!

!

ip prefix-list Prov1_OUT permit 192.168.10.0/24

ip prefix-list Prov1_OUT permit 192.168.11.0/24

!

Access list 30.......

 

 

 

 

_______________________________________________
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/