Introduction To Networking LANS and

WANS
Foundation Degree in IT for Business
By: Emma Jessup

Staffordshire University
Date Issued: 23/02/09
Submission Date: 27/03/09
Recipient: Ivo Chakarov

A Report On The Networking LANS and WANS case study.

By Emma Jessup

Recipient: Ivo Chakarov

Abstract

The evidence in this report shows how to configure the new network for the
Warmingham Health Authority. The report will include how the IP addresses
were worked out so that the network could be configured; there will be an
estimate of the costs to put the project together for the all the sites, the report will
show the cabling diagram. This will show where the cabling has to be placed
under the floorboards so that the end machines will be connected to the switches.
The cabling diagram will be an example of one floor at one of the sites, therefore,
this will give an idea of what needs to be completed at all sites for the network to
operate correctly. The report will explain how the system will be configured. It
will explain how the simulation on packet tracer works. This will give the
hospital a proposal of how this network is going to work for what the want it to
do. The simulation will show a fully working design, which the hospitals network
will be based on.

Acknowledgements
None

Contents

Terms Of Reference
Forward
This report will consider the hospitals requirements for the new future proof network
that the hospitals require so that they can work to the appropriate degree of accuracy.
The report will explain how to work out the correct IP addresses for the given network
address for the machines. A cabling diagram will be shown to explain how the
machines are going to reach the two switches on one floor of one of the three sites.
Also the way in which the network is going to be configured will be explained and
what it has been done is this particular way. The main objective of the report is to
show the hospital, which is described in the case study how the desired structure of
the network is possible and how this may be completed so that all three sites have a
fully working, future proof network.

Aim
1. To describe how the IP addresses we found out.
2. To describe how and why particular goods were chosen for costing.
3. To provide a cabling diagram to show how the computers will be connected to the
switches on one floor of one of the sites.
4. To show how the full network can be configured so that everything is connected as
shown in the diagram in the case study.
5. To explain the costing of the project and why chose certain equipment
6. Write a conclusion involving the case study and how the findings were created.
Objectives
1. To gather information on subnetting and VLSM.
2. To evaluate how the costs were put together and why.
3. To use the internet to find out information on costing for equipment and labour
4. To use books and discussions with engineers on how use cabling.
5. To collate all relevant information and findings in a report to show how the network
can be configured accurately for the hospital described in the case study.

1.0 Method
The information within this report was collected from

The internet to investigate subnetting, VLSM and costing for the equipment to
make the network useful.
Discussions with engineers to investigate best ways for cabling.

Packet tracer to show a simulation to show the hospital what their network is
going to be like and to show that it is possible to get the network working.

1.1 Introduction
This report is designed to show that it is possible for the scenario in the case study to
be successful in a working environment. The report will explain how the IP
configuration has been worked out so that all three hospitals can talk to one another
via the network. The report will show how one floor in one of the sites is going to be
cabled. This will then give an estimate of what is needed in cable for the whole
network as a rough estimate can be worked out. The network needs to be built so that
if changes need to be made in the future it is possible to do so. Prices will be shown
and described why certain equipment has been chosen for this particular network
shown in the case study. Overall the report is going to explain how the network can be
configured so that it will work effectively and efficiently for the hospitals involved.

2.0 Findings
2.1 IP Addressing
The given IP address for the hospital in the case study is 172.168.0.0. Therefore this
makes the IP address a class B IP address. As the address is class B, this would
make the default subnet mask 255.255.0.0. Knowing this helps when requiring
the IP addresses that are needed as shown in the table below.
The Case study required VLSM (variable length subnet mask) to be used to
address the network. VLSM is a means of allocating IP addressing to subnets
according to their individual need. VLSM is used so that the minimum amounts
of subnets are used so that they can be used for future growth.
When addressing the network described in the case study I will use VLSM. To work
this out correctly I will start with the highest number of hosts and then work from
the highest number of hosts to the lowest. This is done so that no IP addresses
will be wasted by going in the highest number of hosts.
The numbers of hosts required for the network are
120 hosts For doctors at the Audley hospital
120 hosts For the doctors at the Peover hospital
90 hosts For the administration at the Audley hospital
90 hosts For the administration at the peover hospital
25 hosts For the warmingham HQ site
2 hosts For the Patient records and the healthcare server

