Implement device hostnames

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 xAcme’s 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
–

Implement device hostnames

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 this template as a guide on how to format your project. Be sure to cite your external sources using the IEEE citation style. To learn how you will be assessed on this assignment, please take a moment to review the rubric.
Existing VLANs
–

Implement device hostnames

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).

Existing VLANs, per xACME:
Faculty VLAN
used by faculty on-site for all office locations (non-instructional communications)
total devices per site will vary
Administrative VLAN
used by staff on-site for business administrative communications
total devices per site will vary
Academic VLAN
used by faculty and students for classroom labs and instructional communications
total devices per site will vary
Server VLAN
used by IT staff for all technology/management communications
total devices per site will vary

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

(Per Router)
2 Serial Interfaces

(Per Router)
fa0/0     s0/0/0
fa0/1     s0/0/1
fa1/0
fa1/1

Switches Per Site:
Cisco Catalyst 6500 Series
Ports Available     96 Total Gigabit Ethernet

Implement device hostnames

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.
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 on all switches 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 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.

Please refer to the following configurations:
SpringfieldSw1
SpringfieldSw2
SpringfieldSw3
SpringfieldSw4

Worchester Site Subnetting Configurations (Focus on the Worchester Site Only)

Implement device hostnames

–

Required Implementation:Subnet addressing to accommodate Worchester site

Subnetting: Properly subnet addressing blocks to accommodate the sites VLAN sizes. You will notneed 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 format below and should be clearly stated and placed within a table.
NetID
mask/CIDR values
broadcast
usable range

No additional device configurations required to complete

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.

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 our 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.

Implement device hostnames

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:
BostonSiteRouter1
BostonSiteRouter2
BostonSiteRouter3

Sacramento Site VLAN, Routing on a Stick (ROS) and DHCP Implementation (Focus on the Sacramento Site Only)
–

Required Implementation: VLANs, ROS, and DHCP implementation

VLANs: Implement the VLAN database on the Sacramento site switches. Explain the assignment of switchport modes and how to implement each. Demonstrate how to implement port security on the switchports to allow only two MAC addresses per port and shutdowns for violations. Additionally, consider proper security management of any unused ports.
Provide the VLAN IDs, ports with matching switchport modes, and sample configuration of port security and port management steps.
ROS: The site will be treated as a routing on a stick (ROS) topology. Provide a sample configuration for Sacramento fa0/0 interface to support the multiple VLAN’s and inter-vlan routing.
To simplify configuration, please use the following addressing:
faculty VLAN: 10.50.0.0 /26
administrative VLAN: 10.50.0.64 /26
instructional VLAN: 10.50.0.128 /26
server VLAN: 10.50.0.192 /26
DHCP: The site will need a solution to manage the deployment of IP addresses. Briefly explain the purpose of DHCP and provide implementation of the DHCP configuration for the VLANs. Be sure to include the pool name, exclude the last 10 addresses of each subnet range and configure the gateway, subnet mask and DNS Address (Sacramento fa0/0 address).

Please refer to the following configurations:
SacramentoSw1
SacramentoSw2
SacramentoSw3
SacramentoRouter

Los Angeles Site Management Technologies (Focus on the Los Angeles Site Only)

Implement device hostnames

–

Required Implementation: Device configuration remote storage, remote management of switches, ACL implementation, and an NTP solution.

Remote IOS Storage: The site will require remote storage of the devices configurations. Server details are provided per your topology. You will determine the protocol to use and demonstrate how to implement the solution.
Remote Management of Switches: All devices will be configured to allow for remote management. You will be required to implement this solution on the switches found on the site.
ACL Implementation: In order to restrict and protect access to the devices, the only VLAN allowed to communicate remotely with the devices should belong to the server VLAN. Determine the type of ACL to implement and the placement of the list, and implement the solution on the site router.
Network Time Protocol: Implement an NTP solution on the devices found within this topology to ensure clock synchronization is accomplished. The purpose would be for accurate logging records and authentication protocols. Server details are provided per your topology.

Please refer to the following configurations:
LosAngelesSw1
LosAngelesSw2
LosAngelesSw3
LosAngelesRouter

xACME WAN – WAN Implementation and Secure Communications (Focus on All Site Entry Point Routers)
–

Implement device hostnames

Required Implementation: WAN Implementation, device authentication, and topology suggestions.

WAN Implementation: Current WAN links are serial based and connected over leased lines that are using the Cisco default protocol for layer 2 connectivity. Authentication is not present at this time, but the added security would be preferred. Research the available WAN protocols and suggest a solution to provide authentication between devices. Implement basic routing protocol authentication. Provide a sample implementation over serial links for your systems administrator to follow. Included in this task are device configurations for the current implementation.
Topology: Currently, the Los Angeles and Boston sites are connected across leased lines and each remains as the entry point to its respective regional locations. There is growing concern over the amount of traffic both devices are handling. Please review the xAMCE educational topology and make recommendations to provide some redundancy among sites, as well as to alleviate some of the bandwidth requirements placed on both devices. This may require additional lines to be leased. With your suggested improvements, please update the topology as you see fit.

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.

Please refer to the following configurations:
BostonSiteRouter1
WorchesterRouter
SpringfieldRouter
SacramentoRouter
LosAngelesRouter

Implement device hostnames

Order 100% Plagiarism paper Now

Implement device hostnames

Implement device hostnames

Implement device hostnames

Implement device hostnames

Implement device hostnames

Implement device hostnames

Implement device hostnames

Implement device hostnames

Implement device hostnames

Implement device hostnames

Implement device hostnames

Implement device hostnames

Implement device hostnames

Implement device hostnames

Implement device hostnames

Implement device hostnames

Implement device hostnames

Implement device hostnames

Implement device hostnames

Implement device hostnames

Implement device hostnames

Implement device hostnames

Implement device hostnames

Implement device hostnames

Implement device hostnames

Implement device hostnames

Implement device hostnames

Implement device hostnames

Implement device hostnames

Implement device hostnames

Implement device hostnames

Implement device hostnames

Implement device hostnames

Implement device hostnames

Implement device hostnames

Implement device hostnames

Implement device hostnames

Implement device hostnames

Implement device hostnames

Implement device hostnames

Implement device hostnames

Implement device hostnames

Implement device hostnames

Implement device hostnames

Implement device hostnames

Implement device hostnames

Implement device hostnames

Implement device hostnames

Implement device hostnames

Implement device hostnames

Implement device hostnames

Implement device hostnames

Implement device hostnames

Implement device hostnames

Implement device hostnames

Implement device hostnames

Implement device hostnames

Implement device hostnames

Implement device hostnames

Implement device hostnames

Implement device hostnames

Implement device hostnames

Implement device hostnames

Implement device hostnames

Implement device hostnames

Implement device hostnames

Implement device hostnames

Implement device hostnames

Implement device hostnames

Implement device hostnames

Implement device hostnames

Implement device hostnames