<div>
Greetings,<br />
<br />
Any load-balancing between the T1 and the DSL line has to be configured in the Cisco 891 since both the T1 and the DSL are connected to it. You can not load-balance circuits connected to the 891 from a device sitting behind it.<br />
<br />
Do you have access to the Cisco 891 for configuration? If not, can your ISP configure the 891 to your needs?<br />
<br />
What is the average bandwidth of your DSL?
</div>


<div>
To use the Sonicwall for load balancing you must have access to the individual circuits. That is, each must have its own modem/router and ip address, and each of these would go on a separate X interface on the Sonicwall.
</div>


<div>
My understanding is same. <br />
1. If we have access to cisco 891, we can do that. But our ISp can help for that.<br />
<br />
But engineer of our partner company says that load balancing would be internal, I don't get it. What does it mean internal load balancing, inside cisco 891 router.<br />
<br />
Thank you.
</div>


<div>
to balance something you need at least two links. your ISPs CISCO has two links, so, it is the point where balancing should be done. if for some reason you need to do balancing somewhere else - you should throw those links through CISCO router, and keep the traffic separated (either through vlans, or split IPs with source based routing, or whatever) right to the machine that will do balancing. if you do not, then there is no place for balancing - you can not balance on single _logical_ link. <br />
hope, now it's a bit clearer ? :)
</div>


<div>
You are absolutely correct!
</div>


<div>
If you have access to 891, or if your ISP needs assistance with the configuration, just ask. It is easy to do.
</div>


<div>
I have talked to our ISP. They will change some configuration on Router. Now, DSL and T1 are connected to WAN ports of 891. I think they will remove WAN ports and we will put Sonicwall LB in between.<br />
<br />
Can we use Peplink Balance20 instead of Sonicwall tz205?<br />
<br />
Thanks,
</div>


<div>
Yes, you can use the Peplink if you want. Put both ISP circuits into that, and the output to a single X interface on the Sonicwall.
</div>


<div>
In &nbsp;fact we will be using either one.<br />
Internal network (swithch) ------&gt;Cisco891--------&gt;So<wbr />nicwall or peplink---------&gt; to WAN circuit (T1 and DSL).
</div>


<div>
I suspect your load balancer does not have T1 ports, so you may want to keep the Cisco connected on the T1.<br />
<br />
The DSL line you can connect via ethernet directly from DSL modem to load balancer.<br />
<br />
That way the load balancer will have two ethernet uplinks; one to cisco/T1 and the other to modem/DSL.
</div>


<div>
I have contacted Peplink, it has 2 WAN port one for T1 and another one for DSL.<br />
<br />
I have just got the soniwall. <br />
it says,<br />
<br />
X0 - LAN<br />
X1 - WAN<br />
X2, X3, X4 - says configurable, can be used for T1 or DSL<br />
<br />
Thank you
</div>


<div>
I just want to make sure you are clear on this: the 891 would have worked just fine without the extra equipment and cost. all you needed was two default routes: one to each of your wan links.<br />
<br />
you had mentioned that your ISP is providing the 891 and the links. so, if you put your equipment after their router and before their circuit, how would they support the links and their routed?
</div>


<div>
One support engineer has just contacted me today. They are working on that and get back to me. My understanding, the network flow would be as below. <br />
<br />
Internal network (swithch) ------&gt;Cisco891--------&gt;So<wbr />nicwall or peplink---------&gt; to WAN circuit (T1 and DSL).
</div>


<div>
I just want to make sure you know lb can be achieved with the 891. no need for extra devices and complexity. your ISP would also have hard time troubleshooting their circuits if not terminated on their equipment.
</div>


<div>
<b>HUSupport </b> 
<blockquote>
My understanding, the network flow would be as below.<br />
Internal network (swithch) ------&gt;Cisco891--------&gt;So<wbr />nicwall or peplink---------&gt; to WAN circuit (T1 and DSL). 
</blockquote>
<br />
i seriously doubt, that any sane ISP would accept it this way. after al, they're either providing you with links OR complete solution, that they have to support. there should be a clear border for area of responsibility. usually, it's the last port on operators equipment (ethernet port on switch/router or media convertor). if they want/agree to implement the load balancer (as a separate hardware device), then they are responsible for it, and it shouln be your problem no more :)<br />
<br />
<b>naderz</b> LB is not just two default routes. it's alternative routes + algorythm for route choice/balancing + watchdog, that looks, what is happening on those alternative links. is that cisco able to do that ?
</div>


<div>
just looked at <a href="http://www.cisco.com/en/US/docs/ios/ipswitch/configuration/guide/cef_load_balancng.html" rel="ugc">cisco manual</a>, and, honestly, could not find how CEF might get aware of different cost for those two uplinks. maybe there is a way, however, these links are not equal. so equal cost multipath choice algorithms (that seem to be used by CEF), do not seem for me to be a best choice.<br />
<b>naderz</b>, could you, please, comment ?
</div>


