Normally, you would take a top-down approach in designing a LAN/WAN. This means that you first analyze the applications that you will use across the WAN, and determine the types of sites you will be connecting together. For examples, if you have a mission critial application from branch sites that must connect to central sites, and requires X amount of bandwidth, then you know you must get a link of X type. When cost is a major factor, you have to weigh the cost/benefit of the available connectivity options -- high price/high reliability vs. lower price/lower reliability. What is the cost to the business if the application can't perform it's function? There's a lot to consider.
Basically, the applications and availability requirements will dictate what kind of WAN you plan initially, and the type of WAN connectivity available in your area will dictate what kind of WAN you finally design/implement.
Hi everyone, I would like to thank you in advance for any help you can provide a newcomer like myself!
Im studying the 100-105 book by Odom and am currently on the topic of Port security. I purchased a used 2960 and I'm trying to follow a...
While deploying a number of 18xx/2802/3802 model access points (APs), which run AP-COS as their operating platform. It can be observed on some occasions that while many of their access points were able to join the fabric WLC withou...
I am going to design and build an LAN network under a tunnel underground with long distance between the switches.
I will have 2 Catalyst switches and 8 Industrial IE3000, and they will be connected with fiber.
For now I am planning on use Layer-2 s...