The document outlines the subnetting and VLAN configurations required for various sites as per the Xacme educational topology, focusing on creating appropriate subnet sizes and addressing without needing to implement VLANs. It details the specific device counts and configurations for each site, including routing protocols, DHCP configurations, and security measures for switches. Additionally, it emphasizes the importance of proper documentation, managing network redundancies, and implementing routing solutions within designated topologies.

1. 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.
NetID
mask/CIDR values
broadcast
usable range
No additional device configurations required to complete
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).
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:
Switches Per Site:
Note:Device type will not impact your configuration commands and implementation of ALL

2. 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.Cisco 2800 Series Integrated
ServicesInterfaces Ports Available4 Fast Ethernet Interfaces
(Per Router)2 Serial Interfaces
(Per Router)fa0/0s0/0/0fa0/1s0/0/1fa1/0fa1/1 Acme Educational Topology Public Address
Range 165.128.63.0 /26 Private Network 10.0.0.0 /8 Boston Site Administrative VLA structional
VLAN Device List 4 Devices 34 Devices Network 10.10.0.0 Switches: Catalyst 6500 Series
Server VLAN Faculty VLAN Devices 5 Devices 96 Gigabit Ports fa010 Mod 220 Total Hosts
Module 2.gl1j1 gl n Stub Area Module 3 gi2u1-g gi012 Boston, MA Module 4 31-g 3/24 Site
Router 2 Router 2800 Series Integrated Services Sacramento. SWTch1 Sacramento SWRch2 Sac
3 024 ta0A0 Pot Contuurations uper Router 4 Fast Ethernet erfaces Sacramento Site 010
Network 10.50.0.0 2- fa011 fa 100 42 Total Hosts 65.128.63. Stub Area Boston, 2 Serial
Interfaces Route Boston, MA Site Router 3 DCE Sacramento, CA 0.255.25 48 30 0,255 .252 130
Internet Faculty VLAN Worchester Site 21 Devices Network 10.20.0.0 /1 gio fa010 DCE.
0.255.255. Administrative VLAN Worchester, MA fa024 130 44 Devices fa0/24 DCE Router
Faculty VLAN fa0M0 9 Devices Switch 2 s010/1 Springfield site gi0/2 gl012 Springfield, MA
Router gi02 Angeles, CA Instructional VLAN gl0196 Administrative VLAN Roure 20 Devices
30 gio/2 gioi1 65.128.63.2 Los A Swich 3 field. gioi1 gi0 gi012 Server VLAN ructional VLAN
21 Devices gi0/2 215 gi0/22 Server VLAN gi011 24 Devices Switch 3 Los Angeles site Faculty
VLAN Network 10.40.0.0 20 Devices SFTP/NTPS Instructional VLAN Administrative VLAN
Server VLAN 38 Devic Devices
Solution
protect the devices from bogus BPDUs.Note: When approaching the spanning tree challenge, do
not concern yourself with the multipleVLANs at this time. Focus simply on the default VLAN1,
which is the active VLAN that all portsbelong to in this topology at this time.Please refer to the
following configurations:o SpringfieldSw1o SpringfieldSw2o SpringfieldSw3o
SpringfieldSw4Worchester SiteRequired Implementation: Subnet addressing to accommodate
Worchester siteSubnetting: Properly subnet addressing blocks to accommodate the site's VLAN
sizes. You willnot need to implement VLANs here; rather, you will create the correct sizing to
properlyaccommodate the devices stated per the xACME educational topology. Carefully
consider thechallenges faced when structuring subnets too large and/or too small during your
design. Thestarting Worchester site addressing range is 10.20.0.0 /16 (per the xACME
educational topologydiagram). Formatting per subnet should follow the format below and should

3. be clearly stated andplaced within a table.NetIDmask/CIDR valuesbroadcastusable rangeNo
additional device configurations required to completeBoston Site Routing Protocol, Route
Summarization and TopologyImprovements (Focus on the Boston Site Only)Required
Implementation: Implement a routing protocol to manage networks within theBoston site
topology as well as default routes to exit non-Boston traffic. Summarizationaddresses 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/linkstate/hybrid) and choose a routing protocol implement (OSPF, EIGRP, RIP).
Justify yourselection by defining its strengths and weaknesses. Define the proper addressing
block toassign per point-to-point links and implement your solution per all three routers.
Routingprotocol should be set up in a way to advertise all IP subnets, WAN, and LAN
interfaceson 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 inyour response.
Each summarization address must be large enough to include all requiredsubnets contained
within the underlying site subnets.Default Route: Any traffic not matching internal networks will
need to be routedoutward. 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 anddiscuss and
routing redundancy approaches you see fit.Please refer to the following configurations:o
BostonSiteRouter1o BostonSiteRouter2o BostonSiteRouter3Sacramento Site VLAN, Routing on
a Stick (ROS) and DHCP Implementation(Focus on the Sacramento Site Only)Required
Implementation: VLANs, ROS, and DHCP implementationVLANs: Implement the VLAN
database on the Sacramento site switches. Explain theassignment of switchport modes and how
to implement each. Demonstrate how toimplement port security on the switchports to allow only
two MAC addresses per portand shutdowns for violations. Additionally, consider proper security
management of anyunused ports.o Provide the VLAN IDs, ports with matching switchport
modes, and sampleconfiguration of port security and port management steps.
ROS: The site will be treated as a routing on a stick (ROS) topology. Provide a
sampleconfiguration for Sacramento fa0/0 interface to support the multiple VLANs and
interVLANrouting.o To simplify configuration, please use the following addressing:faculty
VLAN: 10.50.0.0 /26administrative VLAN: 10.50.0.64 /26instructional VLAN: 10.50.0.128
/26server VLAN: 10.50.0.192 /26DHCP: The site will need a solution to manage the deployment
of IP addresses. Brieflyexplain the purpose of DHCP and provide implementation of the DHCP
configuration forthe VLANs. Be sure to include the pool name, exclude the last 10 addresses of
eachsubnet range and configure the gateway, subnet mask, and DNS address (Sacramentofa0/0

4. address).Please refer to the following configurations:o SacramentoSw1o SacramentoSw2o
SacramentoSw3o SacramentoRouterLos Angeles Site Management Technologies (Focus on the
Los Angeles SiteOnly)Required Implementation: Device configuration remote storage, remote
management ofswitches, 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 anddemonstrate how to implement the
solution.