WAN Implementation with SOHO Configuration 1-3 PARTS

You have been recently hired as a network administrator for the xAcme Technology Trade School. The company is realizing that the local systems administrators need help implementing certain technologies at each of the remote locations as well as final WAN configurations. Out of the network administrators on staff you have been asked to move forward the project. With your background and skills you will design implement and assist in configurations to support xAcmes topology. Technologies to implement will differ from site to site as administrators have begun topology implementations. You will be provided the overall topology as well as certain device configurations in order to determine the best course of action per site/challenge. In addition to helping them configure their network they require that all new network administrators obtain their CCNA Certification within 60 days of being hired. You are excited about starting this project but realize creating a schedule to help balance your work and home life will be key to success.
To get started follow the steps below:
IEEE Format and also the assignment will be submitted on TurnItin.
Overview
–
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.
You can use thistemplateas a guide on how to format your project. Be sure to cite your external sources using theIEEE citation style. To learn how you will be assessed on this assignment please take a moment to review therubric.
Existing VLANs
–
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 Available4 Fast Ethernet Interfaces(Per Router)2 Serial Interfaces(Per Router)
fa0/0s0/0/0
fa0/1s0/0/1
fa1/0
fa1/1
Switches Per Site:
Cisco Catalyst 6500 Series
Ports Available96 Total Gigabit EthernetPorts 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.
Springfield Site Device and STP Configurations (Focus on the Springfield Site Only)
–
Required Implementation:Device hostnames banners secured passwords and spanning tree protocol.
Device Configurations:Implement device hostnames to match the xACME educational topology labels. Provide a template and sample configuration for the MOTD banner and login banner (wording and implementation) for one of the switches. Keep this generic as it will be implemented onallswitches in the xACME educational topology. Lastly include the configuration steps for implementing device passwords on both console port (out-of-band communications) and VTY (Telnet/in-band communications). All passwords should be encrypted.
Spanning Tree Protocol (STP):Briefly explain the advantages and purpose of the STP. Administrators are having a difficult time placing switch 1 as the root. Provide a sample configuration for implementing SPT on the switches. Choose the mode you feel would be best suited for the environment and justify why. Switch 1 will need to be the root switch in the Springfield topology. Consider any security measures that can be implemented to protect the devices from bogus BPDUs.
Note:When approaching the spanning tree challengedo notconcern 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 Subnetting Configurations (Focus on the Worchester Site Only)
–
Required Implementation:Subnet addressing to accommodate Worchester site
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 Bostons 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 165.128.63.0 /26.