Sacramento-Site-VLAN-Routing-on-a-Stick-ROS-and-DHCP-Implementation-Focus-on-the-Sacramento-Site

Source should be IEEE

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 VLANs 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) 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: o LosAngelesSw1 o LosAngelesSw2 o LosAngelesSw3 o LosAngelesRouter

xACME WAN – WAN Implementation and Secure Communications (Focus on All Site Entry Point Routers) 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. 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, 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: o BostonSiteRouter1 o WorchesterRouter o SpringfieldRouter o SacramentoRouter o LosAngelesRouter