11-12-2009 12:02 PM - edited 03-06-2019 08:35 AM
hello:
If I had 2 Internet routers, each homed to a different ISP -- and then had one router sitting behind them with a routed uplink to each, could I create a load sharing scheme if I have 2 equal-cost default routes in that backend router to each of the Internet routers?
So, its like a triangle...2 Internet edge routers, each with its own bgp connection to a different ISP, and then a 3rd router sitting behind both of them with the static routes as described.
Would that work to utilize both edge routers' ISP links going outbound?
Thanks
11-12-2009 12:07 PM
Joe
Yes you could use both ISP links that way assuming that
1) the BGP routers are independant of each other ie. there is no IBGP peering between them - if there was then it may not work as you expect
2) you NAT the outbound traffic to one of the ISP's public address per ISP so return traffic comes back in the same router.
Jon
11-12-2009 12:17 PM
Jon:
Can you elaborate further on point 1?
11-12-2009 12:25 PM
Joe
Actually i may be talking rubbish (wouldn't be the first time !!). EBGP routes will always be preferred over IBGP routes so it shouldn't matter and in fact running IBGP would also give you some sort of redundancy if one of the ISP links went down.
Jon
11-12-2009 12:47 PM
Jon, we presently have a box topology.
Two Internet (I1 and I2) routers with one "access" router (A1 and A2) connected to each - like a box.
So, its I1 with a southbound connection to A1 and I2 with a southbound connection to A2. I1 and I2 connected to each other, and A1 and A2 connected to each other. All equal cost L3 links.
Each edge router has an eBGP connection to the ISP, but this is what is happening:
A1 is the HSRP primary and it receives and forwards all the traffic from the users to a default route it has to I1. I1 sees itself as the best route to the Internet and out it goes. Thats it. A2 and I2 are sitting their twittling their thumbs. This is the outbound direction.
So, what I am thinking is that A1 (lets just talk about A1 for now), should be dual homed to I1 and I2.
A1 can then have 2 equal-cost default routes to I1 and I2 that it learned dynamically from each of them.
I1 and I2 both learn their default routes from their ISP connections, so they can withdraw the default route advertisment to A1 if it loses it.
Does this make sense?
let me know if you need a drawing?
I am trying to get I2 to forward outbound traffic to the Internet as much as I1 does...right now, I1 outbound to the Internet is about 16 times more than I2.
What do you think?
11-12-2009 12:52 PM
Joe
"Does this make sense?"
Yes it does. One solution is as you suggest to dual hone A routers to L routers so whichever A router is used it sees 2 equal cost paths via both L routers.
You could also think about using GLBP instead of HSRP on A routers which would then spread the load between A1 and A2 and with the current box setup both L routers would be used equally.
Note when i say equally that is not necessarily traffic volume but spread of internal clients over the 2 ISP links.
Jon
11-12-2009 01:01 PM
Yup, I was thinking about GLBP, too.....
I guess I could leverage both solutions simultaneously...no?
This way A1 has 2 routes with the dual homing solution...
And A2 can now start forwarding Internet bound traffic with its dual homed connection.
In theory, this should increase our outbound throughput exponentially...
Any more thoughts?
By the way, why the NATing requirement?
Whats wrong with traffic leaving throug I1 sand retruning through I2?
By the way, its an I, not an "L" :-)
11-12-2009 01:14 PM
Joe
"I guess I could leverage both solutions simultaneously...no?"
Well yes you can but i'm guessing the bottleneck will be the ISP links so it's questionable whether you need both. Then again you might have great ISP links :-)
NAT - "Whats wrong with traffic leaving throug I1 sand retruning through I2?" - just a question of asymmetric routing. If you don't have firewalls then maybe not such a big issue but if you are trying to make sure both links are utilised would make sense to have return traffic coming back on the same link.
"By the way, its an I, not an "L" :-)" - thought it might be but i knew you'd work it out :-)
Jon
11-12-2009 01:19 PM
The ISP links are 10-Gig.
Got your point on the FWs...there arent any, believe it or not...
Thanks for all your help....
11-12-2009 01:49 PM
EBGP routes will always be preferred over IBGP route
Let's be careful there :)
http://www.cisco.com/en/US/tech/tk365/technologies_tech_note09186a0080094431.shtml
That would be at Step 7.
11-12-2009 01:54 PM
Yep. good point. I should have said all other things being equal EBGP routes will be preferred over IBGP.
Jon
11-12-2009 01:54 PM
Edison, see your point....
So, will an iBGP connection between I1 and I2 cause an issue? I dont see how
11-12-2009 02:08 PM
So, will an iBGP connection between I1 and I2 cause an issue? I dont see how
If ISP A has a better route, the edge router connected to ISP B will use the iBGP connection to exit the network. The same can be seen from ISP B.
This will provide some kind of load balancing on traffic leaving your network.
With iBGP implemented, you can also deploy the same level of load balancing on traffic entering your network if both edge routers are advertising similar subnets (using AS_PATH prepend for some subnets, for instance).
Regards
Edison.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide