routing protocol to manage networks
routing protocol to manage networks
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 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
