one router 7206VXR

Hssi1 is AS 209 (Qwest 45M)

Hssi2 is AS 1239 (Sprint 10M)

FastEthernet0/0 is AS 21531 (connection to my core switch)

BGP does go further into the network, as some of the neighbors are announced on the core.

The outbound is my main priority right now, that is getting maxed more often.

Shawn

This information is helpful. One question that Kevin asked becomes critical now: do the EBGP peers advertise more than just a default route. If each EBGP peer advertises some prefixes in addition to any default that they may advertise then you can set weight or local-perference for some of those prefixes to prefer the higher capacity link. This would address outbound traffic but not inbound traffic.

You would almost certainly want to configure a route map and apply it inbound to the peer so that you can prefer SOME (not all) routes from that peer.

HTH

Rick

Ok I will admit, BGP is new to me, so here it goes. You ask "do the EBGP peers advertise more than just a default route"

How do I verify that?

Shawn

The easy way to do that is to do show ip bgp summary and post the output. This will display each peer and how many prefixes they have advertised. For more detail use show ip bgp. This command will show the BGP working table and show what prefixes have been advertised, and by looking at the AS path and the next hop you can figure which peer has advertised which prefix.

HTH

Rick

show ip bgp summary

BGP router identifier xx.xxx.xxx.xxx, local AS number 21531

BGP table version is 362359, main routing table version 362359

233787 network entries and 465696 paths using 39442395 bytes of memory

82752 BGP path attribute entries using 4967100 bytes of memory

73572 BGP AS-PATH entries using 1926998 bytes of memory

582 BGP community entries using 38124 bytes of memory

15 BGP extended community entries using 2122 bytes of memory

0 BGP route-map cache entries using 0 bytes of memory

0 BGP filter-list cache entries using 0 bytes of memory

Dampening enabled. 244 history paths, 445 dampened paths

9 received paths for inbound soft reconfiguration

BGP activity 484015/309727 prefixes, 966782/501086 paths, scan interval 60 secs

Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd

xx.xxx.xxx.xx 4 209 1198028 21076 362345 0 0 19:17:19 232129

xx.xxx.xxx.xx 4 21531 10446 10566 362358 0 0 19:17:26 0

xx.xxx.xxx.xxx 4 21531 10410 10587 362358 0 0 19:17:25 1

xx.xxx.xxx.xxx 4 26671 10444 10564 362346 0 0 19:17:09 1

xxx.xxx.x.xx 4 1239 426976 14068 362354 0 0 19:17:15 233302

first neighbor is Qwest DS3

second neighbor is Customer Aggregation Router (another 7206VXR that feeds T1's and DSL subscribers)

third neighbor is layer3 routing on the Core Switch

fourth neighbor is BGP we are announcing for one of our customers

fifth neighbor is Sprint 10MB connection

Thanks again

Shawn

Shawn

This shows that Qwest is advertising 232129 prefixes to you and that Spring is advertising 233302 prefixes to you. This certainly gives you something to work with if you want to move some of the traffic to the higher capacity outbound link.

HTH

Rick