Designing large-scale LANs
This unique book offers a vendor-neutral approach for designing large local area networks according to business or organizational needs, rather than from a product perspective. Author and independent network design consultant Kevin Dooley outlines ""top-down network design""...
| Autor principal: | |
|---|---|
| Formato: | Libro electrónico |
| Idioma: | Inglés |
| Publicado: |
Sebastopol, California :
O'Reilly
2002.
|
| Edición: | First edition |
| Materias: | |
| Ver en Biblioteca Universitat Ramon Llull: | https://discovery.url.edu/permalink/34CSUC_URL/1im36ta/alma991009627193106719 |
Tabla de Contenidos:
- Designing Large-Scale LANs; Organization; Conventions Used in This Book; Comments and Questions; Acknowledgments; 1. Networking Objectives; 1.1.2. Geography; 1.1.3. Installed Base; 1.1.4. Bandwidth; 1.1.5. Security; 1.1.6. Philosophical and Policy Requirements; 1.2. OSI Protocol Stack Model; 1.2.1.2. Layer 2; 1.2.1.3. Layer 3; 1.2.1.4. Layer 4; 1.2.1.5. Layer 5; 1.2.1.6. Layer 6; 1.2.1.7. Layer 7; 1.2.2. Where the OSI Model Breaks Down; 1.3. Routing Versus Bridging; 1.4. Top-Down Design Philosophy; 2. Elements of Reliability; 2.1.2. Performance Is a Reliability Issue; 2.2. Redundancy
- 2.2.2. Redundancy by Protocol Layer2.2.3. Multiple Simultaneous Failures; 2.2.4. Complexity and Manageability; 2.2.5. Automated Fault Recovery; 2.2.5.2. Intrinsic versus external automation; 2.2.5.3. Examples of automated fault recovery; 2.2.5.4. Fault tolerance through load balancing; 2.2.5.5. Avoid manual fault-recovery systems; 2.2.6. Isolating Single Points of Failure; 2.2.7. Predicting Your Most Common Failures; 2.2.7.2. Multiple simultaneous failures; 2.2.7.3. Combining MTBF values; 2.3. Failure Modes; 2.3.2. Traffic Anomalies; 2.3.3. Software Problems; 2.3.4. Human Error
- 3. Design Types3.1.1.2. Ring topology; 3.1.1.3. Star topology; 3.1.1.4. Mesh Topology; 3.1.2. Scalability; 3.2. Reliability Mechanisms; 3.2.1.2. Spanning Tree activates backup links and devices; 3.2.2. Layer 3 Recovery Mechanisms; 3.3. VLANs; 3.3.2. Protocol-Based VLAN Systems; 3.4. Toward Larger Topologies; 3.4.1.2. Backbone capacity; 3.4.1.3. Backbone redundancy; 3.4.2. Distributed Backbone; 3.4.2.2. Trunk fault tolerance; 3.4.3. Switching Versus Routing; 3.4.3.2. Modernizing the old rule; 3.5. Hierarchical Design; 3.5.1.2. Redundancy; 3.5.1.2.2. Physical diversity; 3.5.1.3. Filtering
- 3.5.1.3.2. Filtering for application control3.5.1.3.3. Policy-based routing; 3.5.2. Switching and Bridging Strategies; 3.5.2.2. Redundancy in bridged networks; 3.5.2.3. Filtering; 3.5.3. VLAN-Based Topologies; 3.5.3.2. Trunking through a router; 3.5.3.3. Trunks; 3.5.3.3.2. Trunk redundancy; 3.5.3.3.3. Trunks on servers; 3.5.3.4. VLAN Distribution Areas; 3.5.3.5. Sizing VLAN Distribution Areas; 3.6. Implementing Reliability; 3.7. Large-Scale LAN Topologies; 3.7.2. Routers in the Distribution Level; 3.7.3. Routers in Both the Core and Distribution Levels; 3.7.4. Connecting Remote Sites
- 3.7.5. General Comments on Large-Scale Topology4. Local Area Network Technologies; 4.1.2. Installed Base; 4.1.3. Maintainability; 4.1.4. Performance; 4.2. Ethernet and Fast Ethernet; 4.2.2. Collision Detection; 4.2.3. Hubs, Bridges, and Switches; 4.2.4. Transceivers; 4.3. Token Ring; 4.4. Gigabit and 10 Gigabit Ethernet; 4.4.2. Gigabit as a Backbone Protocol; 4.5. ATM; 4.6. FDDI; 4.7. Wireless; 4.8. Firewalls and Gateways; 4.9. Structured Cabling; 4.9.2. Vertical Cabling; 5. IP; 5.2. IP-Address Classes; 5.3. ARP and ICMP; 5.3.2. ICMP; 5.4. Network Address Translation
- 5.5. Multiple Subnet Broadcast
