Download Designing Large Scale LANs by Kevin Dooley PDF

By Kevin Dooley

This precise booklet deals a vendor-neutral procedure for designing huge neighborhood zone networks in accordance with enterprise or organizational wishes, instead of from a product point of view. writer Kevin Dooley outlines "top-down community design" for development a technological infrastructure to suit your organization's necessities, a procedure way more powerful and reasonably-priced than becoming the association to the parameters of a shrink-wrapped proprietary answer. Designing Large-Scale LANs covers every little thing from safety, bandwidth and scalability to community reliability, such as backup, redundancy, and issues of failure. particular applied sciences are analyzed in aspect: community topologies, routing and switching options, instant, digital LANs, firewalls and gateways, defense, web protocols, bandwidth, and multicast companies. The e-book additionally discusses proprietary applied sciences which are ubiquitous, equivalent to Cisco's IOS and Novell's IPX. this entire advisor to top-down community layout can help you opt the appropriate community strategies. If you're designing huge scale networks and want professional recommendation and tips, glance no extra than Designing Large-Scale LANs.

Show description

Read or Download Designing Large Scale LANs PDF

Best networking books

Wireless Technology: Protocols, Standards, and Techniques

Enormous, complicated applied sciences, numerous proper subject matters, doubtless unlimited documentation of criteria and suggestions… In a box as dynamic as instant know-how, how is one to take care of while the very activity of determining which courses to learn and which assets belong in your shelf might be daunting?

Additional info for Designing Large Scale LANs

Example text

As a quick aside, consider how N+1 redundancy works for larger values of N. How much can the situation be improved by adding one extra hot standby? In other words, I want to compare the probability for one failure out of N with the probability for two simultaneous failures: 34 and: So 2Pn / 1Pn ~ n/4m. This means that as long as N is much smaller than 4 times the MTBF in days, the approximation should be reasonable. But, for example, if the MTBF were 100 days, then it would be a very bad idea to use N+1 redundancy for 25 components.

The result can be routing loops, or just slow unreliable response across the network. 38 The most common reason for convergence problems at either Layer 2 or 3 is complexity. Try to make it easy for these processes by understanding what they do. The more paths available, the harder it becomes to find the best path. The more neighbors, the worse the problem of finding the best one to pass a particular packet to. A broadcast storm is a special type of problem. It gets mentioned frequently, and a lot of switch manufacturers include features for limiting broadcast storms.

This means that as long as N is much smaller than 4 times the MTBF in days, the approximation should be reasonable. But, for example, if the MTBF were 100 days, then it would be a very bad idea to use N+1 redundancy for 25 components. In fact, it would probably be wise to look at N+2 or better redundancy long before this point. The same prescription can be used for calculating the probability of failure for an entire network. Consider the network shown in Figure 2-1 and Figure 2-2. How much has the network's net MTBF improved by making the Core redundant?

Download PDF sample

Rated 4.40 of 5 – based on 48 votes