You are on page 1of 44

Introduction to Computer Networking

Name: Sylvanus Jenkins

Student Id: 000449066

Network Design proposal

Contents

Introduction 2

IP Addressing 3

IP Configure for all devises 5

Passwords and security Management 7

Massage of the day 9

Host Names 8

Consol Passwords 11

VTY Password 14

cdp neighbors for each Router 15

Show ip Route 16

Show ip interface 18

Show version 19

Show ip interface brief 21

Pings for all devises 22

Access Control Lists 25

Conclusion 33

Sylvanus Jenkins Student ID: 000449066


Page 1
Introduction

This basic network design has been created to the University of Greenwich and it will
explain all the implements that the whole network contains and how will that help to
the users in all ends.
The basic network design included three Routers and it has been separated in to three
places as follows.
1. Greenwich
2. Avery Hill
3. Medway

This network design has been created more securely. Workstation 2 and File server 1
are in the management network. Any device on the management network can access
any device on the entire network.

The estimated value for the devises on the whole network as follows:

Devise Description Value for single Devise Items Total Value Total for the whole
required network devises
(except service charges)

Cisco 2621 Router £ 1497.00 3 £ 4491.00

HP ProLiant ML350 G5 £ 1029.00 1 £ 1029.00


Server
Ei System 209 + 5 £
17" Widescreen £ 298.99 1494.95
TFT Monitor

Cisco WS-CSwitch-PT £ 450.00 3 £ 1350.00 £ 8364.95(service


charge will be included)

The network design will be as follow:

Sylvanus Jenkins Student ID: 000449066


Page 2
IP Addressing

The network address used here is 192.168.0.0 and for the subnet mask VLSM
(Variable length subnet mask) has been used so it will help to create the network
easier, and if there any changes in future that can be done very easily.

Avery Hill

Avery Hill Router

Fast Ethernet 0/0


IP Address 192.168.0.1
Subnet mask 255.255.255.248

Serial 0/0
IP Address 192.168.0.26
Subnet mask 255.255.255.252
Clock Rate 56000

Serial 0/1
Sylvanus Jenkins Student ID: 000449066
Page 3
IP address 192.168.0.30
Subnet mask 255.255.255.252
Clock Rate 56000

Server 1
Gateway 192.168.0.1
IP Address 192.168.0.2
Subnet mask 255.255.255.248

Work station 2
IP Address 192.168.0.3
Gateway 192.168.0.1
Subnet mask 255.255.255.248

Medway

Medway Router

Fast Ethernet 0/0


IP Address 192.168.0.9
Subnet mask 255.255.255.248

Serial 0/0
IP Address 192.168.0.25
Subnet Mask 255.255.255.252
Clock Rate 56000

Work station 3
IP Address 192.168.0.10
Gateway 192.168.0.9
Subnet mask 255.255.255.248

Work station 4
IP Address 192.168.0.11
Gateway 192.168.0.9
Subnet mask 255.255.255.248

Greenwich

Greenwich Router

Fast Ethernet 0/0


IP Address 192.168.0.17
Subnet mask 255.255.255.248

Sylvanus Jenkins Student ID: 000449066


Page 4
Serial 0/0
IP Address 192.168.0.29
Subnet Mask 255.255.255.252
Clock Rate 56000

Work station 5
IP Address 192.168.0.18
Gateway 192.168.0.17
Subnet mask 255.255.255.248

Work station 6
IP Address 192.168.0.19
Gateway 192.168.0.17
Subnet mask 255.255.255.248

IP Configure for all devises

Workstation 2

Sylvanus Jenkins Student ID: 000449066


Page 5
Workstation 3

Workstation 4

Sylvanus Jenkins Student ID: 000449066


Page 6
Workstation 5

Workstation 6

Passwords and security Management

Medway Avery Hill Greenwich


Host Name JuniadMD JunaidAV JunaidGR
Console Password Cisco Cisco Cisco
Secret password Cisco Cisco Cisco
VTY Password Cisco Cisco Cisco

Sylvanus Jenkins Student ID: 000449066


Page 7
Host name has
been created

Sylvanus Jenkins Student ID: 000449066


Page 8
Host name has
Massage of the day been created

