Distance Restriction Issue For Rural Bandwidth

Here's an oft asked question .... If you wanted to have a T-1 line (or any other level bandwidth circuit) installed in a very rural location, is the T1 subject to the same distance restrictions as a DSL line is?

The general answer is no. T1 lines do not have a maximum distance "limitation" as does DSL. Network carriers can use multiple T1 repeaters to regenerate (not just amplify) the T1 signal.

However, 2 distance "sensitive" components can increase T1 cost.

First, the T1 access loop. Most local exchange carriers (LECs .... e.g., AT&T/SBC/BellSouth, Qwest and Verizon) charge the ISP for T1 access based on distance between the ISP's router (Internet POP) and the customer's local serving exchange (LEC Central Office). That is why most ISP's T1 quote tools require the customers local phone number, or at least the 1st 6-digits (NPA-NXX) which identify the local CO exchange, in order to caculate the distance to the ISP's closest IP POP (Internet router).

Second, extrordinary construction costs. If the customer location is a great distance from the closest T1-equipped LEC central office, then the LEC must install additional T1 repeaters and possibly incur other transmission equipment / construction costs to reach the customer. In this case, the LEC has 2 options to deal with construction cost: either absorb cost themselves, or pass it on to the ISP who then pass it on to the end-user customer.

Assuming no extrordinary construction cost, there are ISPs that offer flat rate Internet T1s in the $100-400 range per month, anywhere in US, with no distance limitations between ISP POP and customer's serving CO. The flat rate cost includes T1 access loop and 1.5 Mbps Internet port. This can vary though so shop around. Also, don't get enamored with cost over performance and reliability. Cheapest isn't always best. In other words ... be careful of buying from "K-Mart" providers. Always go with reputable carriers (name brand) if the cost is reasonable (they all are coming down in price so this shouldn't be a big issue).

However, for most locations that are under 25 miles to the ISP POP, we are seeing Internet T1 bandwidth prices in the general range of $100-$300 per month +/-.

If you are looking for a T1 in a rural area I strongly suggest using the free search and rate quote support offered by FreedomFire Communications. They'll find you a solution that makes the most business sense ... and their services are no cost to you.

Keep in mind that in some cases a business may need more than a T1 for a bandwidth solution ... such as maybe a Business Ethernet line. The same type of concerns and solutions above for T1 also apply.

Tip....How To Determine Network/Bandwidth Requirements For Supply Chain Management Systems

Following is a list of information packed articles to help you solve your bandwidth issues with a supply chain management system network design and installation. You'll get tips on what to look for, what to ensure is part of any design package, how to compare providers for any solution you decide upon, and where to find the best deals so you have the best chance at the most cost effective solution.

* What Bandwidth Solution (T1, DS3, OC3) Makes Sense For A Supply Chain Network?

“A company's supply chain network can be a complicated animal. To service this network of constant data sharing and storage requires a high performing reliable network backbone. An important part of the design is the right level of bandwidth support .... T1, DS3, or OC3 bandwidth circuits to be exact. Making the right decision on what circuit to choose means navigating a number of issues.”

* Meeting Your Bandwidth Requirements For Supply Chain Management Applications

"Deploying an Supply Chain Management (SCM) solution that provides the intended return on investment requires that the applications, servers, and enterprise network infrastructure work together seamlessly. This is easier said than done and will necessitate a thorough evaluation of your bandwidth needs to meet the demand."

* More On Meeting Your Bandwidth Requirements For Supply Chain Management Applications

"The key to a successful SCM implementation is a clear understanding of the business objectives and business requirements of the company the SCM primarily supports. This often includes a number of legacy systems which need to be integrated into the solution. From this will come the technical objectives to be met and the technical requirements that frame the solution. Only then will the communication requirements for bandwidth capacity, reliability, resiliency, latency, security, and expandability be meaningful."

OC3, OC12 & OC48 Bandwidth (Fiber Optics)....Ideal Solution For High End Users

The ideal solution for high end bandwidth users where connectivity is essential for operations isn't a simple T1 or DS3 dedicated line...you need an "OC" fiber optic network. So just what is OCx, what can it do for you, and what do you need to know?

