Order 1459501: Cisco Network Proposal
CMIT 350 WAN and SOHO Skills Implementation
Document Index/Contents Site Worchester Subnetting Implementation 3 Boston Site Routing Protocol, Route Summarization and Topology Improvements (Focus on the Boston Site Only) 4 Bibliography 9
I. Site Worchester Subnetting Implementation:
Site Details and Challenges (Summary)
Subnetting: Properly subnet addressing blocks to accommodate the sites 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 format below and should be clearly stated and placed within a table.
· NetID
· mask/CIDR values
· broadcast
· usable range
Site Solutions and Technologies:
The Worchester sites starting address allocation is 10.20.0.0 /16 according to the topology diagram provided. The implementation of an addressing structure which creates balance between not being too large and causing wasteful distribution or too small resulting in insufficient coverage for the current configuration and limiting future growth.
Subnetting Solution
|
NetID |
Mask/CIDR value |
Broadcast |
First host address |
Last host address |
Description |
Hosts |
Hosts per Subnet |
|
10.20.0.0
|
255.255.255.0 /24
|
10.20.0.255
|
10.20.0.1 |
10.20.0.254
|
Instructional VLAN |
215 |
254 |
|
10.20.1.0
|
255.255.255.192 /26 |
10.20.1.63 |
10.20.1.1 |
10.20.1.62 |
Administrative VLAN |
30 |
62 |
|
10.20.2.0 |
255.255.255.192/26 |
10.20.2.63 |
10.20.2.1 |
10.20.2.62 |
Server VLAN |
24 |
62 |
|
10.20.3.0
|
255.255.255.224/27
|
10.20.3.31 |
10.20.3.1 |
10.20.3.30 |
Faculty VLAN |
19 |
30 |
II. Boston Site Routing Protocol, Route Summarization and Topology Improvements (Focus on the Boston Site Only)
Site Details and Challenges (Summary)
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.
Site Solutions and Technologies
Routing Protocol:
A comparison of different routing protocols is presented in the table below:
|
Protocol Feature |
RIP v1/v2 |
IGRP |
EIGRP |
OSPF |
Static |
BGP |
|
Supports classful addressing |
yes |
yes |
yes |
yes |
yes |
yes |
|
Interior Gateway Protocol |
yes |
yes |
yes |
yes |
No |
No |
|
Exterior Gateway Protocol |
No |
No |
No |
No |
Yes |
Yes |
|
Supports classless addressing |
Yes (V2) |
No |
Yes |
Yes |
Yes |
Yes |
|
Supports load sharing |
No |
Yes |
Yes |
Yes |
No |
Yes |
|
Supports authentication |
yes (v2) |
No |
Yes |
Yes |
No |
yes |
|
Easy implementation |
Yes |
Yes |
Yes |
No |
No |
No |
|
Routing algorithm |
DV |
DV |
Dual |
LS |
None |
DV |
|
Supports weighted metrics |
No |
Yes |
Yes |
Yes |
No |
No |
|
Fast convergence |
No |
Yes |
Yes |
Yes |
Yes |
Yes |
|
Uses broadcasts for route updates |
yes (v1) |
Yes |
No |
No |
No |
No |
|
Uses multicast for routing updates |
yes (v2) |
No |
Yes |
Yes |
No |
No |
|
Supports large network diameters |
No |
No |
Yes |
Yes |
Yes |
Yes |
Administrative distance is the feature that routers use in order to select the best path when there are two or more different routes to the same destination from two different routing protocols. Administrative distance defines the reliability of a routing protocol [1]. Each routing protocol is prioritized in order of most to least reliable (believable) with the help of an administrative distance value. These protocols and distance values are displayed in the table below:
|
Protocol |
Distance |
|
Connected interface |
0 |
|
EIGRP summary route |
5 |
|
BGP (external) |
20 |
|
EIGRP (internal) |
90 |
|
IGRP |
100 |
|
OSPF |
110 |
|
RIP |
120 |
|
EIGRP (external) |
170 |
|
BGP (internal) |
200 |
|
Unknown |
255 |
The lower the administrative distance value, the more trusted the route. So, we can see in situations where multiple routing protocols are being used for route advertisement, the router will prefer information provided from certain protocols over others.
Enhanced Interior Gateway Routing Protocol (EIGRP) is a cisco proprietary protocol and considered to be a hybrid of link-state and distance vectors and is frequently referred to as an advanced distance vector protocol [6]. EIGRP performs in ways that OSPF and RIP do by combining the two algorithms allowing it to acquire and utilize the best route for each subnet. EIGRP is most often used in large networks. EIGRP metric takes into consideration bandwidth, reliability, delay, MTU and load. EIGRP will be the best routing protocol option for the xACME topology.
EIGRP characteristics
• Advanced Distance Vector
• Routes IP, IPX, Decnet, Appletalk
• Routing Advertisements: Partial When Route Changes Occur
• Metrics: Bandwidth, Delay, Reliability, Load, MTU Size
• Hop Count: 255
• Variable Length Subnet Masks
• Summarization on Network Class Address or Subnet Boundary
• Load Balancing Across 6 Equal or Unequal Cost Paths (IOS 11.0)
• Hello Timer: 1 second on Ethernet / 60 seconds on Non-Broadcast
• Holddown Timer: 3 seconds on Ethernet / 180 seconds on Non-Broadcast
• Metric Calculation = destination path minimum BW * delay (msec) * 25
• Bidirectional Forwarding Detection (BFD) Support
• Split Horizon
• LSA Multicast Address: 224.0.0.10 [4]
Router Configuration setup
R1#config t
R1(config)#ip route 10.10.0.0 255.0.0.0 10.10.255.254
R1(config)#ip route 10.10.10.0 255.0.0.0 10.10.255.250
R1(config)#router eigrp 100
R1(config-router)#network 10.10.0.0 ?? Summarize only what needs to be advertise.
R1(config-router)#CTRL-Z
R1#copy run start
R2#config t
R2(config)#ip route 0.0.0.0 0.0.0.0 10.10.255.253
R2(config)#router eigrp 100
R2(config-router)#network 10.10.0.0?? Summarize only what needs to be advertise.
R2(config-router)#
R2(config-router)#CTRL-Z
R2#copy run start
R3#config t
R3(config)#ip route 0.0.0.0 0.0.0.0 10.10.255.249
R3(config)#router eigrp 100
R3(config-router)#network 10.10.0.0?? Summarize only what needs to be advertise.
R3(config-router)#
R3(config-router)#CTRL-Z
R3#copy run start
R3#show ip eigrp neighbors
165.182.63.1 Se0/0/0
10.255.255.248 /30 Se0/0/1
Route Summarization
In order have to create an efficient network a route summarization for each Boston, MA Site routers is depicted below. A Cisco Press article showing examples of how to create route summarizations was used when creating this route summarization to ensure that correct conversions and calculations were performed. [4]
Boston, MA Site Router 1
00001010.00001010.11111111.11111101 - 10.10.255.253
00001010.00001010.11111111.11111001 - 10.10.255.249
00001010.11111111.11111111.11111001 - 10.255.255.249
Route Summarization: 10.0.0.0/8
Subnet: 255.0.0.0 Inverted mask: 0.255.255.255
Boston, MA Site Router 2
00001010.00001010.11111111.11111110 - 10.10.255.254
00001010.00001010.00000000.00000001 - 10.10.0.1
00001010.00001010.00000010.00000001 - 10.10.2.1
00001010.00001010.00000100.00000001 - 10.10.4.1
00001010.00001010.00000110.00000001 - 10.10.6.1
Route Summarization: 10.10.0.0/16
Subnet: 255.255.0.0 Inverted mask: 0.0.255.255
Boston, MA Site Router 3
00001010.00001010.11111111.11111010 - 10.10.255.250
00001010.00001010.00001010.00000001 - 10.10.10.1
00001010.00001010.00001100.00000001 - 10.10.12.1
00001010.00001010.00001110.00000001 - 10.10.14.1
00001010.00001010.00010000.00000001 - 10.10.16.1
Route Summarization: 10.10.0.0/16
Subnet: 255.255.0.0 Inverted mask: 0.0.255.255
Topology Issues
The current established Boston site topology depicts routers only. This current network topology will not be a adequate for the specified number of required hosts. I propose that a total of 6 Cisco Catalyst 6500 series switches labeled as Boston, MA Site Switch Main and Boston, MA Site Switch 1 thru 5 be added to the topology depiction. I also recommend that the Boston, MA Site Switch Main be located between the existing Routers 1, 2 and 3 and configured to connect to Boston, MA Site Routers 1, 2 and 3. Three of the purposed Cisco Catalyst 6500 series switches labeled Boston, MA Site Switch 1, 2 and 3 will be connected to the existing Boston, MA Site Router 2 to accommodate the 220 total hosts in Stub area. The last two purposed Cisco Catalyst 6500 series switches labeled Boston, MA Site Switch 4 and Boston, MA Site Switch 5 will be located off of the existing Boston, MA Site Router 3 to accommodate the 142 total hosts in Stub area. After all of the new Cisco Catalyst 6500 series switches have been installed they will require being configured with IP addresses and VLANs for the 362 total hosts in the Boston Site. This should be done in a manner the increases organizational flow and reduce redundancies [5]
III. Bibliography
[1] “What Is Administrative Distance?", Cisco, 2017. [Online]. Available: http://www.cisco.com/c/en/us/support/docs/ip/border-gateway-protocol-bgp/15986-admin-distance.html. [Accessed: 24- Mar- 2017].
[2] "TCP/IP Tutorial and Technical Overview", Danzig.jct.ac.il, 2017. [Online]. Available: http://www.danzig.jct.ac.il/tcp-ip-lab/ibm-tutorial/3376c22.html. [Accessed: 24- Mar- 2017].
[3] C. Guide, "Subnetting Tutorial - Subnetting Explained with Examples", Computernetworkingnotes.com, 2017. [Online]. Available: http://computernetworkingnotes.com/subnetting-supernetting-and-vlsm/subnetting.html. [Accessed: 22- Mar- 2017].
[4] S. Hummel, "Routing Protocol Selection Guide - IGRP, EIGRP, OSPF, IS-IS, BGP," Cisco, 1
November 2015. [Online]. Available: https://supportforums.cisco.com/document/127851
/routing-protocol-selection-guide-igrp-eigrp-ospf-bgp. [Accessed 6-April-2017].
[5] A. Bruno and J. Kim, “Cisco Network Topologies and LAN Design,” > Foundation Topics, 16-Nov-2001. [Online]. Available: http://www.ciscopress.com/articles/article.asp?p=
24101. [Accessed 6-April-2017].
[6] Cisco, "Enhanced Interior Gateway Routing Protocol," Cisco, 5 January 2015. [Online]. Available: http://www.cisco.com/c/en/us/support/docs/ip/enhanced-interior-gateway-
routing-protocol-eigrp/16406-eigrp-toc.html. [Accessed 6-April-2017].
2