Avery Hill

Medway

Sylvanus Jenkins Student ID: 000449066


Page 9
Massage of the
day

Greenwich

Sylvanus Jenkins Student ID: 000449066


Page 10
Avery Hill
Password

Created the password

Sylvanus Jenkins Student ID: 000449066


Page 11
Medway
Password

Password

Greenwich
Password

Password and
massage of the day

Consol Passwords for each Router as follow:

Consol password for Medway has been created

Sylvanus Jenkins Student ID: 000449066


Page 12
Password
for consol

Consol password for Greenwich has been created

Password
for consol

Sylvanus Jenkins Student ID: 000449066


Page 13
Consol password for Avery Hill has been created

Password for consol

Sylvanus Jenkins Student ID: 000449066


Page 14
VTY Password

Medway

VTY password
has been
created

VTY Password to Avery Hill has been setup

Sylvanus Jenkins Student ID: 000449066


Page 15
Show cdp neighbors for each Router

Sylvanus Jenkins Student ID: 000449066


Page 16
Show ip Route

Sylvanus Jenkins Student ID: 000449066


Page 17
Sylvanus Jenkins Student ID: 000449066
Page 18
Show ip interface

Sylvanus Jenkins Student ID: 000449066


Page 19
Show version

Sylvanus Jenkins Student ID: 000449066


Page 20
Sylvanus Jenkins Student ID: 000449066
Page 21
Sylvanus Jenkins Student ID: 000449066
Page 22
Show ip interface brief

Sylvanus Jenkins Student ID: 000449066


Page 23
Before do Access Control List I would like to make sure all the devices are
communicating, in order to do that I would like to ping to each devices so that will
help to make sure they all are sending packets.

When it was pinged from workstation 3 to work station 6 it was successful, and it has
not lost any packets and it is confirming, that they are working properly.

Sylvanus Jenkins Student ID: 000449066


Page 24
When it was pinged from workstation 4 to the server it was successful, and it has not
lost any packets.

Pinged from workstation 6 to workstation 3 and it was successful.

Sylvanus Jenkins Student ID: 000449066


Page 25
Pinged from Medway to Avery Hill was successful and success rate was 100 percent.

Pinged from Avery Hill to Medway was successful and success rate was 100 percent.

Sylvanus Jenkins Student ID: 000449066


Page 26
Pinged from Greenwich to Avery Hill was successful and success rate was 100
percent.

The above pinging massages are confirming that they are pinging without any
restrictions, and now I would like to prepare the Access Control List. In order to
create access control list it is very important to select the correct wildcard bits. It has
been used most of the time 0.0.0.0 so it will check each bits for security recent, at that
will help to protect the network.

Sylvanus Jenkins Student ID: 000449066


Page 27
Access Control Lists

1 Telnet from Medway to Greenwich Successful

From Medway which is


the Router name
junaidMD, then telnet to
Greenwich and it was
successful. And
password is required to
access.

2 Telnet from workstation 4 to Greenwich blocked

Now it has been


blocked
192.168.0.11 is
workstation 4

Sylvanus Jenkins Student ID: 000449066


Page 28
3 Telnet from workstation 5 to Medway Blocked

Now two access control list has


been created to deny access
from workstations 4 and 5, and
wildcard bits has been given to
confirm the hosts.

Standard Ip
access list

4 Telnet from workstation 2 to Medway Successful

Sylvanus Jenkins Student ID: 000449066


Page 29
5 Telnet from 2 to Greenwich Successful

6 Ping from workstation 5 to file server 1 Successful

Sylvanus Jenkins Student ID: 000449066


Page 30
Sylvanus Jenkins Student ID: 000449066
Page 31
7 ping from workstation 3 file server 1 successful

8 ping from workstation 3 to workstation 4 successful

9 ping from workstation 5 to workstation 6 successful

Sylvanus Jenkins Student ID: 000449066


Page 32
10 ping from workstation 2 to workstation 5 successful

11 ping from workstation 2 to workstation 3 successful

Sylvanus Jenkins Student ID: 000449066


Page 33
12 Ping from Router Greenwich to workstation 3 successful

13 ping from Router Medway to workstation 5 successful