The starting point was finding IP addressing for 120 hosts. This was worked out
by using subnetting as shown below.

128

64

32

16

This table shows how many bits are needed to get to 120. As the bits start at 64 to
equal to 120 it shows that 7 bits are required. This is because the table above
shows that from 64 to 1 there are 7 numbers used. This is how the number of bits
is worked out.

Once the number of bits is worked out the subnet needs to be considered.

The default subnet mask for a class B IP address is 255.255.0.0. The first two
octets of the subnet mask do not change. This is because it is a class B IP address.

This subnet mask needs to be worked out in binary which is

255.255.00000000.00000000
When dealing with the subnet mask, 0 is equivalent to host bits and 1 is equivalent
to network bits.
As the case study requires 120 hosts, it is essential that the subnet mask has 7 host
bits. Therefore, this would make the subnet mask
255.255.11111111.10000000
This address shows that there are now seven host bits and that any remaining bits
within the octet will become network bits.
When this subnet mask is converted back into decimal the new subnet mask for
this range is created which is
255.255.255.128
For the network to work correctly we need to work out the ranges. The ranges are
found out by taking the lowest number in the subnet mask and then find the
equivalent to the numbers position in binary.
I.e. 10000000 = 1 = 128
As this 1 represents 128 in binary it means that you need to add 128 to the address
in the fourth octet. You go up in 128s until you have reached 255. This is because
it is valid within this range.
From this it can be shown that there are two network ranges for this for the
network to support 120 hosts. To find out the end address you must minus one
from the next range.
e.g. 172.168.0.0 end address is 172.168.0.127 etc. (the 1 has been subtracted from
the 128.)

From this you can work out that the range of IP addresses in the first network
(Audley Hospital) will be 172.168.0.0 172.168.0.127 and the last range is
172.168.0.255.
As all of the IP addresses have been used for both sets of the 120 hosts
(172.168.0.0 172.168.0.255) the next range will have to be used for the 90 hosts.
This will start from 172.168.1.0.
Here are the ranges that I have used for all hosts.
IP address = 172.168.0.0
Subnet Mask = 255.255.0.0
120 hosts = 172.168.0.0 172.168.0.127
172.168.0.128 172.168.0.255

/25
/25

90 hosts = 172.168.1.0 172.168.1.0 172.168.1.127

172.168.1.128 172.168.1.255

25 hosts = 172.168.2.32 172.168.2.31

/25

/25

/27

2 hosts = 172.168.2.32 172.168.2.35 /30

172.168.2.36 172.168.2.39

/30

Below you will find the table which shows all of the required IP addresses needed
for each site described in the case study. These addresses have been worked out by
using the above method. The IP addresses have also been used for configuring the
network via packet tracer.

2.2 IP Address Configuration

Host/ Interface

IP address
start
Doctor Machine 172.168.0.1
Audley
Admin Machine 172.168.1.1
Audley
Doctor machine 172.168.0.129
peover
Admin machine 172.168.1.129
Peover
Audley router
172.168.0.126
Fa0/0
Peover router
172.168.0.254
Fa0/0
Audley router
172.168.1.126
Fa0/1
Peover router
172.168.1.254
Fa0/1
Audley router
172.168.2.34
serial 0/0
Peover router
172.168.2.37
serial 0/0
Warmingham
172.168.2.30
router Fa0/0
Warmingham
172.168.2.33
router serial 0/0

IP address end

Mask

DCT/DTE*
N/A

Default
Gateway*
172.168.0.126

Broadcast
address
172.168.0.127

Network
Address
172.168.0.0

172.168.0.126

25

172.168.1.126

25

N/A

172.168.0.126

172.168.1.127

172.168.1.0

172.168.0.254

25

N/A

172.168.0.254

172.168.0.255

172.168.0.128

172.168.1.254

25

N/A

172.168.1.254

172.168.1.255

172.168.1.128

N/A

25

N/A

N/A

172.168.0.127

172.168.0.0

N/A

25

N/A

N/A

172.168.0.255

172.168.0.128

N/A

25

N/A

N/A

172.168.1.127

172.168.0.0