<div>
corower: true, you do have a point. CEF load-balancing will &quot;alternate&quot; outgoing traffic between the T1 and the DSL. This is in a sense called load-balancing.<br />
<br />
We don't know the bandwidth of the DSL. That may or may not be a big factor. And, yes, depending on that factor of difference the T1 could saturate quickly, <i>but only for the same destination</i>. Traffic for a different destination would be placed on the DSL. So, in essence we would be load-balancing.<br />
<br />
Given the fact that the ISP is providing the T1 and the DSL and the 891 router if one wanted to setup a load-balancing scheme in that environment quickly, then CEF per-destination would be a good candidate. My response was to the original question and given setup.<br />
<br />
If the DSL's speed is way much larger than the T1, I would actually not bother with the load-balancing schemes and just use the T1 as backup and at some point drop the T1 altogether and go with two DSLs. The cost would probably be less actually with two DSLs.
</div>


<div>
T1 speed is 6M/6M - primary<br />
DSL is 6M/768K - backup
</div>


<div>
HUSupport:<br />
<br />
Please clarify: your T1 is 6Mbps download and upload? Is it bundled T1s?
</div>


<div>
Upload and download same, bonded T1
</div>


<div>
In that case, what I have commented above for the 891 will get you per-destination load-balancing. This is not fancy, but it will get the job done.<br />
<br />
ip route 0.0.0.0 0.0.0.0 <i>T1-termination-IP</i><br />
ip route 0.0.0.0 0.0.0.0 <i>DSL-termination-IP</i><br />
<br />
And, for the sake of completeness make sure CEF is enabled:<br />
<br />
ip cef
</div>


<div>
<b>naderz:</b> as far as i understood, CEF gives only round-robin like load balancing, and single given connection always goes through single link. my concern is - as CEF does not have any capability to weight those links, it might introduce some problems. i.e. if said client heavily uses up his upload channel, filling his 768K at DSL, what happens on T1 side ? if that was simple RR, it would be impossible to get more than 768K on other link too. as enduser is almost unable to interact with CEF routing cache table, it is hardly predictable which way traffic will take. for some connections it would be a killer to go through loaded asymmetric link.<br />
i would strongly suggest to look for another balancing solution, that will take in consideration that one of the balancing links is highly asymmetric. one of the ways could be directing asymmetric part of traffic (like HTTP and incomming file transfers) to DSL, and leave symmetric traffic (SIP, servers, outgoing traffic in general) to T1 line. <br />
<br />
<b>HUSupport:</b> to understand better the situation i would like to ask -- what kind of traffic you have ? are you filling up your tube or 768K uplink has enough space for you ? as DSL and T1 is provided by single provider, are you hiding behind NAT, or are you using two independant IP ranges, or single IP range (on your side of router)? is your ISP giving you any options for load balancing / dynamic routing at all ?
</div>


<div>
Our ISP is configuring the cisco router 891 for load balancing.
</div>


<div>
<div class="content wysiwyg-content">
Hello,<br />
<br />
We have been trying to use a sonicwall or other load balancer between our 2 WAN, T1 and DSL line - both are from same ISP.<br />
Also, ISP as provided us Router, Cisco 891 that is connected to our LAN switch and 2 WAN port is conncted to T1 &amp;&nbsp;DSL. So, how do we use our Load Balancer, in between WAN link and router? We don't &nbsp;have any IP from ISP for Cisco. We only know gateway, i.e, x.x.1.1.<br />
<br />
We used load balancer, peplink before but that is the router directly connected with EVDO card.<br />
<br />
Appreciate your help, thanks!
</div>
</div>


Hello,

We have been trying to use a sonicwall or other load balancer between our 2 WAN, T1 and DSL line - both are from same ISP.
Also, ISP as provided us Router, Cisco 891 that is connected to our LAN switch and 2 WAN port is conncted to T1 & DSL. So, how do we use our Load Balancer, in between WAN link and router? We don't  have any IP from ISP for Cisco. We only know gateway, i.e, x.x.1.1.

We used load balancer, peplink before but that is the router directly connected with EVDO card.

Appreciate your help, thanks!

Load Balancer - Internet

Networking hardware includes the physical devices facilitating the use of a computer network. Typically, networking hardware includes gateways, routers, network bridges, modems, wireless access points, networking cables, line drivers, switches, hubs, and repeaters. But it also includes hybrid network devices such as multilayer switches, protocol converters, bridge routers, proxy servers, firewalls, network address translators, multiplexers, network interface controllers, wireless network interface controllers, ISDN terminal adapters and other related hardware.

Networking Hardware-Other

A router is a networking device that forwards data packets between computer networks. Routers perform the "traffic directing" functions on the Internet. The most familiar type of routers are home and small office cable or DSL routers that simply pass data, such as web pages, email, IM, and videos between computers and the Internet. More sophisticated routers, such as enterprise routers, connect large business or ISP networks up to the powerful core routers that forward data at high speed along the optical fiber lines of the Internet backbone. Though routers are typically dedicated hardware devices, use of software-based routers has grown increasingly common.

Routers

Hardware-based firewalls provide more sophisticated protection for inbound and outbound traffic than the simple Windows software firewall or the basic NAT firewalls found in routers. These devices implement techniques such as stateful packet inspection, deep packet inspection, and content filtering; and may include built-in antivirus and anti-malware protection.