What is an OCx Circuit?

'OC' stands for Optical Carrier and is used to specify the speed of fiber optic networks conforming to the SONET standard. SONET, (Synchronous Optical Networks), includes a set of signal rate multiples for transmitting digital signals on optical fiber. The base rate (OC-1) is 51.84 Mbps. Certain multiples of the base rate are provided below with bandwidth amounts. Asynchronous transfer mode (ATM) makes use of some of the Optical Carrier levels.

Optical Carrier lines provide content providers, ASP's, ISP's & large enterprises with dedicated Internet connectivity. These Optical Carrier Level circuits are an ideal solution for high end bandwidth users where connectivity is essential for operations. Some examples are large data centers, high tech research facilities, university infrastructure, airport complex, and casino video security and data systems.

What is an OC3?

An OC3 can be three DS3s (T3s) or as one 155M pipe. The benefit in using DS3s is that each can be separated back out as individual T1s (each with 24 channels). To put it into perspective, the speed of an OC3 connection is 155Mbps. This is equivalent to 3 T3 lines or 100 T1 lines. An OC12 connection is 622Mbps, equivalent to 14 T3 lines or approx. 414 T1 lines.

What is an OC12?

An OC12 is approximately equal to 4 OC3s and runs at 622 Mbps. which makes it an excellent point-to-point IP delivery connection. The greatest benefit to an OC-12 is that bandwidth can be added to a business as it grows without any major system overhauls. An OC12 can also allow a business to have unlimited IP addresses which insures that growth is never limited...

What is an OC48?

An OC48 works as a reliable fiber optic backbone for large networks which require volume extensive voice/data/video traffic. It is a long-haul backbone fibre connection capable of transmitting data at 2.45 Gbps. To put it into perspective the speed of an OC48 is the equivalent of having 48 T3's OR 1,344 T1 lines

The pricing for these type of connections can vary widely depending on the carrier, location of service and the exact application for which the connection is being used. Due to this complexity it is suggested to use the services of a consultant such as FreedomFire Communications to research available providers and find the best fit to meet a specific requirement.

More On....Meeting Your Bandwidth Requirements For Supply Chain Management Applications

As I pointed out in a previous article, Supply Chain Management (SCM) is a complex animal. The key to a successful SCM implementation is a clear understanding of the business objectives and business requirements of the company the SCM primarily supports. This often includes a number of legacy systems which need to be integrated into the solution. From this will come the technical objectives to be met and the technical requirements that frame the solution. Only then will the commmunication requirements for bandwidth capacity, reliability, resiliancy, latency, security, and expandability be meaningful.

Here's just 2 such technical aspects.....

Frame Relay

Frame relay initially had several advantages over the alternative solutions for SCM and other multi site and multi company communications networks.

The first advantage was with circuit costs. For a multi site network, the traditional approach was a large number of point to point circuits. Each circuit required a router port, a CSU, and often a circuit monitoring module. With milage based pricing, each circuit represented a significant recurring cost on top of the initial hardware costs. Router sizing was often a factor of ports supported rather than performance capability.

Frame relay exchanged the point to point circuit costs with an access circuit, typically at less than 1/10th of the cost. With port speeds from DS0 to DS3, multiple sites could be connected with a single port at each site. A partial or full mesh, even with full redundancy, could be accomplished with very few router ports and CSU at each site. This represented significant capital savings.

Using fractional T1 and T3 on the access circuits, frame relay made expanding capacity between sites relatively painless. Port changes within the frame relay provider's network was often a configuration change. Expanding the actual circuits was typically a configuration change on the CSU and DACS.

Adding new sites was often accomplished with physical changes at the new site only. The new PVC across the frame relay network and at the existing site(s) was a configuration change. Depending on the routers used and the routing protocol implemented, this might be accomplished without a maintenance window.

The PVC approach allowed for additional security. A given location could be directed to a specific port within the DMZ, limiting the exposure of one's own network to other vendors within the SCM network. Firewalls at each end allowed each company to control its own security. The frame relay network was vulnerable to external monitoring at very few points, and the relationship of PVC traffic to specific customer required specific network design information.