Sylvanus Jenkins Student ID: 000449066


Page 34
Ping from Avery Hill Router to Server 1 successful

Sylvanus Jenkins Student ID: 000449066


Page 35
Conclusion

This network has been designed to access from three places from Avery Hill,
Greenwich, and Medway. To access any one, they will require a password unless the
administrator allowed to access to the users without the passwords. The Routers have
been given names but it can be changed, and without passwords these Routers can not
be operated remotely or Telnet in to it.

The whole network has been protected by the Access control List, so any one from out
side can not get in to use the computers or the server. Devises have been supplied here
are very good quality and can be find out any faults very quickly, so that will reduce
the amount of time wasting by students or the staffs at the University.
If the University expect a high volume of computer users in future, this design has
been created to add many numbers of computers depend on the requirements of the
University.
A Variable Length Subnet Mask (VLSM) is a means of allocating IP addressing
resources to subnets according to their individual need rather than some general
network-wide rule. Of the IP routing protocols supported by Cisco,OSPF, Dual IS-IS,
BGP-4, and EIGRP support "classless" or VLSM routes. So this is supporting to this
whole network and in future many computers can be added if that necessary.

Sylvanus Jenkins Student ID: 000449066


Page 36
Minute for a Formal Meeting
Tuesday, February 5, 2008
3:00 p.m. – 4:00 p.m.
Nelson Block A

Members present: Sylvanus Jenkins, Sandra Nanziri

Members unable to attend: Akram

Welcome and Call to Order – Sylvanus Jenkins

Sylvanus Jenkins welcomed all members present. After brief introductions, the meeting
was called to order at 3:00 p.m.

Approval of Minutes from the last meeting: None

Review Agenda for February 15, 2008 – Group Members

DISCUSSION SESSION
Sylvanus Jenkins led the discussion of the meeting. During the discussion team members
exchange contact with other team members Sylvanus Jenkins exchange with Sandra)
since Akram was not present for the meeting we could not acquired any contact from him.
We then review the assignment to begin assigning tasks to each individual. Team
members begin looking at the assignment and the required tasks.

Group MEETING
Sandra and Sylvanus Jenkins were to create the draft of the physical topologies. The first
task was to work out the IP scheme that the three networks that will be used. We then
discuss amongst ourselves the given class of our IP scheme and our given range. Both
members where to work out the IP schemed by the next meeting schedule meeting.
Several nominations were made as to who might be able to serve on the group for the
diary. Sylvanus Jenkins suggested the he will create the Diary and then Gantt chart as
well as write minute of the meeting.
To be completed by the next meeting:
• IP address scheme(Sylvanus Jenkins and Sandra)

• Creation of the first draft of the physical topologies (Sylvanus


Jenkins, Sandra)

• Diary and Gant chart(Sylvanus Jenkins and Sandra)

• Mintue of the meeting hold(Sylanus Jenkins)

Other-It became apparent the AKram had not attended the meeting. This matter was to
be brought forward in the next meeting.

Adjournment- S. Jenkins
S.Jenkins thanked members for their input. The meeting was adjourned at 3:56 p.m. The
next Group meeting is scheduled for February 15, 2008 at 9:00 a.m. in Nelson Block A.

Sylvanus Jenkins Student ID: 000449066


Page 37
Minute for a Formal Meeting
Friday, February 15, 2008
2:00 p.m. – 3:00 p.m.
Nelson Block A

Members present: Sylvanus Jenkins, Sandra Nanziri

Members unable to attend: Akram

Welcome and Call to Order – Sylvanus Jenkins

Sylvanus Jenkins welcomed all members present. After brief introductions, the meeting
was called to order at 3:00 p.m.

Minutes from the last meeting: Approve

Review Agenda for February 15, 2008 – Group Members

DISCUSSION SESSION
Sylvanus Jenkins led the discussion of the meeting. Team members were asked to
produce the complete result from task given. Akram was not present for the meeting and
could not be contacted from us. We then review the tasks each individual were suppose
to carry out by this meeting. Although an IP scheme had been worked out by Sylvanus
Jenkins and Sandra it still was a concern as we had completed our task but it was not
worked out properly. They were then told to look in to the problem and try to solve it by
the third meeting. Team members looked in to the assignment and the required tasks.

