CCNA 1 and 2 Companion Guide, Revised (Cisco Networking Academy Program) part 100

appen_a.fm Page 959 Tuesday, May 20, 2003 4:54 PM The Cabling Business 959 As-built drawings are not created until all cables are placed, all jacks are installed, and all cables are terminated. Drawing can begin while final testing is taking place, but assurances must be made that no changes or additional work is done that is not reflected accurately in the drawings. Floor plans, furniture plans, or T drawings usually are used as the basis for as-built drawings. The contractor is not required to redraw the building plans for the as-built drawings. The contractor draws all cable runs, terminations, and outlets, and supplies all labeling information as it was installed. The punch list is the checklist that the customer provides the contractor with when the contractor considers the project complete (see Figure A-53). Figure A-53 Typical Punch List Punch List The punch list is a list containing items that were not completed (missing outlets or cable runs, for example), items that were completed unsatisfactorily (cables not fastened to ladder racks or outlets that do not work, for example), or cleanup items (debris left in corridor, for example) that the customer requires corrected before approval for final payment. The punch list can take the form of the customer’s final acceptance of the project. When the items on the punch list are completed to the customer’s satisfaction, payment is expected. appen_a.fm Page 960 Tuesday, May 20, 2003 4:54 PM 960 Appendix A: Structured Cabling Case Study: FARB Software Development, Ltd.: Network Design and Implementation Lab exercises give you the opportunity to practice the manual skills portion of structured cabling installation. The case study is designed to give you a hands-on opportunity to participate in the design of a structured cabling system for a fictitious software-development company that is occupying a new three-story building and requires it to be built out. Overview To complete this case study, you should be able to Gather information for the preinstallation process and lay plans for the installation process Create documentation as would be required for creating a real network Comply with TIA, EIA, and electrical standards Using this supplement, as well as having mastered the CCNA 3 curriculum, will prepare you to complete many tasks related to real-world network creation. These objectives are spelled out within this case study in a letter from Cheryl Farb, president of FARB Software Development, Ltd., who, for this case study, is serving as the client company. The following are some review items that will help you to focus on the case study. General Design Process Framework Network design is best done by following a framework. Determining where the wires go requires knowledge of the structure of the networks. You will need to know where the users are and what their applications are before you can begin to sketch out a viable network. A Layer 1 LAN logical and physical topology must be developed. This development includes the type of cable and the physical (wiring) topology that are selected, as well as the physical placement of infrastructure connection points on the network. A Layer 2 segmentation plan must be overlaid on the previously created Layer 1 topology. This layer plan includes devices added to the topology to improve its efficiency and functionality. Examples of these devices might be switches and bridges. This layer also includes the use of technologies such as microsegmentation, virtual LANs (VLANs), and the Spanning Tree Protocol (STP), to add efficiency and reliability. A Layer 3 hierarchical plan then is overlaid on both of the previous two layers. This plan includes adding Layer 3 devices that will provide intranetwork and internetwork functionality to the network, as well as creating a network address plan. Layer 3 is appen_a.fm Page 961 Tuesday, May 20, 2003 4:54 PM Case Study: FARB Software Development, Ltd.: Network Design and Implementation 961 where routing and firewalls are implemented, imposing a logical structure on the net-work. They also can be used for segmentation of both collision and broadcast domains. An extension of the Layer 3 plan might be considered a Layer 4 plan. This plan could be laid over the first three; it moves strictly to software and controls access and avail-ability of the network. It involves access lists and firewall configuration. Although a complete network design keeps moving up the OSI model, it is beyond the focus of this project. This design focuses on Ethernet, IP, Layer 1, Layer 2, and Layer 3, which is the focus of this curriculum. The design process logically flows up the layers of the OSI model. That said, it is important to remind ourselves of one of the purposes of structured cabling. The cabling system must be able to withstand change and growth over its life of service. Odds are good that most companies will be in different quarters by the time their structured cabling system is worn out. This means that care must be taken to not follow the current network layout so closely that the cables are not good for any other organization that may follow. An appropriate structured cabling system may be said to fit the network today, but accommodate easily the network of tomorrow. The most important—and, many times, the most neglected—part of network design and operation is the documentation. The main focus of this project is the documentation of the network design. Documentation for this project should include wiring maps, addressing schemes, any brainstormed ideas, problem-solving matrices, and any other notes made while making these determinations. Predesign Process Before a network can be designed, the data needed to design the network must be gathered. For a network to be effective and serve the needs of its users, this data should be gathered according to a systematic series of preplanned steps. These steps provide a guide to completely discover the data needed to create the network. The first step in the process is to gather information about the organization. This information should include the following: Organization history and current status Projected growth Operating policies and management procedures Building diagrams (blueprints) Existing network diagrams and documentation Office systems and procedures Viewpoints of the people who will be using the LAN appen_a.fm Page 962 Tuesday, May 20, 2003 4:54 PM 962 Appendix A: Structured Cabling In the information packet that follows this section, you will find communications from the president outlining FARB Software Development, Ltd. This document exists at FARB Software Development LTD.doc. In this letter, Farb indicates her specific requirements for this project. The second step is to make a detailed analysis and assessment of the current and pro-jected requirements gathered in the first step. This step identifies and defines issues or problems that need to be addressed (for example, a remote room in the building might not have network access). It also provides information about future network expansion needs, access, and security. The third step is to identify the resources and constraints of the organization. Organi-zation resources that can affect the implementation of a new LAN system fall into the categories of hardware, software, and human resources. If this were a network expansion or upgrade, existing computer hardware and software would have to be documented. Identification and definition of those projected needs also must be done. The answers to some of these questions also will help determine how much training will be required and how many people will be needed to support the LAN. The questions asked should include the following: What are the financial resources of the organization? How are these resources currently linked and shared? How many people will be using the network? What are the computer skill levels of the network users? What are the attitudes toward computers and computer applications? Following these steps, documenting the information in the framework of a formal report will help estimate costs and develop a budget for the implementation of a LAN. Design Methodology and Deliverables With the material that has been presented to this point, a strong foundation and understanding should have been developed for the concepts of a layered communica-tions model. Using the OSI model as the framework, an understanding of the functions and devices that support operations at those layers also should have been gained. To perform this case study, material related to the physical design and installation of a network must be learned. As was presented in previous material, rules and standards govern how a network is designed and built. These rules and standards must be learned before the actual case study can be performed. appen_a.fm Page 963 Tuesday, May 20, 2003 4:54 PM Case Study: FARB Software Development, Ltd.: Network Design and Implementation 963 Students completing this lesson should be able to Develop a Layer 1 and 2 topology Gather information for both the preprocess and the process Create documentation during the course of the process Comply with TIA, EIA, and electrical standards Note that this aligns with Farb’s requests for her company’s project. Standards Organizations When designing and building networks, it is necessary to ensure compliance with all applicable fire codes, building codes, and safety standards. Perhaps the most important part of the network-design process is designing according to the EIA/TIA and ISO/IEC industry standards. The focus in this curriculum is on the standards for networking media that have been developed and issued by the following groups: ISO—International Organization for Standardization (not an acronym—see glossary) IEEE—Institute of Electrical and Electronics Engineers UL—Underwriters Laboratories EIA—Electronic Industries Alliance TIA—Telecommunications Industry Association The latter two organizations jointly issue a list of standards called the TIA/EIA standards. In addition to these organizations, local, state, county, and national government agencies issue specifications and requirements that can impact the type of cabling that can be used in a local-area network. It is also important to understand that these standards are being reviewed constantly and are updated periodically to reflect new technologies and the ever-increasing requirements of voice and data networks. Just as new technologies are added to the standards, others are dropped or phased out. In many cases, a network might include technologies that are no longer a part of the current standard or that are being elimi-nated. Typically, this does not require an immediate changeover, but these older, slower technologies eventually are replaced in favor of faster ones. Standards Definitions The primary standards that will affect layer design have been created by the TIA/EIA. The Telecommunications Industry Association (TIA) and the Electronic Industries Alli-ance (EIA) are trade associations that jointly develop and publish a series of standards ... - tailieumienphi.vn