pehalwaan
asked on
Load Sharing between Two links
I have a CISCO 6500 with multiple SUP cards( for redundancy) peering with two diffrent ISP for BGP v4.
ISP1 ISP2
| |
| |
Router1
I understand i can share the inbound traffic using AS prepnding but how do i make outbound sharing work ?
I need both lines configured for redundancy and increased throughput..
I am getting default routes from both isp's .
ISP1 ISP2
| |
| |
Router1
I understand i can share the inbound traffic using AS prepnding but how do i make outbound sharing work ?
I need both lines configured for redundancy and increased throughput..
I am getting default routes from both isp's .
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
These are both good solutions. Let me add to them.
pehalwaan's way is good for equal lines and doesn't require BGP. Just make sure CEF is enabled so it will do per-destination load balancing. You will also want to make sure you add SLA Tracking onto the "ip route 0.0.0.0" commands or else you'll get a black hole to half your routes if one of the ISP's goes offline. This method also does not offer you any control over how much it load balances or if the best gateway is used for a particular customer.
JFrederick29's BGP method will work for BGP outgoing. I would also recommend a higher level of quality control by adding OER into the mix. It can be configured to use netflow and ICMP pings (passive and active monitoring) and will adjust which gateway is used by injecting new BGP routes.
OER introductory documentation can be found here:
http://www.cisco.com/univercd/cc/td/doc/solution/tdprpdgx.pdf
http://www.cisco.com/en/US/docs/ios/12_4t/oer/configuration/guide/h_oerstr.html
It's a lot of pages, but don't let it get you down. A final OER configuration usually isn't more than 20-30 lines of config. Cisco is just very thorough in explaining it.
pehalwaan's way is good for equal lines and doesn't require BGP. Just make sure CEF is enabled so it will do per-destination load balancing. You will also want to make sure you add SLA Tracking onto the "ip route 0.0.0.0" commands or else you'll get a black hole to half your routes if one of the ISP's goes offline. This method also does not offer you any control over how much it load balances or if the best gateway is used for a particular customer.
JFrederick29's BGP method will work for BGP outgoing. I would also recommend a higher level of quality control by adding OER into the mix. It can be configured to use netflow and ICMP pings (passive and active monitoring) and will adjust which gateway is used by injecting new BGP routes.
OER introductory documentation can be found here:
http://www.cisco.com/univercd/cc/td/doc/solution/tdprpdgx.pdf
http://www.cisco.com/en/US/docs/ios/12_4t/oer/configuration/guide/h_oerstr.html
It's a lot of pages, but don't let it get you down. A final OER configuration usually isn't more than 20-30 lines of config. Cisco is just very thorough in explaining it.
ASKER
router bgp 50
neighbor 1.1.1.1 remote-as x
neighbor 1.1.1.1 prefix-list denyall in
neighbor 2.2.2.2 remote-as y
neighbor 2.2.2.2 prefix-list denyall in
ip route 0.0.0.0 0.0.0.0 1.1.1.1
ip route 0.0.0.0 0.0.0.0 2.2.2.2
ip prefix-list denyall 0.0.0.0/0 le 32