Download includes all parts answered (1,2&3).
Your proposal will be submitted in three major parts:
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:
Remote locations vary in terms of size and requirements. Some implementations will require current site router/switch-running configurations, which will be provided. All sites will use the following four VLANs, but you will need to configure only what is asked per site (some assumptions will be made).
The types of devices per site will be the same; however, the number of deployed devices may vary (all documented in the xAcme educational topology).
Routers Per Site:
|Cisco 2800 Series Integrated Services|
|Interfaces Ports Available||4 Fast Ethernet Interfaces
|2 Serial Interfaces
Switches Per Site:
|Cisco Catalyst 6500 Series|
|Ports Available||96 Total Gigabit Ethernet
Ports Per Switch
|Module 1 = gi0/1 – gi0/24|
|Module 2 = gi1/1 – gi1/24|
|Module 3 = gi2/1 – gi2/24|
|Module 4 = gi3/1 – gi3/24|
Note: Device type will not impact your configuration commands and implementation of ALL required technologies will use Cisco IOS commands/concepts learned in our TestOut lecture(s). Standard switchports will be configured and used as trunk OR access ports, and DCE ends should be noted when configuring serial ports per router.
Click here to download the configuration file for all of the devices. Note: one of the files in the zip file is a PacketTracer file. You can open it using the Packet Tracer program that you can download from here. The use of Packet Tracer is optional.
Springfield Site Device and STP Configurations (Focus on the Springfield Site Only)
Required Implementation: Device hostnames, banners, secured passwords and spanning tree protocol.
Note: When approaching the spanning tree challenge, do not concern yourself with the multiple VLANs at this time. Focus simply on the default VLAN1, which is the active VLAN that all ports belong to in this topology at this time.
Worchester Site Device and STP Configurations (Focus on the Worchester Site Only)
Required Implementation: Subnet addressing to accommodate Worchester site
Subnetting: Properly subnet addressing blocks to accommodate the site’s VLAN sizes. You will not need to implement VLANs here; rather, you will create the correct sizing to properly accommodate the devices stated per the xACME educational topology. Carefully consider the challenges faced when structuring subnets too large and/or too small during your design. The starting Worchester site addressing range is 10.20.0.0 /16 (per the xACME educational topology diagram). Formatting per subnet should follow the format below and should be clearly stated and placed within a table.
Boston Site Routing Protocol, Route Summarization and Topology Improvements (Focus on the Boston Site Only)
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.
Sacramento Site VLAN, Routing on a Stick (ROS) and DHCP Implementation (Focus on the Sacramento Site Only)
Required Implementation: VLANs, ROS, and DHCP implementation
Los Angeles Site Management Technologies (Focus on the Los Angeles Site Only)
Required Implementation: Device configuration remote storage, remote management of switches, ACL implementation, and an NTP solution.
xACME WAN – WAN Implementation and Secure Communications (Focus on All Site Entry Point Routers)
Required Implementation: WAN Implementation, device authentication, and topology suggestions.
Note: Additional addressing is available if needed. Simply create the additional ranges from the provided available xACME public address range, 22.214.171.124 /26.