Frame relay offered the ability to have a disaster recovery site support multiple locations. PVC between the disaster location and other locations could be defined in the configuration, allowing dynamic implementation of the disaster recovery network.

As a circuit protocol, frame relay functions independent of other protocols. This segmentation allowed IPX, IP, SNA, and other system communications protocols to be implemented over the same paths. If desired, each of these could have its own PVC and bandwidth, or they could all operate over a common path. Finally, the bandwidth and performance could be established specifically to site pairs on a PVC basis.

For a vendor that participated in multiple SCM networks, frame relay represented real cost savings. Instead of a new circuit for each network, a PVC could be established. Instead of 6 week circuit installation delays, service could be established in hours.

----

So why the past tense? The advantages of frame relay are now achieved via the Internet. The timeframes for implementation have been reduced from hours to minutes. Encryption has advanced beyond the security offered by isolated paths. Advances in application based routing can achieve availablity assurances. Legacy protocols have been largely replaced by IP.

There are still times when frame relay is the best choice based on business requirements or technical constraints. But a robust bandwidth network (e.g. OC3 or OC12 bandwidth....perhaps with GigE connectivity) applying IP protocols will enable a seemless flow of information without risking security concerns.

Emerging Technologies

The most notable is Radio Frequency Identification, or RFID. RFID tags are essentially barcodes on steroids. Whereas barcodes only identify the product, RFID tags can tell what the product is, where it has been, when it expires, whatever information someone wishes to program it with. RFID technology is going to generate mountains of data about the location of pallets, cases, cartons, totes and individual products in the supply chain. It's going to produce oceans of information about when and where merchandise is manufactured, picked, packed and shipped. It's going to create rivers of numbers telling retailers about the expiration dates of their perishable items—numbers that will have to be stored, transmitted in real-time and shared with warehouse management, inventory management, financial and other enterprise systems. In other words, it is going to have a really big impact.

Another benefit of RFIDs is that, unlike barcodes, RFID tags can be read automatically by electronic readers. Imagine a truck carrying a container full of widgets entering a shipping terminal in China. If the container is equipped with an RFID tag, and the terminal has an RFID sensor network, that container’s whereabouts can be automatically sent to Widget Co. without the truck ever slowing down. It has the potential to add a substantial amount of visibility into the extended supply chain.

Right now the two biggest hurdles to widespread RFID adoption are the cost of building the infrastructure and the lack of agreed-upon industry standards. But regardless...RFID implementation will be bandwidth intensive to retrieve and disseminate the mountain of information such a tool will provide.

Summary

The answer to how to meet bandwidth requirements for SCM applications is as complex as ever. The addition of emerging technologies like RFID into the mix of legacy point-to-point approaches, the frame relay darling, and the simplification afforded by OCx backed IP protocols....means your IT staff will be pegging their stress meter trying to make a decision. To navigate the aspect involving researching and acquiring the right bandwidth solution....do yourself a favor. Use the services of an independent unbiased consultant such as FreedomFire Communications to navigate the minefield for you. Your IT staff will love you for it.

What Bandwidth Backbone Makes The Most Sense For Networks In Africa, Middle East, And Latin America?

Given network infrastructure available in each region ... what bandwidth solution make the most sense (and why) for designing network solutions to meet business voice/data needs?

This is a difficult question to answer given the challenges faced by each region. The reality may be there is no easy answer. There is no "one size fits all" that covers all of these regions at once. So each must be treated seperately and distinctly to have any chance of success.

Some of the factors to consider likely deemed important would include business (e.g. type of business, number of locations in the network) technology (e.g. copper, fiber, wireless backhaul) economic (financing, ROI of implementation, budget), political (e.g. stable government, nationalized services, free market encouraged entrepreneurship), and regulatory (e.g. internal government restrictions, international connectivity limitations).

For example .... is a DS3 based solution viable for a multi-site WAN network in Nigeria? T1 for a single location in Brazil? Ethernet for a campus LAN in Bahrain?