N/A

25

N/A

N/A

178.168.1.255

172.168.1.128

N/A

30

DTE

N/A

172.168.2.35

172.168.2.30

N/A

30

DTE

N/A

172.168.2.31

172.168.2.0

N/A

27

N/A

N/A

172.168.2.31

172.168.2.0

172.168.2.34

30

DCE

N/A

172.168.2.35

172.168.2.32

Warmingham
router serial 0/1
Warmingham
router serial 0/2
Patient records
Health care
server

172.168.2.37

172.168.2.38

30

DCE

N/A

172.168.2.39

172.168.2.36

145.45.5.100

N/A

N/A

DTE

N/A

145.45.5.100

145.45.5.100

172.168.2.1
172.168.2.2

172.168.2.30
172.168.2.30

27
27

N/A
N/A

172.168.2.30
172.168.2.30

172.168.2.31
172.168.2.31

172.168.2.0
172.168.2.1

2.2 Project costs

The average price for a technician is 250 for 2 hours work and if the technician
works on average eight hours a day, five days a week this averages to about
1250.00 for employ the technician for the week. It is estimated that the job will
take approximately eight months to complete. This gives the total cost for a
technician to set up the network for 40,000.00. I have used eight months as the
technician will have to set up each of the computers on each site, complete the
cabling and configure the routers so that they can talk to on another from all of
the sites. Eight months should give the technician enough time to complete the
job to a good standard and make the network do what the hospital wants it to do.
The desktop that I have chosen to use to set up the network is the Zoostorm advanced
premium PC plus the Samsung 22 TFT monitor. For the 420 desktops needed
this would cost 275440.20 altogether. This desktop is ideal for use in the
hospitals as it can store up to 4GB of RAM. This will be enough room for the
desktops to store the necessary information which is needed to store patient
information. The PC also has a 640GB hard drive which means that it will run
much faster when compared to a normal PC. This will be ideal for the hospitals as
the large amount of RAM and large hard drive mean that the PCs have room for
further growth if needed in the future. The PCs will be able to store much more
data in the future if needed when compared to what they need now and this is
why this particular PC has been chosen.
The switches that have been chosen are the WS-C3560-48TS-S - Cisco Catalyst 356048TS SMI - switch - 48 ports. I will need eleven of these switches to allow for
future expansion. The eleven switches will cost 24803.35. This particular switch
has been chosen because it has a data transfer rate of 100mbps. This is fast
enough for the three sites to transfer data across to one another without delay.
This is necessary as it is a hospital and patient records will be needed quickly.
This is why this particular switch has been chosen it allows room for expansion
and has an ideal data transfer rate for the hospital in question.

The router chosen for the network is a CISCO2801-SEC/K9 - Cisco 2801 Security
Bundle router. The costing for three of these routers is 3708.66. One router
will be used per site. This router has been chosen because it has a high RAM of
256mb to store data. This will allow the hospital store more information and the
data transferred from site to site can be stored more efficiently. Also this
particular router has hardware encryption installed on it and uses advanced Cisco
security. Therefore, the network is less likely to catch any viruses or get hacked
into which would be a serious problem for the hospital as they hold highly
confidential data on its patients.

The cabling has been priced up for the floor plan shown further down in the report.
This is so that an average cost can be given to estimate the price of cabling for the
whole project. The costing for the cabling on the one floor of one site is 202.40.
It is approximately 600 metres that is needed. I have calculated spare cabling into
this costing for error and in case it is needed in the future. From this figure it can
be estimated what needs to be completed on the other floors or the other buildings
and how and how much each site might cost for the total project.

Total costing for this project is = 344154.61

2.3 Cabling Diagram

2.4 Configuration explained

