[...]... are many types of networks: local area networks (LANs), wide area networks (WANs), metropolitan area networks (MANs), campus area networks (CANs), Ethernet networks, Token Ring networks, Fiber Distributed Data Interface (FDDI) networks, Asynchronous Transfer Mode (ATM) networks, Frame Relay networks, T1 networks, DS3 networks, bridged networks, routed networks, and point-to-point networks, to name... the network (even if it’s just master/slave or primary/ secondary) The machines on a network are often connected physically via cables However, wireless networks, which are devoid of obvious physical connections, are connected through the use of radios Each node on a wireless network has an address Frames received on the wireless network have a specific source and destination, as with any network Networks... propagating it to the remaining hubs in the network This design replicates the backbone idea, in that every device on the network will receive every frame sent on the network Figure 2-5 Hub-based network 8 | Chapter 2: Hubs and Switches In large networks of this type, new problems can arise Late collisions occur when two stations successfully test for a clear network and then transmit, only to encounter... 624 626 626 35 Designing Networks 627 Documentation Requirements Documents Port Layout Spreadsheets IP and VLAN Spreadsheets Bay Face Layouts Power and Cooling Requirements Tips for Network Diagrams Naming Conventions for Devices Network Designs Corporate Networks Ecommerce Websites Modern Virtual Server Environments Small Networks 627 628 629 633... the CIO calls the network a WAN, but the engineers call the network a CAN, you must either educate whoever is wrong or opt to communicate with each party using its own language This issue is more common than you might think In the case of MAN versus WAN versus CAN, beware of absolutes In other areas of networking, the terms are more specific For our purposes, we will define these network types as follows:... connecting several computers to a network In Ethernet network design, repeaters and hubs are treated the same way The 5-4-3 rule of Ethernet design states that between any two nodes on an Ethernet network, there can be only five segments, connected via four repeaters, and only three of the segments can be populated This rule, which seems odd in the context of today’s networks, was the source of much... not have a presence on the network (except possibly for management purposes) They do not alter frames or make decisions based on them in any way Figure 2-4 illustrates how hubs operate As you might imagine, this model can become problematic in larger networks The traffic can become so intensive that the network becomes saturated—if someone prints a large file, everyone on the network will suffer while... network at any given time Should all of the stations be active, the network will appear to be slow because of the excessive collisions Figure 2-3 Repeater joining hubs Figure 2-4 Hubs repeat inbound signals to all ports, regardless of type or destination Collisions are limited to network segments An Ethernet network segment is a section of network where devices can communicate using Layer-2 MAC addresses... collision domains A collision domain is an area of an Ethernet network where collisions can occur If one station can prevent another from sending because it is using the network, these stations are in the same collision domain A broadcast domain is the area of an Ethernet network where a broadcast will be propagated Broadcasts stay within a Layer-3 network (unless forwarded), which is usually bordered by... in a properly designed network If you connect two switches with a crossover cable—one configured with VLAN 10 on all ports and the other configured with VLAN 20 on all ports—hosts plugged into each switch will be able to communicate if they are on the same IP network Broadcasts and IP networks are not limited to VLANs, though it is very tempting to think so Figure 2-5 shows a network of hubs connected . class="bi x0 y0 w0 h1" alt="" Network Warrior SECOND EDITION Network Warrior Gary A. Donahue Beijing • Cambridge • Farnham • Köln • Sebastopol • Tokyo Network Warrior, Second Edition by Gary A. Donahue Copyright. History: June 2007: First Edition. May 2011: Second Edition. Nutshell Handbook, the Nutshell Handbook logo, and the O’Reilly logo are registered trademarks of O’Reilly Media, Inc. Network Warrior, the image. 634 Tips for Network Diagrams 636 Naming Conventions for Devices 637 Network Designs 639 Corporate Networks 639 Ecommerce Websites 643 Modern Virtual Server Environments 648 Small Networks 648 36.