These regions of the world are also commonly referred to as "developing nations", which is usually true of their infrastructure, and communications infrastructure included.

Persian gulf emirates ..... and to some extent Brazil (in the big metro areas) .... are well developed and you can expect the same telecom services to some extent as in the USA and Europe.

Elsewhere, availability is scarce and inconsistent.

For this reason many developing nations are focusing on cellular communications intending to "skip" the development of wireline infrastructure altogether. For example basing it on direct satellite service, like VSAT. There is of course the issue of delay with this approach that will effect voice and high-interactivity, so if delay is an important factor you may need to consider use of Iridium (not sure what's became of them ) or some other low-orbit satellites.

Before digging into the technical aspects for a Middle East or African network infrastructure one should look into the political situation. Most of these countries still have their local phone companies government owned. At best they are a monopoly directed by political powers and local rich people. Once you tap into the right people, these countries are more adopting of leading and bleeding edge technologies. Customers in these regions are more prone to using the "latest-&-greatest" mostly for novelty reasons. In the end, it does not matter why customers subscribe as long as the business is there!

In Africa there have been some improvements in the terrestrial subsea connectivity but that doesn't help much in reaching specific locations and providing backhaul. Similarly VSAT has been the traditional solution in Africa and some other remote regions but the proliferation of WiMax is generating increasing problems of interference. This is compounded by the unpredictable nature of licensing and controls. In my view Latin America has improved quite significantly in general access provision but quality and cost is still difficult to predict and manage. In the Middle East a lot of investment has and is taking place .... but here the biggest hurdle tends to be regulatory and the lack of an open market for supply.

A true "answer" can only be achieved by detailed study of IT and telecom prospects and existing infrastructure availability in each region. To this end the following factors should be considered;

Technology .....

This type of pursuit all depends upon types of services to be offered (like voice “Fixed or cellular”, leased circuits for WAN, broadband, Triple Play, IPTV, etc), users (e.g number of users, individual or corporate, scattered or concentrated), service coverage and existing available backbone network infrastructure (e.g. OFC network with PDH, SDH, DWDM or MW via PDH, SDH) .... then we could be able to forecast backbone bandwidth, evaluate existing available infrastructure, plan enhancements if required, select technology, and estimate the investment. The short answer is that T1, DS3, and OC3 bandwidth make sense if line infrastructure is readily available for tie in. Fiber makes better sense (ethernet) if grid is readily available and supported. If none of these are reasonably available in quantity than VSAT will continue as solution of choice with tie in to minimal hard line structure "nodes" where present.

Business/Economic ....

To prepare a business model, the factors would include by neccessity CAPEX, OPEX, NPV, IRR, revenue based on ARPU for a specific offered service, taxes, licensing fees, Inflation rate, decline in ARPU due to expected competition, last mile connectivity for corporate customer, and unforeseen costs in licensing/approvals and project rollout. This category seems the most self limiting over any technology challenges.

Regulatory / Administrative (Political) .....

The administrative factors involved would be different for each region ..... like monopolized regime and political situations in Africa and partially de-regulated environment in most of the countries in the Middle East ..... normally getting a license is a tricky job in many countries.

For each of the regions cited (Africa, Middle East, Latin America) .... depending upon your analysis per the above factors .... you may find that a realistic solution may be that a hybrid of technologies would be needed. For example, VSAT can offer a worldwide network and be integrated into terrestrial networks (T1, DS3, OCx, fast ethernet) where feasible and available. In the end there is no single solution that fits every scenario ... you must be flexible and innovative to target the right solution for each situation on it's own merits.

Who Is The Best Business Broadband Provider?

This question is often asked by IT staff at any given business …. but what they really mean is “who is the best business broadband provider …. for ME?” Even more specifically … “who can give me exactly what I need ….. where I need it …. to do what I have to do with my data/voice network?”

If you ask this ….. read on so you’ll be better positioned to ask the question in a more meaningful way; and get a response that makes the most business sense for your specific situation.

Most importantly ….. to get a complete and worthwhile answer ... there really needs to be more information provided which better describes exactly what your requirements are.

What is the exact location or locations? What is your budget? What applications must your network support (voice, data, multi-media, conferencing, number of users, 1 or more locations - single building or campus, etc.). What's your current usage? What’s your projected future usage? What do you have now (T1, DS3, etherent, etc.)? What’s your current uptime, latency, SLA, and QoS? Who's your current provider? Are you currently under a contract and when does it run out?

Don’t focus solely on speed … or price either. You also need to consider uptime, latency, packet forwarding, and other issues. Both in analyzing your current “state” …. and estimating your future “grow to”.

First start by asking yourself which applications you need to run over the link. People don't buy networks, they buy access to applications.

Then you need to look at the expected usage over the link. The profile of the applications is also important -- are they latency constrained? Are they bandwidth hogs? Is it sporadic access or sustained? Are you bringing Internet over the link?

How far apart are your sites (if this is a multi-site install)? Will that introduce latency? Is that latency going to be a problem?

You also have to look at what you can get. Maybe all you can get is a T1.

Depending on the answers above, you might also need to look at WAN acceleration, Citrix, or other such technologies to get around application limitations. Some applications just don't work well when they're separated by their users by more than a few milliseconds.

That said .... initially I'd lean toward a T1; probably integrated (voice and data). But that will depend on number of users and load (video conferencing, large multi-media file sharing, etc.) and so forth. You might need to go bonded T1 or DS3 (T3) bandwidth if your load/usage is large. If available, ethernet should be an option at least from a cost effectiveness standpoint.

As for a provider .... shop around. Remember that location is key when buying broadband. Use a consultant who can talk the language and negotiate for you. If you do this yourself you'll get frustrated, spend a lot of time and effort, and likely be talked into something you really don't need ... at a cost more than you should pay. If you’d like free help with this …. I strongly recommend the no cost services at:

Compare Business Broadband Providers

Moving To MPLS Network Architecture From WAN Architecture

You're tasked with investigating if moving your company's network from a point-to-point T1 WAN architecture to a MPLS architecture makes business sense.

The easy answer here is yes.

But .... why?

In looking at changing your architecture from Point to Point to an MPLS type of network I suggest starting with the business requirements and tying your network requirements to the business needs. In this manner, you'll have clear business outcomes which you can negotiate back with you're business when you start getting the cost vs benefits discussion in developing your business case for investment.

A robust Total Cost of Ownership model will be needed to understand what the TCO will be gonig forwards. Also, I'd suggest developing a strong understanding of the costs of doing nothing and also the potential savings or new revenue opportunities for your business so you can develop a Net Present Value (NPV) of your network options.

I would also recommend looking at the interfaces you're looking to support in the network. MPLS does enable you to have a common protocol across all your networks and you can effectively establish an MPLS Cross Connect in your network. This will rely on how your local service providers will provide MPLS services to you, if at all. So you would most likely need to purchase either point to point or point to multipoint based transmission services from your provider. We're seeing that many enterprises and service providers are heading towards ethernet ubiquity as a service interface and then offering multiple services ontop of the ethernet interface.

VoIP works well across an MPLS type of network, however it does depend on the services that you purchase off your service provider. As you're looking at MPLS, then I assume that you're looking at buying straight transmission services and then you'll use MPLS to aggregrate traffic into your WAN links. Hence, you're business case is going to be driven by arbitrage opportunities so capture as much traffic as possible onto your network and apply QoS at the edge.

From a QoS perspective, ensure that you can also apply policing to the traffic that goes onto your WAN traffic. I recommend applying Heirarchical QoS as this will enable you to dynamically share the bandwidth in your WAN links.

As you can tell, there are lots of issues and questions that need to be addressed so I'd suggest working closely with some trusted partners and driving towards an outcome based business drivers and commercial outcomes.

We have worked with many customers that have migrated to MPLS from old school point to point. There are a few reasons our customers did this, but let me assure you the #1 reason was cost. A good competitive carrier will offer an MPLS solution that is sometimes less costly than the old point to point type solution ..... with most of the same or more functionality.

But there are some factors:

1. If the point to points are crossing state or lata boundaries ..... or are fairly separated by miles .... you should enjoy considerable savings.

2. If you get a carrier that bundles MPLS with an Integrated Access type solution you will save big money (combination of voice, internet & MPLS delivered on one T1 with quality of service).

Here's some additional points that might help you.

1. Is it redundant? Yes, depending on how you design your network (we can help you of course) sites can network with each other over your wide area network for disaster recovery/ redundancy. Unlike the traditional point to point architecture where you might only be as strong as that single link. We helped a huge national company with a migration from point to point and frame relay to MPLS. The big reason was with so many sites there was an outage almost every day. The network was designed with redundancy as the main driver.

2. Does it work as well? It depends who you ask. Are you talking to a salesman? He will say yes. Let me give you my "consultant" opinion. It works ALMOST as well but there are so many benefits to MPLS that typically motivate a customer to change. For example, if you have Quality of Service (QoS) sensitive applications running accross your WAN then you should consider MPLS. MPLS is a private networking technology similar to the concept of Frame Relay in that it is delivered in the "cloud". The primary difference with MPLS is that you can purchase quality of service for applications across your WAN. During the provisioning process the carrier (or your agent-wink wink) will interview you in order to determine which appications are important to your business, they will then build a QoS template to service these applications on your WAN. These applications will be given priority over all other traffic in times of peak load. MPLS is by far the most costly solution between Frame Relay, VPN and MPLS .... but is the only technology that will support QoS!

But let's put the salesman aside and remember one thing. With MPLS we are using the carrier's private network which is infinitely better than creating your own VPN. But because of some "overhead" and the belief that all carriers over-subscribe somewhat I am convinced that it's ALMOST as good.

So if it's almost as good would it be worth migrating if you could enjoy cost savings & redundancy??? Maybe. But these are the things that are making MPLS the hot ticket now.

3. Does this work well with VOIP? Sure. You can get QoS like I stated above.

MPLS is an IP-based framing technology (at OSI layer 3) that inherently meshes your WAN (this is the redundancy you refer to above). MPLS has a feature called QoS or quality of service. This feature allows both your CPE router and the carrier's network to prioritize data based upon your settings or preferences (carrier's level of support of QoS can be broad) and gives you more "bang for your buck" with the bandwidth that you select for the local loop going to each office. MPLS is made for VoIP like RC Cola is made for Moonpies. Because true "toll quality" VoIP requires prioritization across a carrier network, you (or your provider) can tag VoIP traffic with high priority to easily address the jitter and latency sensitivity inherent in the service.

