Designing Large Scale Lans

Preface

Computer networks are like any complex engineering project. A small network can be slapped together quite successfully with minimal experience. But a larger network requires careful thought and planning. As with many types of engineering projects, this planning and design phase is best served by an organized and disciplined design philosophy. The trouble with design is that it is difficult to differentiate between personal or near-religious biases and sound ecumenical strategies that can result in better usability, stability, security, and manageability.

Everyone has religious biases when it comes to network design. This is because most networks are so complex that a feeling of black magic falls over anybody trying to understand them. They tend to be too large and too intricate to hold in your mind all at once. So when some particular incantation appears to work miracles, it is adopted as an article of faith. And when a vendor's equipment (or support engineer) saves the day in some important way, it can turn into a blanket belief in that vendor as savior.

So, in the interests of making plain my assumptions and biases, let me explain right from the start that I am a network agnostic. I have used equipment from most of the major vendors, and I believe that every individual piece of gear has its pluses and minuses. I prefer to use the gear that is right for the job, rather than expressing a blind devotion to one or another. So this book is vendor neutral.

I will discuss some ...