Manipulating BGP to influence incoming traffic?

[scottosan]

We have 2 T1's to different ISP's. We use EIGRP to do outbound load balancing. This is done 1 hop internal to the ISP routers. This works great outbound, but obviously does not work inbound. It hasn't been a problem until recently and now most of the traffic comes inbound on one of the links to the point of saturation. I remember about some bpg attributes that ccould be set to influence inbound desireability, but BGP is not my strong area of knowledge. We just have default routs to the ISP's with no fancy configurations at this point.

Router 1

router bgp 326xx

bgp redistribute-internal

bgp log-neighbor-changes

network 12.5.x.x mask 255.255.255.0

neighbor 12.127.x.x remote-as xxxx

Router 2

router bgp 32xxx

bgp redistribute-internal

bgp log-neighbor-changes

network 12.5.x.x mask 255.255.255.0

neighbor 64.245.x.x remote-as xxxx

[cwangskr]

You may want read this and get some ideas,

http://www.nanog.org/mtg-0110/ppt/smith.pdf

[opers13]

This is an old post I just came across of and I have a question on the config example on page 55.

Where the config example announces a /19 block with longer AS PATH to the back up ISP making incoming traffic more desirable

thru Main ISP.

On the example the ACL is not listed for "routerD-out permit 10", I'm assuming the ACL is the 221.10.0.0/19 ip block correct??

neighbor 220.1.5.1 prefix-list aggregate out

neighbor 220.1.5.1 route-map routerD-out out

ip prefix-list aggregate permit 221.10.0.0/19

route-map routerD-out permit 10
set as-path prepend 107 107 107