Within packet tracer I set up the network diagram as shown in the case study. Once
the diagram was set up I started to configure the network. I did this by working from
one site to another. This made it clear and concise to follow when building the
network. The first thing that I did before configuring the system was to give the hosts
in each site the correct IP addresses and subnet. This was done so that each host could
communicate with one another.
When starting configuring the first thing to do is to give the router a host name.
To give the router a host name you need to start from global configuration mode. To
get to global configuration mode you need to
Enable exec mode
Configure terminal global configuration mode
Hostname <hostname>
By doing this it gives you the name of your router.
Once this was completed I configured the interfaces with the correct IP addresses and
subnet masks.
To do this I did..
Interface <interface> <IP address> <subnet mask>
No shut (the interface is shut down by default, however to turn it on this command is
used.)
If the router has a serial cable connected to it which is DCE then the clock rate needs
to be set for that line. The command is
Clock rate <speed in bits>
The clock rate is usually set by the internet service provider. However in this given
network the clock rates have been set individually.
Once the PCs and routers interface was set up with IP addresses, I tested that they
were configured correctly by completing a ping test. A ping test allows you to see if
data can reach across the network.
When all of the sites were talking to each other I implemented EIGRP. EIGRP is a
routing protocol. This routing protocol allows all of the routers to send updates about
routing to one another. Routers can talk to networks which are directly connected to
them. Without the routing protocol the routers would not be able to talk to other
networks that were connected.
Within packet tracer to configure EIGRP I carried out the following commands.
Router eigrp < autonomous system number>
Network <network advertising> <wild card mask>
Doing this in configuration allowed the network to set up neighbour relationships to
exchange router information.

The protocol used on serial 2/0 that connects the internet service provider is showing
as being down. This is because packet tracer does not allow you to set the clock rate
of the line from the internet service provider. To overcome this problem I simulated an
internet service provider address as a loopback address set on the Warmingham SH
site.
The commands which I used to do this are as follows from the global configuration
mode
Interface loopback <loopback number> < IP address> <subnet mask>
On a network you would usually set a default route to the internet as it is not advised
to advertise the IP address via the routing protocol as this will decrease the security
set on the network.
Once this was completed each site had full connectivity. Therefore, once this was
done I put a description on each of the interfaces to do this you need to use the
commands:Description <description>
A message of the day (MOTD) also needed to be added to the configuration. For this
you need to make up a message for example unauthorised access will be reported.
To configure the message of the day you use
Banner motd <unauthorised access will be reported>
The next step is to configure the passwords on the network. The passwords are needed
for when someone tries to gain access to a privileged exec mode they will require a
password to gain access to this. (All of the passwords set in packet tracer are cisco0
To enable a password within configuring you use the commands
Enable secret <password>
Using the enable secret command is a very secure method to use so that no
unauthorised access in gained into the network.
The next password to set is the password for the console port. This is also done from
global configuration mode.
The commands are:Line console 0
password <password>
Login
The login command is the most important command as it specifies the router needs to
send a prompt for a password.
The next task is to set the passwords for the vty ports the commands to use are:Line vty 0 4 (supports five terminal sessions)
password <password>
login
The final thing to complete within configuration is to set up a host table. This enables
the user to type the name of the device rather then using telnet and the IP address of
the interface of the router.
This is completed by using the command:IP host <hostname of router> <IP address of the interface>
The final thing to configure was to use write memory. This saves the configuration
which has been carried out on the network. Once this has been completed the
configuration is saved and used as all of the devices have full connectivity and can
talk to one another by configuring the network in this way.

3.0 Conclusion

Overall by writing this report it is evident that the network that the hospital requires is
possible to complete even though it may be timely and costly. The report shows how
the configuration of the network can be carried out and why it is done in such a way.
However, if I were to do this project again I would change the way of doing the
cabling as it is difficult to estimate how much it would cost for three sites to be cabled
in different ways. Overall, the report is trying to show how much a project like this
would cost to set up and hoe IP addresses can be found out for the whole network to
be configured and have full connectivity throughout the whole network.

References/Bibliography
Cabling4less [online] available at http://cabling4less.co.uk/index.php?
action=search&searchTerm=rj45 [Accessed 24 March 2009]
Cisco [online] available at http://www.hardware.com/store/Cisco/WS-C3560-48TS-S
[Accessed 24 March 2009]
Cisco [online] available at http://www.hardware.com/store/Cisco/CISCO2801SEC/K9 [Accessed 24 March 2009]
Ebuyer [online] available at http://www.ebuyer.com/product/159365
[Accesses 24 March 2009]
Foundry [online] available at http://www.hardware.com/store/Foundry/EIF48G
[accessed 25 March 2009]