Worchester Subnetting and Boston Site Routing and Topology Analysis

This report provides a comprehensive analysis of the network design for Worchester and Boston sites. The Worchester section focuses on subnetting configurations, identifying issues such as the lack of subnets for network devices and server management, and proposes a new subnetting scheme. The Boston site analysis delves into the routing protocol, specifically OSPF, and suggests the implementation of route summarization to minimize routing table size. Furthermore, the report addresses the existing network's inefficient use of two internet links, proposing the use of BGP to enable load balancing and ensure both links are actively utilized, thereby preventing packet drops and improving overall network performance. The report concludes with a bibliography referencing relevant Cisco certification guides.

Worchester Subnetting Configurations and Boston Site Protocol, Route Summarization,
and Topology Improvements
Site Details and Challenges
Subnetting Configurations:
Worchester has design different subnets for different department or area. But network doesn’t have any
subnet for network devices. There is no subnet for server management too. Current network uses
10.2.0.0/16 network for this site. Subnets as mention below:
VLAN Subnet Subnet-mask First valid IP Last valid IP Assign to
VLAN 1 10.2.1.0 255.255.255.0 10.2.1.1 10.2.1.1 Network Management
VLAN 10 10.2.10.0 255.255.255.0 10.2.10.1 10.2.10.1 Staff
VLAN 11 10.2.11.0 255.255.255.0 10.2.11.1 10.2.11.1 Admin
VLAN 12 10.2.12.0 255.255.255.0 10.2.12.1 10.2.12.1 Server
Boston Site Protocol, Route Summarization, and Topology Improvements:
Routing Protocol:
Routing protocol is design for learn route dynamically. OSPF is link-state routing protocol which use
Dijkstra’s algorithm to find best path to destination and other paths as redundant paths. OSPF update its
data base according to paths. OSPF works on LSA principal.
OSPF has different area types. We can summarize network address at ABR or ASBR. Those routers are
boarder area routers.
We have three different areas. Each area has four subnets. Currently, there full advertisement into OSPF
domain. Now, I’m going to use summarize network address to minimize routing table.
Summarization:
Summarization is reverse of subnetting. Router will only advertise its summary address rather than full
route (all subnets).
a) BR1 AREA 1
10.5.0.1, 10.5.1.1, 10.5.2.1, 10.5.3.1  10.5.0.0/22
b) BR2 AREA 2:
10.5.8.1, 10.5.9.1, 10.5.10.1, 10.5.11.1  10.5.8.0/22
c) BR3 AREA 3:
10.5.16.1, 10.5.17.1, 10.5.18.1, 10.5.19.1  10.5.16.0/21

Network Improvement:
Site has two internet link from two different ISPs. Issue is only one link is used as an active and
standby scenario. Active/primary link utilization is high, sometime it’s reach 100%. So packet
drops are there in active WAN link.
Currently network design has two WAN links which are terminated at backbone router. Site is
using static route for the WAN link. Site is paying for both links but they are not using both links
at a time. I’m going to use BGP protocol instead of static route to use both link at a time.
Using BGP routing protocol we can use both link as we want. We can do load-balance and much
more using BGP protocol, but our main aim to use both links so there is no packet drop in
current network.
Sample Configuration
Router#configuration terminal
Router(config)#router bgp 64513
Router(config-router)#neighbor 10.10.10.10 remote-as 100
Router(config-router)#neighbor 20.20.20.20 remote-as 200
Router(config-router)#network 40.10.9.0
Bibliography
Cisco Official Certification Guide - CCNP Route by Wendell Odom