Slashdot Mirror
How Do Businesses Scale Their Bandwidth Needs?
onebadmutha asks: "I'm technology admin for a very rapidly growing company. We've gone from a fractional T-1, to supplementing that with a snappy DSL line, and now we're running out of reasonable options. I've looked at routers that load-balance, but do so horribly. I've considered splitting up my network users to use several incoming DSL lines, only to be confronted with intranet accessibility issues. None of these provide the kind of redundancy and control that I'd like, and certainly not with a nice pleasant UI that doesn't cause me great grief. I've looked at Open Source router distros (like routerOS, and others) and I've looked at using the full gamut of Microsoft madness. How do other businesses solve this problem of scaling bandwidth needs, without completely unlimited budgets for redundant OC-48 runs?"
That's how real tech companies do it. If you can get Yipes, Cogent, AboveNet, or some other dark fiber provider to serve you Ethernet service, that's the cheapest way to get a lot of bandwidth (10-100Mb/s range). If you can't, then you get a fractional DS3. Most real providers will let you dial the bandwidth up and down reasonably, so you could start out with a 5-10Mb/s circuit and grow from there.
Bonding T1s and DSL is neat and all, but if your business actually depends on the Internet working, go with one really good fat pipe and then maybe a thin one (T1 or so) as a backup. Don't mess with complex setups. Complex = new ways to fail.
Then, ask yourself what kind of traffic you are handling. If you're looking at users surfing the web, you probably needn't be overly concerned with load balancing; if you're receiving tons of inbound traffic to your servers, on the other hand, not only do you need load balancing, but you probably also need to seriously consider co-location solutions for your servers.
The adminstrative traffic is typically a much lower priority in most companies. I don't know how many users you're talking about, or what they're doing, but most small companies just live with a single (full) T1 until they absolutely need to bond another T1 (where "need" is subject, but should be kept in check, especially given that last bit about not having unlimited funding).
I guess this is not much of an answer, but these are all important questions you need to be asking yourself well before seeking specific answers. I'm not sure where you're coming from, and I don't mean to accuse you of anything, but taking the approach that you'll know the right answer when you see it is usually flawed from the start.
Slow down there, chief. Exactly what kind of company would be going from fractional T-1, to DSL, to... an OC-48? (I sssume you were exaggerating on the OC-48)
Couple questions:
1) How many employees are we talking about here?
2) What are they doing on the internet that is so demanding?
3) Are you running any web/streaming servers onsite?
4) Have you gone to any lengths to diagnose exactly what your bottleneck might be?
5) Are you sure you don't just have a couple of hogs downloading porn all day?
I know 200+ employee companies that get by with a single T-1 just fine. I'm a little suspicious of your bandwidth needs.
But if you really meed that much bandwidth for web browsing (I doubt you do), the next step would be a DS-3 circuit at about 45Mbit. But that can be pretty costly for the circuit alone. It would, however, allow you to scale because you'd probably be paying for the bandwidth used and not the full 45Mbit. If you are in a building with other companies who have similar needs, you may be able to split the cost of the circuit and share it.
Also, depending on your location, you may be able to setup a wireless (not WiFi) deal with someone. Something with real gear, of course. Not just a couple Linksys' with Pringle can antennaes.
-matthew
"THERE IS NO JUSTICE, THERE IS ONLY ME." -Death
Is this internet access for desktop users? People from outside coming in to your corporate website? VPN connections to other offices? How many users? Are you attempting to syncronize any data across the link? In real time, or overnight?
The possible set of right answers depends a lot on what you're doing with it.
Policy based routing plus any number of DSL lines will work for splitting up desktop web access.
Inbound traffic for the corporate website is pretty much the antithesis of that... outbound traffic is the target, and that ends up being T-1 optimized for small sites and bonded T-1s or faster links for bigger ones.
VPNs can be symmetrical or asymmetrical. Your mileage may vary.
You've got a variety of options for banning bitorrent (that is your problem, right? You have done traffic analysis before coming to Slashdot, right?). This is in an escalating hierarchy of how invasive you'll have to be. 1) Tell your employees that bandwidth costs have gone up, that you know BT to be the source of the problem, and that you trust them to do what is necessary. 1.5) Ban BT by policy, threaten severe sanctions up to and including dismissal for skirting the ban. 2) Block the standard BT ports. 3) Filter out BT packets. 4) Install computer forensics software and look for evidence of BT use (pretty much has to be combined with 1.5).
Help poke pirates in the eyepatch, arr.
Such a line can easily be brought to it's knees by simply saturating the upstream. ADSL does not work well in business environments with many users. I'd take a full T1 over that 7M/768k DSL line for a business any day.
-matthew
"THERE IS NO JUSTICE, THERE IS ONLY ME." -Death
Forget speakeasy bonded T1, you can bond your standard DSL lines through an OpenBSD firewall using CARP. Read also about VRRP and (HSRP and GLBP) for cisco solutions. They add not only redundancy but also load balancing, and recovery is real fast as opposed to something like RIP2. You can also use OSPF but careful, OpenOSPFD and zebra dont provide load balancing and redundancy of default routes. IOS does.
I say spend your budget on additional lines instead of cisco smartnet.
"Give orange me give eat orange me eat orange give me eat orange give me you." -Nim Chimpsky
In short, there are several commercially available choices that may be available depending on latency, bandwidth, price, reliability, and availability.
1) Classic T-1, 1.5Mbps
2) IMA (Inverse Multiplexing over ATM) - Essentially bonded T-1s up to about 6 Mbps before the cost of the routers becomes prohibitive
3) Ethernet Switching - 10Mbps and higher
4) DS-3 and higher - 45 Mbps and up
If you need high availability, option 1 is ruled out. IMA is good for speed and availability, but increases complexity. Ethernet switching is fast, but redundancy will cost you and it will require additional CPE devices for security and traffic monitoring. DS-3s and up are reliable and fast, but the cost of high availability (e.g. dual-entrance facilities, multiple providers) is astronomical.
Set yourself up a matrix of each of the key metrics that make a difference to you. Talk to all your possible providers and populate your matrix with their service responses. Read their SLAs very carefully. Understand how they calculate their measurements. A 99.98% availability can be insufficient depending on how they calculate it. Weight their responses based on your business requirements and then choose the option that best suits your needs.
If all else fails, bring in a telecommunications expert for a couple hours to help you analyze your options.
nos laetus epulor qui would domito nos
...where morale drops through the floor and people start looking for new jobs.
Nobody likes living under a fascist big-brother network policy. But, hey, you put those lousy "freeloaders" in their place, huh? That's all that matters, after all...
"A great democracy must be progressive or it will soon cease to be a great democracy." --Theodore Roosevelt
... that it's their network, their rules.
Some non-work net use is inevitable (like me making this post). But when people are using their workplace's network connection for non-work activities to the extent that it's impacting the performance of the rest of the network, then something has to change.
For most businesses, there is simply no business reason to allow people to download music and/or stream video to or from the office. It's just like the telephone. Most places don't mind people making personal calls, but they ask that they be reasonable about it, because you're supposed to do your socializing at home, on your own time. It's the same with the office net connection. Nobody cares if you use it to order a book from Amazon, or read the daily news, or browse Slashdot. But if you start hitting iTunes or Youtube, or start doing lots of Ebaying, or share a torrent of last night's "American Idol", then you might be crossing a line.