The other huge advantage you have is that you can add locations with a simple routing table update and maintain a fully-meshed architecture, where with Point to Point circuits, you would have had to add a separate circuit to each location you want to interconnect, making MPLS more and more cost friendly the more locations you add.

Finally, MPLS allows you (or your carrier) to configure network objects (such as servers, VPN concentrators, and Network-Based Firewalls) as nodes on your MPLS network. For instance, with a properly deployed Network Based Firewall, you can provide all of your locations with an internet connection over your MPLS network that doesn't rely on a single location to aggregate the traffic. Some carriers even offer redundant firewalls, meaning that you have redundant Internet connections fully meshed giving you more potential up-time in the case of a single failure on your network.

What do you need to consider? In my experience, the biggest things to keep in mind are:

- Stay away from MPLS enabled Frame/ATM networks with committed access rates (CAR), this committed access rate is often a lower bandwidth than your local loop bandwidth, which can degrade your quality and quantity of bandwidth across a carrier's network (its always in the fine print).

- QoS at the "Edge" and across the "Core" - choose a carrier with both.

- QoS recognition across the carrier network - some carriers will allow customers to mark packets with priority, but will not recognize and uphold that priority, don't fall into this trap.

- SLA guarantees - be sure to choose a carrier that provides acceptable service level agreements for the type of service you plan to push across your network

- Customer Service and dedicated sales rep - you want someone you can reach out to with questions that you can trust - this is the most difficult thing to find.

For FREE assistance designing the right MPLS configuration for your network .... AND sourcing the most cost effective provider ..... take advantage of the help available via:

MPLS Networks