Group MEETING
Sandra and Sylvanus Jenkins were told to create the second draft of the logical topology
and physical topologies. The second agenda had been address already the (IP scheme)
three networks had been created. The team then discuss the whether or not the current
version of packet tracer had something to do with the IP scheme not working properly.
We then discuss amongst ourselves how we can address the current developed problem.
Several nominations were made as to who might be able to serve on the group for the
diary. Since Sylvanus Jenkins had created the diary and Gant chart they were then
updated to remind ourselves of the progress made.
To be completed by the next meeting:
• IP address scheme(Sylvanus Jenkins and Sandra)

• Creation of the Second draft of the physical topologies and


logical topology (Sylvanus Jenkins, Sandra)

• Diary and Gant chart where to be updated (Sylvanus Jenkins and


Sandra)

• Minute of the meeting hold(Sylvanus Jenkins)

Other-It became apparent the AKram had not attended this meeting. This matter was to
be brought forward that he should attend the next meeting or he is no longer part of the
team.
Sylvanus Jenkins Student ID: 000449066
Page 38
Adjournment- S. Jenkins
S.Jenkins thanked members for their input. The meeting was adjourned at 2:56 p.m. The
next Group meeting is scheduled for February 21, 2008 at 9:00 a.m. in Nelson Block A.

Sylvanus Jenkins Student ID: 000449066


Page 39
Minute for a formal meeting
Thursday, February 21, 2008
3:00 p.m. – 4:00 p.m.
Nelson Block A

Members present: Sylvanus Jenkins, Sandra Nanziri

Members unable to attend: AKram

Welcome and Call to Order – Sylvanus Jenkins

Sylvanus Jenkins welcomed all members present. After brief introductions, the meeting was
called to order at 2:00 p.m.

Minutes from the last meeting: Approved

Review Agenda for February 15, 2008 – Group Members

DISCUSSION SESSION
S.Jenkins led the discussion with team members aware that the topologies had been
created and now working the discussion of configuration came into place and
completion of the network. It was apparent to each individual the network is working.
They then began to discuss the write up of the technical documentation. Several
people made suggestions as to how this should be done in accordance with the
required specification. We then review the progress made and record it in the diary.
However during the meeting team members was alerted to that the network had not be
advertise on the network and that needed to be done.

Group MEETING
The first meeting review was the first one where action is needed to be taken to address
one team member. AKam it was decided that is no longer part of the team as he had not
attended any of the meetings and had their for not put in work contributing to the group
work. The next review is for the advancement in the amount of work done per week in
other to meet the given deadline. The next tasks was the needed presentation for the
create network and it benefits; upgrade scenarios; expected performance etc was also
discuss and will be brought forward in the next meeting.

To be started by the next meet:


• Final Physical Network in working order

• Update of the Diary and Gantt chart

• Technical documentation

Other-It became apparent the AKram had not attended the meeting. This matter was to
be brought forward in the next meeting.

Adjournment- S. Jenkins
S.Jenkins thanked members for their input. The meeting was adjourned at 3:56 p.m. The
next Group meeting is scheduled for February 28, 2008 at 9:00 a.m. in Nelson Block A.

Sylvanus Jenkins Student ID: 000449066


Page 40
Minute for a formal meeting
Thursday, February 28, 2008
3:00 p.m. – 4:00 p.m.
Nelson Block A

Members present: Sylvanus Jenkins, Sandra Nanziri

Members unable to attend: Akram

Welcome and Call to Order – Sylvanus Jenkins

Sylvanus Jenkins welcomed all members present. After brief introductions, the meeting
was called to order at 3:00 p.m.

Minutes from the last meeting: Approved

Review Agenda for February 21, 2008 – Group Members

DISCUSSION SESSION
S.Jenkins led the discussion with team members about the Technical Document that
Sylvanus Jenkins and Sandra Nanziri were to work on it. The configuration of the
physical network had been completed as explained in the documentation. The group
began the discussion on access control list and suggested that Sylvanus Jenkins and
Sandra the only members of the team were to complete that task. While testing the
network, the team leaders Sylvanus Jenkins began implementing security produce to
prevent authorised users from accessing the network. This discussion was also to be
brought to the next meeting as a topic of discussion. Also discuss was the update of the
Diary and Gantt chart. From the previous meeting it was brought to our attention that a
presentation is required regarding the cost and other issue pertaining to that. The
Technical documentation is worked on to ensure progress is made.

