I am currently in charge of a LAN environment with over 3000 nodes. We have a remote site that connects the LAN via three T-1 lines. Obviously their connection is slow. We are about to double the amount of users at the location and the question has been posed whether the need for a T3 is eminent or if we should simply add more T1s. I am a LAN guy, and I do not know that much about T1 bandwidth restrictions. Do you have any recommendation on determining this? I have about a month of performance logs for the three circuits and though the average usage is around 30-40% it does spike into the 80-90% region during peak hours. I think it should also be noted that we utilize Microsoft AD, and many other server centric applications that need to be accessed for each login. E-mail traffic resides at another remote site with a T3 link, so for these users to access e-mail they have to connect back to our LAN, and then over a T3 to another LAN to get e-mail. Any help or recommendation is very much appreciated.
Thanks in advance,
You've certainly got a big project ahead of you and I strongly believe you can make the correct decisions if you carefully plan everything out.
Due to the size of your project, you can understand it's almost impossible for me to get a clear picture of your LAN/WAN requirements, available equipment and budget, to make a suggestion that will provide you with the necessary answers you are looking for. However, there are a few guidelines you can make use of that can help you stay on the right track.
T1 lines can provide a maximum of 1.544 Mbps. You mention you've got three such lines, giving you a capacity of 4.632 Mbps which run at 30-40% during the day, but peak up to 80-90% at times.
Since you are doubling the amount of workstations, you will most certainly need to upgrade your lines to serve the new clients because according to your current statistics, you can expect a 70-80% load average when the clients are installed. The problem here though isn't how many additional lines you should install. I find it far more important to firstly understand where the traffic is going, then, based upon your findings, make the necessary decisions.
For example, you mention Microsoft's Active Directory is running throughout your WAN alongside with other server-centric applications. You'll need to figure out what the bandwidth requirements are for each of these services. Once this is done, you can easily calculate the required bandwidth for your clients. Obviously, any excess traffic would be classified as Internet traffic (email, Web etc). Considering the importance of each application, you can then classify the traffic and provide a higher priority to your network applications ensuring they are not starved by Internet (or other) traffic.
When you've successfully managed to obtain a complete view of your traffic needs, taking into consideration possible redundant connections, you can then decide if you should.
Again, because you are talking about 6,000+ clients, I strongly advise you layout your traffic needs, break them into categories and then priorities. From that point, you'll know exactly what you need to do.
In closing, keep in mind that we are currently preparing a very interesting article on the ISDN protocol where you'll be able to obtain a lot of information regarding the protocol, T1, T3 lines and much more.
Dig Deeper on Network Infrastructure
Related Q&A from Chris Partsenidis
A MAC address and an IP address each identify network devices, but they do the job at different levels. Explore the differences between the two and ... Continue Reading
Expert Chris Partsenidis explains what iPerf is and how iPerf commands can help you measure your network's bandwidth, delay, jitter and potential for... Continue Reading
SFP ports enable Gigabit switches to connect to a wide variety of fiber and Ethernet cables in order to extend switching functionality throughout the... Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.