Professional Documents
Culture Documents
1
Network Routing and Fundamentals Case Study 2
CONTENTS
3. Summary Page 8
4. Abbreviations Page 9
5. References Page 10
6. Appendices Page 11
2
Network Routing and Fundamentals Case Study 2
1.1 Introduction
A unit has several people responsible for maintaining various sections of the
internetwork infrastructure. Many technicians have done an excellent job with the
small portion for which they are responsible.
One of the other network associates who was responsible for a larger portion of the
infrastructure was suddenly posted. This left redesign and implementation on this
portion of the internetwork unfinished. A technician is given the task to complete the
design and implementation of the unfinished network.
The few documents that existed were poorly written. So during the weekend the
technician reconstructs the diagram from an existing diagram that was found. It
represents the new internetwork design. It shows the planned routers, hubs
/switches, circuits, and the servers/ workstation at each site. The server at the center
site is a file server accessed only by workstations on this internetwork. The
workstation at the center site is used to manage all routers on the internetwork.
After returning to work Monday morning, the technician presents the new diagram,
shown at Figure 1 to their network infrastructure team leader that assigned the
project. After discussion, it is determined that the new documentation must be
developed for the project.
3
Network Routing and Fundamentals Case Study 2
1.2 Requirements
1.2.1 This Project has the following requirements:
• Set up the physical layout of the network using the provided diagram
and accompanying narrative.
2.1.1 The original network topology diagram has been provided and is
shown at Figure 1 below. The topology has been checked and is correct, so
this to form the basis of the new network design.
4
Network Routing and Fundamentals Case Study 2
3 4 5 6
Center
Eva
Boaz
Server
2.1.2 The information gleaned from Figure 1 shows that there are five distinct
networks within the topology. There are three Local Area Networks (LANs)
and two smaller networks which provide serial link connectivity between the
LANs. The following information will provide will be used throughout this
document and will be used for the network design process.
5
Network Routing and Fundamentals Case Study 2
2.2.1 As stated in paragraph 2.1.2, the provided network address for this
project is 172.17.0.0/16. This address space will provide 65534 Internet
Protocol (IP) addresses which far exceeds the requirements for this network.
Using Variable Length Subnet Masking (VLSM), it is recommended that the
address space be reduced and is that it is sub-netted as shown in Tables 1
through to 5 at Appendix 1, page 11 and as summarised here:
2.2.2 It is proposed that the serial link subnets will become /30 networks
providing 2 usable host addresses; each serial link requires only 2 host
addresses, one for each end. The three LANs will become /24 networks,
allowing a maximum of 254 host’s each. This will allow for significant future
expansion to each of the LAN networks and the distinct subnets will enable
ease of configuration. To provide a logical addressing scheme which is
common across the subnets, each LAN will use the first usable address for
the router Fast Ethernet interface and the second address is used for the
Switch VLAN. The remaining addresses are used by the workstations and
server, starting with the last usable address and working backwards.
Configuration tables for each network can be found at Appendix 2, Page 13.
2.2.3 The network design has been constructed and tested in the Cisco
propriety simulation software called Packet Tracer. A network topology
printout from Packet Tracer can be found at Appendix 3, page 14, and Show
commands for each router can be found at Appendix 5a – g on pages 16 –
39.
6
Network Routing and Fundamentals Case Study 2
2.3.1 The routing protocol recommended for this project is Open Shortest
Path First (OSPF). OSPF is a ‘Link-state protocol that was developed as a
replacement for the distance vector routing protocol Routing Information
Protocol (RIP)’ Graziani and Johnson (2008: 500). Link-state protocols do not
exchange routes and metrics, they exchange only the state of the links they
7
Network Routing and Fundamentals Case Study 2
know about, and the cost associated with those links. This saves
considerably on bandwidth.
There are disadvantages to using link state protocols, such as OSPF. They
are resource intensive and require more processor capacity and memory.
‘For very large internetworks, the database of link state advertisements and
the calculation of routing table entries can be memory and processor
intensive.’ . www.microsoft.com (2010). The size of the current network
topology is not considered intensive for the routers to handle.
3.0 SUMMARY
8
Network Routing and Fundamentals Case Study 2
3.1 Summary
3.1.1 The solution provided covers all the requirements requested by the
project. The proposed network is based on the existing topology diagram and
the solution will be easily managed and can be scaled for future growth. The
network addressing scheme has been derived from sub-netting the allocated
address space into manageable subnets with logical allocation of IP
addresses whilst leaving significant room for future expansion.
The two main routing protocols considered were EIGRP and OSPF. Although
OSPF is slightly more complex to configure and understand than EIGRP, it is
the recommended protocol due to EIGRP being Cisco proprietary.
4.0 ABBREVIATIONS
4.1 Abbreviations
9
Network Routing and Fundamentals Case Study 2
References
Graziani and Johnson (2008). Routing Protocols and Concepts. 2nd ed. USA: Cisco
Press. 392.
Graziani and Johnson (2008). Routing Protocols and Concepts. 2nd ed. USA: Cisco
Press. 500.
10
Network Routing and Fundamentals Case Study 2
Appendix 1
Internet Protocol Range
Table 1 – Center Subnet
11
Network Routing and Fundamentals Case Study 2
12
Network Routing and Fundamentals Case Study 2
Appendix 2
Network Configuration Tables
Center Configuration
13
Network Routing and Fundamentals Case Study 2
FA 0/0
Center Switch 172.17.1.2 255.255.255.0 172.17.1.1
VLAN 1
Server 172.17.1.253 255.255.255.0 172.17.1.1
Boaz Configuration
Eva Configuration
14
Network Routing and Fundamentals Case Study 2
Appendix 4
Host Names and Passwords
Hostnames
15
Network Routing and Fundamentals Case Study 2
Equipment Hostname
Boaz Router Boaz
Server Server
PC 2 PC2
PC 3 PC3
PC 4 PC4
PC 5 PC5
PC 6 PC6
Passwords
Type Password
Console class
VTY 0 – 4 class
Secret cisco
Appendix 5a
Center Show CDP Neighbors
Center#sh cdp neigh
16
Network Routing and Fundamentals Case Study 2
Appendix 5b
17
Network Routing and Fundamentals Case Study 2
18
Network Routing and Fundamentals Case Study 2
19
Network Routing and Fundamentals Case Study 2
Appendix 5c
20
Network Routing and Fundamentals Case Study 2
21
Network Routing and Fundamentals Case Study 2
Boaz#
Eva IP Protocol
Eva#sh ip protocol
Routing Protocol is "ospf 1"
22
Network Routing and Fundamentals Case Study 2
Eva#
Appendix5d
23
Network Routing and Fundamentals Case Study 2
24
Network Routing and Fundamentals Case Study 2
25
Network Routing and Fundamentals Case Study 2
26
Network Routing and Fundamentals Case Study 2
27
Network Routing and Fundamentals Case Study 2
28
Network Routing and Fundamentals Case Study 2
29
Network Routing and Fundamentals Case Study 2
30
Network Routing and Fundamentals Case Study 2
31
Network Routing and Fundamentals Case Study 2
32
Network Routing and Fundamentals Case Study 2
Appendix5e
33
Network Routing and Fundamentals Case Study 2
34
Network Routing and Fundamentals Case Study 2
Boaz#
Eva#
Appendix 5f
36
Network Routing and Fundamentals Case Study 2
37
Network Routing and Fundamentals Case Study 2
38
Network Routing and Fundamentals Case Study 2
Appendix 5g
39
Network Routing and Fundamentals Case Study 2
version 12.2
no service timestamps log datetime msec
no service timestamps debug datetime msec
no service password-encryption
!
hostname Center
!
enable secret 5 $1$mERr$hx5rVt7rPNoS4wqbXKX7m0
!
ip name-server 0.0.0.0
!
interface FastEthernet0/0
description Link to Center Switch
ip address 172.17.1.1 255.255.255.0
duplex auto
speed auto
!
interface FastEthernet1/0
no ip address
duplex auto
speed auto
shutdown
!
interface Serial2/0
description Link to Eva Via Serial Cable
ip address 172.17.3.1 255.255.255.252
clock rate 64000
!
interface Serial3/0
40
Network Routing and Fundamentals Case Study 2
41
Network Routing and Fundamentals Case Study 2
password class
login
!
end
Center#
42
Network Routing and Fundamentals Case Study 2
43
Network Routing and Fundamentals Case Study 2
!
interface FastEthernet4/0
no ip address
shutdown
!
interface FastEthernet5/0
no ip address
shutdown
!
router ospf 1
log-adjacency-changes
passive-interface FastEthernet0/0
network 172.17.3.4 0.0.0.3 area 0
network 172.17.0.0 0.0.0.255 area 0
!
ip classless
!
banner motd ^C No Unauthorised Access ^C
!
line con 0
exec-timeout 0 0
password class
logging synchronous
login
line vty 0 4
password class
login
!
end
44
Network Routing and Fundamentals Case Study 2
Boaz#
45
Network Routing and Fundamentals Case Study 2
46
Network Routing and Fundamentals Case Study 2
!
interface FastEthernet4/0
no ip address
shutdown
!
interface FastEthernet5/0
no ip address
shutdown
!
router ospf 1
log-adjacency-changes
passive-interface FastEthernet0/0
network 172.17.2.0 0.0.0.255 area 0
network 172.17.0.0 0.0.3.255 area 0
!
ip classless
!
banner motd ^C No Unauthorised Access ^C
!
line con 0
exec-timeout 0 0
password class
logging synchronous
login
line vty 0 4
password class
login
!
end
47
Network Routing and Fundamentals Case Study 2
Eva#
48