Order 1459501: Cisco Network Proposal
2/4/2019 Cisco Network Proposal (Parts 1-3) - CMIT 350 6380 Interconnecting Cisco Devices (2192)
https://learn.umuc.edu/d2l/le/content/347618/viewContent/14448535/View 1/3
Remote locations vary in terms of size and requirements. Some implementations will require current site router/switchrunning 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 onsite for all office locations (noninstructional
communications)
total devices per site will vary
Administrative VLAN
used by staff onsite 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
Existing VLANs
2/4/2019 Cisco Network Proposal (Parts 1-3) - CMIT 350 6380 Interconnecting Cisco Devices (2192)
https://learn.umuc.edu/d2l/le/content/347618/viewContent/14448535/View 2/3
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.
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.
NetID
mask/CIDR values
broadcast
usable range
No additional device configurations required to complete
Springfield Site Device and STP Configurations (Focus on the Springfield Site Only)
+
Worchester Site Device and STP Configurations (Focus on the Worchester Site Only)
Boston Site Routing Protocol, Route Summarization and Topology Improvements (Focus on the Boston Site Only)
2/4/2019 Cisco Network Proposal (Parts 1-3) - CMIT 350 6380 Interconnecting Cisco Devices (2192)
https://learn.umuc.edu/d2l/le/content/347618/viewContent/14448535/View 3/3
Required Implementation: Implement a routing protocol to manage networks within the Boston site topology as well as default routes to exit nonBoston 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 pointtopoint 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 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 in
your response. Each summarization address must be large enough to include all required
subnets contained within the underlying site subnets.
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