How to determine how much bandwidth your business needs for network infrastructure, computer


Image : http://www.flickr.com

I suggest a path that is easier said than done? The first step is an inventory of what you have, the second step is a measure of the QoS in real terms you are getting … and if you can do one and two and three should be to understand what you really need to eliminate or improve.

I noticed that throwing bandwidth at problems is a very typical approach and NA-band Europe has always been most expensive so companies have tended to be moreefficient.

A sector that you can consider is that if you have T1, E2, fractional DS3, OC3, MPLS, etc. (oh let's throw phones, VoIP, TDM and any other part of the alphabet soup) …… probably do not have a network architecture and certainly do not have a center of "entity" responsible for optimization.

So, inventory, contract review, shorten / lengthen contracts for co-termination, and use this time to build a real solution and an effective competitive RFI(Ask the vendors for their best ideas) an RFP (to marry the best ideas of all providers) and a final contract. Bearing in mind the 80:20 rule of using a "wild card" to keep the leading supplier in a certain degree of control of the competition.

The other piece of the puzzle you must also consider the use of WAN acceleration equipment in each branch. For your private WAN infrastructure (MPLS VPN, etc.), and many companies are evaluating, deploying or have already deployed WANaccelerator appliances. These devices are truly changing the IT landscape so that they are a necessary technology for IT environments more recently.

So, without getting off topic. In our experience, "most" companies using WAN acceleration technology with branches that are less than 60 users can go out only with the installation of a private WAN T1 connection. Even with VoIP and other applications for large pushed to the edge. The majority of host sites or disaster recovery sitesusually require a full or partial NxT1 T3 connections.

Please understand that there are a lot of variables that relate to:

-Types of users

-Applications

-Backup

Etc.-Replica

To crack down just follow this checklist:

1 – Baseline the network to know which applications are running on it and how much bandwidth each is using.

2 – Identify the critical applications and determine the bandwidth requirements for adequate performance foreach.

Three – Locate the "junk" applications such as "Bug Weather", internet radio, etc., which may be limited to little or no band.

4 – Refine your output as well as inbound traffic on all firewalls.

5 – Write the ACL for your router or L3 MDF and log violations to you console management and analysis of results.

6 – Start QoS

7 – To build a laboratory that is the hardware and software infrastructure of your LAN / CAN / MAN / WAN network / WLAN and new testquestions to test how the current configuration will effect bandwidth.

8 – Be proactive how to control the use of bandwidth and is growing at a rate roughly constant recommend and add additional bandwidth before creating a bottleneck.

Armed with the above information …. and with patience and attention ….. you should get a solid solution for the bandwidth best solution for your network. If you want to help free the process ….. let us know.

January 16, 2011. Tags: , , , , , . computer network. Leave a comment.

How do you determine the right network (WAN) architecture for a computer network?

One of the most complicated decisions to make for an IT department about the architecture of a multi-site voice / data network. If the network is based on simple point-to-the bandwidth of T1 circuits? How about bandwidth burstable DS3 or maybe just one cloud band OC3? No matter the bandwidth chosen …. the most efficient design should be based on a backbone of communication configuration MPLS (Multi-Protocol Label Switching).

To get there, first of allin deciding about the architecture of any WAN communications network organization is necessary to determine ….

– How many points you want to connect?

– Architecture – hub and spoke or mesh architecture?

– What applications will run on the network …. Voice, Video, Data, all of the above?

– Exactly which applications will run in the event of data?

– What will each take the% of your QoS, the total of all three should be100%?

– Voice is the premium level of QoS and therefore the most expensive as it is a real-time communication, followed by the video and then.

– How many people are just using the network at any given point of time in each location?

– What will be the competition factor? If you are looking for competition 100% or you can do with less competition?

– What is the scope of scalability in every home and place hub?

– Internet access alsobe given to users?

– Internet in a central location, can help implement and enforce various security policies of your organization.

– Do you want to access network resources to a mobile user?

The answer to all these questions will help to achieve the bandwidth required for each MPLS hub and spoke about the position.

Honestly, no organization should ideally try to do this calculation yourself. Instead they can hire a consultant or atelecommunications service provider to do this activity because they are experts in designing this solution. With their help you can easily decide the bandwidth for each location, select suitable router, make plans to dismiss, the routing of traffic on the routes of the Atlantic or Pacific, blah blah.

To help walking through the analysis …. and determine the best solution …. take advantage of free help to DS3-Bandwidth.com.

Ideally I would also recommend that you give freedom to provide and managethe router at each location of service provider Telecom. Then it becomes a managed solution and the service provider can easily monitor the network in case of interruption. They then log into the router remotely and manage the complete network and giving greater uptime SLA.

At the end …. take a deep breath and work through the steps above. Following this simple game plan will take the right decision for the network of organizationsarchitecture.

December 17, 2010. Tags: , , , . computer network. Leave a comment.

Design a site like this with WordPress.com
Get started