рroposаl will bе submitted in three major parts: Springfield Device and STP Configurations (i.e., Part 1) Worchester Subnetting Configurations and Boston Site Protocol, Route Summarization, and Topology Improvement (i.e., Part 2) Sacramento Site VLAN, Routing on a Stick(ROS) and DHCP Implementation, Los Angeles Site Management Technologies, xACME WAN WAN Implementation and Security Communications (i.e., Part 3) The details for each of these Part (i.e., Part 1, 2, and 3) can be found below. Each of these parts will be submitted to the LEO Assignments folders and TurnItIn. Each of these parts should be submitted independently of the other parts. That is, only submit Part 1 to the LEO Assignments Cisco Network Proposal Part 1 submission folder. Only submit Part 2 to the LEO Assignments Cisco Network Proposal Part 2 submission folder. And, only submit Part 3 to the LEO Assignments Cisco Network Proposal Part 3 submission folder. Along with the challenges presented in this document, you will be provided an overall site topology to work from, as well as specific device configurations (where applicable) to make your recommendations. Suggested solutions should be comprehensive and justified in approach. Configurations of technologies should be written out to help guide the systems administrators with implementation. In some cases, you may find it necessary to implement additional cabling, which can be done by adding to the supplied topology. Any adjustments to the sites’ topology that you find necessary should be documented and supplied with your submission. Your document will be divided up by site and solutions per site. Each area is unique in requirements but collectively will demonstrate your understanding of network routing and switching technologies. Each scenario will provide you with suggested sections within TestOut (LabSim) to use as a guide in your analysis and recommendations. To learn how you will be assessed on this assignment, take a moment to review the rubric. The final deliverable should adhere to the following criteria: Use this template as a guide while creating your Cisco Network Proposal (Parts 13). Include at least two scholarly references in each of the three submissions. Thus, a total of six scholarly references will be included in total. Students may find scholarly sources by visiting UMUC’s library and online sources. Students will also include other credible sources as appropriate. Use IEEE citation style. We do not use APA or MLAstyle citations. Students should contact UMUC’s Effective Writing Center for assistance. Use proper terminology and expand acronyms in each paragraph they are used. For example, the first time in a paragraph an acronym is used it should be expanded (e.g., University of Maryland University College (UMUC). Thereafter, and as long as you are in the same paragraph, the acronym (e.g., UMUC) can be used. When starting a new paragraph, the rule begins anew. The use of figures and diagrams is encouraged. Students will properly cite the figures and diagrams according to the IEEE citation style.
Required Implementation: Implement a routing protocol to manage networks within the Boston site topology as well as default routes to exit non-Boston traffic. Summarization addresses should be stated per router in Boston’s topology. Consider redundancy upgrades as well and document per topology.
- Routing Protocol: Research the different routing protocol types (distance vector/link state/hybrid) and choose a routing protocol implement (OSPF, EIGRP, RIP). Justify your selection by defining its strengths and weaknesses. Define the proper addressing block to assign per point-to-point links and implement your solution per all three routers. Routing protocol should be set up in a way to advertise all IP subnets, WAN, and LAN interfaces on a router. Be sure to protect the advertisements of the routing tables as well.
- Summarization: Define the route summarization addresses for each Boston site router. These addresses will not be implemented on the routers, but they will be documented in your response. Each summarization address must be large enough to include all required subnets contained within the underlying site subnets.
- Default Route: Any traffic not matching internal networks will need to be routed outward. Implement default routes on the site routers to exit this traffic.
- Topology: Consider the potential challenges with the current Boston site topology (cabling and redundancy approach). If improvements are needed, update the topology and discuss and routing redundancy approaches you see fit.
- Please refer to the following configurations:
/* Style Definitions */
mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
font-family:”Times New Roman”,serif;
mso-bidi-font-family:”Times New Roman”;