Group MEETING
The next review is for the advancement in the amount of work done per week in other to
meet the given deadline. The next tasks was the needed presentation for the create
network and it benefits; upgrade scenarios; expected performance etc was also discuss
and will be brought forward in the next meeting. The first meeting review was the first
one where action is needed to be taken to address one team member. AKam it was
decided that is no longer part of the team as he had not attended any of the meetings and
had their for not put in work contributing to the group work.

Other-It became apparent the AKam had not attended the meeting. This matter was to be
brought forward in the next meeting.

Adjournment- S. Jenkins
S.Jenkins thanked members for their input. The meeting was adjourned at 3:56 p.m. The
next Group meeting is scheduled for March 3, 2008 at 9:00 a.m. in Nelson Block A.

Sylvanus Jenkins Student ID: 000449066


Page 41
Minute for a formal meeting
Monday, March 3, 2008
3:00 p.m. – 4:00 p.m.
Nelson Block A

Members present: Sylvanus Jenkins, Sandra Nanziri

Members unable to attend: Akram

Welcome and Call to Order – Sylvanus Jenkins

Sylvanus Jenkins welcomed all members present. After brief introductions, the meeting
was called to order at 3:00 p.m.

Minutes from the last meeting: Approved

Review Agenda for February 28, 2008 – Group Members

DISCUSSION SESSION
S.Jenkins led the discussion with team members on Access control List. Team
members Sylvanus Jenkins and Sandra are to begin are to begin Access control list on
each network. It was discussed that it should be perform so network user would be
able to access all network devices and workstations. Also discussed was the update of
the Diary and Gantt chart. From the previous meeting it was brought to our attention that
a presentation is required regarding the cost and other issue pertaining to that.

Group MEETING
Review is for the advancement in the amount of work done per week in other to meet the
given deadline. The next tasks was the needed presentation for the create network and it
benefits; upgrade scenarios; expected performance etc was also discuss and will be
brought forward in the next meeting.

Other-None

Adjournment- S. Jenkins
S.Jenkins thanked members for their input. The meeting was adjourned at 3:56 p.m. The
next Group meeting is scheduled for March 10, 2008 at 9:00 a.m. in Nelson Block A.

Sylvanus Jenkins Student ID: 000449066


Page 42
Minute for a formal meeting
Monday, March 10, 2008
3:00 p.m. – 4:00 p.m.
Nelson Block A
Members present: Sylvanus Jenkins, Sandra Nanziri

Members unable to attend: Akram

Welcome and Call to Order – Sylvanus Jenkins

Sylvanus Jenkins welcomed all members present. After brief introductions, the meeting
was called to order at 3:00 p.m.

Minutes from the last meeting: Approved

Review Agenda for March 3, 2008 – Group Members

DISCUSSION SESSION
S.Jenkins led the discussion with team members on Access control List. Team
members Sylvanus Jenkins and Sandra are to complete Access control list on each
network. They are also discussed that it should be perform so network user would be
able to access all network devices and workstations. They are to complete the update
Technical Documentation with by adding Access control list to it. Also discussed was
the update of the Diary and Gantt chart. From the previous meeting it was brought to our
attention that a presentation is required regarding the cost and other issue pertaining to be
completed as well.

Group MEETING
The completion of the diary, Gantt chart, technical document and minute of the meeting
held. The next tasks was the needed presentation for the create network and it benefits;
upgrade scenarios; expected performance etc was also discuss and will be brought
forward in the next meeting.

Other-None

Adjournment- S. Jenkins
S.Jenkins thanked members for their input. The meeting was adjourned at 3:56 p.m. The
next Group meeting is scheduled for March 13, 2008 at 9:00 a.m. in Nelson Block A.

Sylvanus Jenkins Student ID: 000449066


Page 43
Sylvanus Jenkins Student ID: 000449066
Page 44