[nsp] BGP, best way to balance outgoging traffic

Lucas Iglesias l.iglesias at tiba.com
Mon Aug 4 12:39:06 EDT 2003

You can do this with policy-routing (be careful, it can load your CPU).
An example would be this one:

route-map RM_OUTGOING1 permit 10
 match ip address 1
 set ip next-hop
route-map RM_OUTGOING2 permit 10
 match ip address 2
 set ip next-hop

Assuming that is the next-hop from a + b and is from
c + d (the set ip next-hop allow you to put next-hops in order, if the first
is not reachable use the next one).
ACL 1 must permit one group of IP source nets, and ACL 2 the other one.
Finally, you must apply the route-maps to all the incoming customer
interfaces, i.e.:

interface Serial5/0/1
 ip policy route-map RM_OUTGOING1

interface Serial5/0/2
 ip policy route-map RM_OUTGOING2

Good Luck.
Eng. Lucas Iglesias 
IP Engineering, Tiba S.A. 

-----Mensaje original-----
De: Lukas Krattiger [mailto:luk at everyware.ch]
Enviado el: Lunes, 04 de Agosto de 2003 06:44 a.m.
Para: cisco-nsp at puck.nether.net
Asunto: [nsp] BGP, best way to balance outgoging traffic


We are currently running our BGP with 4 upstreams and anounceing 6 prefixes.
The advertisement of this 4 prefixes over upstream a + b and 2 prefixes 
over upstream c + d are working fine.
What's now the best way to tell the outgoing traffic from all of this 2 
prefixes must take upstream c + d and the other 4 prefixes are only allowed 
to use upstream a + b ?
Any examples ?

Best Regards

cisco-nsp mailing list  cisco-nsp at puck.nether.net
archive at http://puck.nether.net/pipermail/cisco-nsp/

More information about the cisco-nsp mailing list