Network Project Plan ~ 1 ~
Table of Contents
Network Project Plan Executive Summary..................................................................................... 4
Chapter 1 – Introduction of the Organization and its Requirements .............................................. 5
Introduction 1-1........................................................................................................................... 5
Geographical Location 1-2.......................................................................................................... 5
Campus Volume 1-3.................................................................................................................... 6
Physical Topology 1-4 ................................................................................................................ 6
Needs Assessment 1-5................................................................................................................. 7
Administrator’s Responsibility 1-6............................................................................................. 8
Conclusion 1-7 ............................................................................................................................ 9
Chapter - 2: Network Architecture Design ................................................................................. 10
Network Architecture -2.1......................................................................................................... 10
Physical Topology - 2.2 ............................................................................................................ 11
Advantages verses Disadvantages - 2.3 .................................................................................... 12
Methods of Access - 2.4............................................................................................................ 13
Network Performance and Over site - 2.5................................................................................. 15
Conclusion - 2.6 ........................................................................................................................ 16
Chapter - 3: Network Model or Stacks ....................................................................................... 17
Network Model Overview - 3.1 ................................................................................................ 17
The Open Systems Interconnect OSI Reference Model - 3.2 ................................................... 18
History of (OSI) Model - 3.3..................................................................................................... 18
OSI Layers Defined - 3.4 .......................................................................................................... 19
The Physical Layer 3.4.1 ....................................................................................................... 20
The Data-Link Layer – 3.4.2 ................................................................................................. 20
Network Layer – 3.4.3.......................................................................................................... 21
The Transport Layer – 3.4.4 .................................................................................................. 22
The Session Layer -3.4.5 ....................................................................................................... 23
The Presentation Layer – 3.4.6 .............................................................................................. 23
The Application Layer – 3.4.7............................................................................................... 23
TCP/IP Internet Suite 3.5 (Fujitsu, p.p. 1-12, 2006)..................................................................... 24
TCP/IP Layers Overview 3.5.1.............................................................................................. 24
History of TCP/IP 3.5.2 ......................................................................................................... 25

The TCP/IP Suite Network Example 3.6 .................................................................................. 26
The Application Layer 3.6.1.................................................................................................. 26
The Transport Layer 3.6.2 ..................................................................................................... 26
The Internet Layer 3.6.3 ........................................................................................................ 28
The Network Access Layer 3.6.4 .......................................................................................... 29
Layer Intercommunications 3.7................................................................................................. 30
Conclusion 3.8........................................................................................................................... 32
Chapter - 4: Network Protocols .................................................................................................. 33
Introduction 4.1 ......................................................................................................................... 33
Individual Protocol Responsibilities 4.2 ................................................................................... 34
TCP/IP in Campus Network 4.2.1 ......................................................................................... 34
The Router 4.2.2 .................................................................................................................... 35
The Multi-Layer Switch 4.2.3 ............................................................................................... 35
The Firewall 4.2.4.................................................................................................................. 36
The Client / Servers 4.2.5 ...................................................................................................... 37
VoIP Controller 4.2.6 ............................................................................................................ 38
Computers 4.2.7..................................................................................................................... 39
Management Agents for the Network 4.3 ................................................................................. 39
Security Concerns 4.4 ............................................................................................................... 40
Conclusion 4.5........................................................................................................................... 41
Chapter - 5: Network Security.................................................................................................... 43
Introduction 5.1 ......................................................................................................................... 43
Cyber Attack Awareness 5.2..................................................................................................... 43
Malware 5.3............................................................................................................................... 45
Computer Updates 5.4............................................................................................................... 47
Conclusion 5.5........................................................................................................................... 49
Chapter - 6: Network Management............................................................................................ 50
Introduction 6.1 ......................................................................................................................... 50
IT Manager Tools 6.2................................................................................................................ 51
Base Lining 6.3 ......................................................................................................................... 52
Back IT UP! 6.4 ........................................................................................................................ 52
The Trouble Shooting Process .................................................................................................. 54

Conclusion................................................................................................................................. 55
References..................................................................................................................................... 56

NETWORK MANAGEMENT GUIDE
Network ProjectPlanExecutive Summary
The purpose of this project is to lay the needed overview and specifications for the local school
campus geographically located with my home town. The campus has a Local Area Network
(LAN) star hybrid configuration on the campus. My intention is to really discover the formal
layout of the campus in the two types of topologies presently used in identifying this network.
The logical and physical topology might not accurately match as the administrator has related
this campus is presently undergoing constant upgrades and deployment to facilitate the nearly
600 users throughout this network. This network also runs on many different types of
application program interfaces for local and for web based services. My initial belief is these
programs are causing some of the problems interfaced with the network. Addressing problems
and lack of virtual private networks may be other indicators of problem areas within this network
along with back bone symmetry. The system itself is an antiquated system which was basically
set up on an old bus style network and this has caused the problem of each of the star based
schools being able to access the other schools without having to go through proper routers for
proper security and has caused multiple collisions as the Individual data facilities (IDF’s) and
will interact with each other and not prioritize to the main data facility when multiple computers
access the nodes at the same time. The administrator has many things to consider when
addressing these issues. Since there is only one IT person managing this whole system and
managing it with antiquated or adequate software applications the capability to quickly access
faults can only be alarmed when other components fail to operate. Ultimately this network has
many flaws and with proper deployment of new components, software, and topology
reconfiguration it’s intended to make it work better. We’ll look at all of this.

Chapter 1 – Introduction of the Organization and its Requirements
Introduction 1-1
Finding a network to meet the demands of many personnel, application performance,
communications and other necessities was hard to fathom. I tried to think of a place I would use
as a case study scenario which could meet all the needs as might be addressed as a working
network. I realized I had a perfect organization sitting right in my own little town that met all the
criteria to pin point precision. The school grounds located just blocks from my house was the
perfect candidate for what I was about to embark on. I just needed to see ensure a few things.
Would the above needs meet the challenge for what I was going to be going for? Would this
network be big enough to show topologies, backbones, hardware usage and management, and
media through put and similar other criteria needed for my example scenario? It was time to do
a little research with the school campus personnel to see if this would be an amiable site to begin
a case study.
Geographical Location 1-2
The school has seven different facilities located on a 40 acre area. When entering the
town from the north, the overall campus is viewable on both sides of Williams Street. On the
right side a driver will immediately see the junior high, the elementary and the high school on the
right and the school transportation building on the left side of the street. The football field is
directly behind the junior high, the music department directly behind the elementary school and
the big gymnasium is located behind the high school. This is pertinent as the whole network is
backboned to all facilities through a collapsing type backbone network. This is needed as all the

facilities rely on the network to accommodate students and personnel within these facilities. The
institutional capacity of these facilities is growing.
Campus Volume 1-3
Back in 1923 when The Mossyrock school system was first established, only 16 students
graduated (mossyrock.com, 2014). Today’s standard is much larger with around 40 students
graduating yearly. It has not increased by leaps and bounds, but given the fact we have 40
students per grade, equates out to close to 400 plus students on a yearly basis
(cityofmossyrock.com, 2014), along with 75 plus staff and faculty personnel
(mossyrockschools.org, 2014) working at all these facilities. We haven’t included the
transportation portion but they house 12 buses and have mechanics and administration, which
would include 12 drivers, 3 mechanics and management personnel all competing for computer
use at some point or other. With an institution of this proportion there has to be a notable
network to sustain this usage demand.
Physical Topology 1-4
I visited with John Van Pelt, (Jan 2014) and queried the actual layout of the school
campus. The configuration has the following components. Everything goes in and out of the
campus on a T1 Multi-mode fiber line connecting to a Cisco Firewall. The data is transferred to
the master router; the information is switched out through multiple switches to areas of need.
The backbone from this area becomes collapsed as it is routed to different facilities. The router
sends the data to five possible switches and one wireless control board. The five switches send
data over 1 Gb Multi-mode Fiber lines to switches located in each of the facilities. The junior
high has four switches to accommodate junction with transportation, football field, and special

needs sector. Total amount of switches are 17 switches located throughout the facilities and 5
wireless controllers mounted in the individual data facilities (IDF) of each school building.
From the (IDF’s), Cat-6/1000BASE-T cable runs from each switching unit, to patch panels and
then to the existing wall sockets within every room. Noted also, was the ability for the network
to run (VoIP) Voice over IP phone system within the network. These phones sockets are equal
to the amount of sockets already in place for computer and printer usage. The elementary school
was also equipped with digital surveillance equipment constantly monitoring the grounds
through use of digital cameras with fiber optic uplink directly to the elementary school and being
switched to the high school main data facility (MDF) for real time observations. Wired wall
nodes for this system accommodate 163 physically attached computers and printers as well as an
additional 50 laptops accessing hot spots within the wireless local area network (WLAN) for
teachers. Finally, 8 stacked Cisco servers are in the basement of the elementary school and are
linked directly to the main panel stack located upstairs.
Needs Assessment 1-5
Personal observations of the daily usage of the network by all users brought a realization
that the ratio of component usage was almost 4 to 1. I questioned the productivity scale of all
staff, faculty and students being able to access resources at any given time. Most of the students
are not constantly using computers every second of the day. However, it was observed the
present architecture still needs improvement based on the fact that a great majority of the
components are antiquated and are ready for disposal. The school IT Manager explained
presently, almost 80 % of the operational computers are at the end of their life cycles and will
need to be replaced by the following year, along with the software. Most of the users were
constantly having stoppages, lock ups, or incompatibility issues based on services provided.

Further, the network itself was still in the process of being upgraded to support the volume it’s
intended to handle. There is a high volume of traffic currently colliding throughout the network
due to this very omission. The collisions may be reduced by inserting sub network environments
into the network. The network handles an additional phone system and provides a web page
partitioned to let all parents gain access to their children’s progress and grades. With 400
students attending this means there are 400 plus parents using the system as well. Even though it
a separate, secured, partitioned area, it still represents usage of this particular network. (Van Pelt
J., {P.I.}, 2014)
Administrator’s Responsibility 1-6
The school IT Manager expressed when he first arrived two years ago there were 12
separate closed networks running within the network and none of them were able to really
communicate with the servers or even each other for that matter. His first task was to call in
Cisco and develop a workable plan to get the campus network running again from ground up.
The main frames were upgrade, wireless upgraded; sockets properly run to patch panels, patch
panels to switches. (Van Pelt J., {P.I.}, 2014) Computers were all torn down to see what could
be upgraded and what couldn’t. I was part of that process doing over one hundred computers
with image software. It’s still a long road and the school administrator is wearing many hats in
this particular job as he is the only person available when it comes to running this network.
There are no assisting IT personnel. The only IT people he has are volunteers. This is quite
amazing considering the amount of work I have seen performed within the last two years. This
system has gone from antiquated to fully operational. There is still a lot left to do but as my
physical tutor as told me. (Van Pelt J., {P.I.}, 2014) ”It’s an ongoing party”.

Conclusion 1-7
The initial identification of this network involved looking at the geographical layout as it
is part of possible expansion is the need should arise. We saw that the campus has potential, due
to its large geography, of culminating more facilities and therefore expanding further network
capabilities. The present campus volume is such that a strain has already been placed on the
existing network. It is basically a bus type local area network and needs to be improved with a
form of subnet frame work throughout to be able to sustain the amount of traffic presently
demanded. Even by an explanation of the physical topology we know that more equipment is
needed to sharpen the performance of this campus. The local administrator has already seen
there is room for improvement and he is managing a network with multiple titles. The entirety of
the progression rests solely on his shoulders. He is managing further research and development,
initial deployment of new components, day-to-day operations and maintenance, Inventory
control procedures, audits, decommissioning of antiquated equipment and a myriad of other
tasking’s.

Chapter - 2: Network Architecture Design
Network Architecture -2.1
Network Architecture, as defined by (Kioskea.net, 2014) is the logical and structural layout
of the network consisting of transmission equipment, software and communication protocols and
infrastructure (wired or wireless) transmission of data and connectivity between two or more
components. Architecture by any means is a buildup based on multiple factors. In my case
scenario, I have close to 600 users benefitting from the network presently in place, on the local
campus network. Is this network efficient to quickly administer media, information and
communication and various other services? As has been currently assessed, this present network
has a combination of a star, bus, hybrid combination with multiple data/internet servers all built
into one network. We know that it isn’t a huge expanse that has to connect to other schools via
the internet or to other towns. Therefore, it is not considered a wide area network (WAN) or a
metropolitan Area network (MAN) by any means. It connects through numerous switches within
each of the buildings and with multi-mode Fiber between buildings for its backbone. How it
connects is based on types of application program interfaces (API’s) being able to communicate
based on transfer control protocol/internet protocol (TCP/IP) for analog to digital transmission
and receivership. These are broken down into further access methods based on the protocol from
each of the independent applications. Weather it is a program for processing a document or
talking on the phone, watching a video, doing a system scan for reliability or any other
procedure. All applications are working with the hard within the network to ensure performance
and reliability throughout. Let’s take a look at each individually to see how it does work within
the network.

Physical Topology - 2.2
The school is a K-12 campus running down the main street from the entrance into town.
Coming South off the highway, one can immediately see the junior high on the right, followed
by the elementary school and then the high school. The school transportation building is across
the street from the junior high. Two other buildings associated with the school are positioned
directly behind the elementary school (the music – drama building) and the high school (the
gymnasium), positioned behind the high school. West of these buildings lies the football field
(behind the junior high school). Presented below (figure 1-1) is a mock up I drew to represent
the geographical/physical topology of the local campus. This is markedly different from the
proposed logical topology.
Figure1-1
Figure 1-2 shows the logical topology of the campus when it was upgraded and reflected a
type of star topology. I found they had not shown the wiring system stretching from building to
building but I was told the buildings can interconnect without going through the main data
facility. This portion cannot be monitored due to it being part of the old back bone. However, it
is there and can run to another building without using the proper hub.

Figure1-2
Advantages verses Disadvantages - 2.3
The bus/star hybrid topology network appears to have some advantages according to
(Meyers, 2004, p.76). Star Bus topology is a hybrid, or blend, of the star and bus topologies and
uses a physical star design, which provides improved reliability and a logical bus to maintain
compatibility with existing bus-topology Ethernet standards. The campus is connected by a
single line, which could make that portion a bus topology. Its back bone is collapsed as it runs
out to the MDF, IDF’s and switch/hubs where the star topology forms. If it was bus topology all
the way through, it would be easy to attach more computers, be more cost efficient, and would
U N I V E R S I T Y
Local School
Campus in 1
block area
Elementary Gym
(IDF)
High School
Gym
(IDF)
High School, (IDF),
Control Room
Football Stadium,
(IDF)
Junior High
School, (IDF)
Elementary School
(IDF), (MDF)
Transportation
(IDF)
Music Building
Annex (IDF)
- 6 strand MMF wire
- T1 (phone, fax, router)
(IDF) - Individual Data Frame Room
(MDF) - Main Data Frame Room
K-20 Internet Service
Provider / Cloud
Star/Bus Hybrid Network
Designed By: Mark Simon

work great for limited small local area networks. The problem with bus networks is if one
computer or line does go down, they all go down and have multiple fault collisions dependent on
the number users present. They get more costly after time and the security is minimal at best.
The campus only uses the bus portion for the backbone and the more fluent traffic is run through
independent switching hubs from each building. This gives the star topology a chance to work
with the bus. The star system runs to each building using (proprofs.com, n.d.) multi-mode fiber
(MMF) 1000BaseSX, which has a distance of 500 meters. This is run out from the main data
facility (Elementary school) and to all the subsequent surrounding buildings. Distance of each
school is within 30 meters of each other. The two longest stretching areas are from the Junior
High to the transportation building and football field. These two facilities are also the max
distance for this particular MMF cabling. At each of the building the MMF optic cables are
patched into various switches. All of the buildings hold two or more 40 node switch/hubs. This
switch hubs span (proprofs.com, n.d.) Cat-5e and Cat6 to the individual nodes placed throughout
each independent building. Cat5e is used for regular computing and printers and Cat6 for Voice
over Internet Protocol (VoIP). Since the star and bus are now working hand-in-hand many
advantages come over disadvantages. It becomes more cost effective, is easier to trouble shoot
if one computer or section becomes faulty, the signals can be amplified from the switches, the
system can be expanded if it is needed, and the user can get faster flow response on his/her work.
As these components send the information, it needs to use certain protocols or instructions to
send and receive the data to the appropriate component or computer.
Methods of Access - 2.4
Older network protocols like “Token Ring” and “Local talk” were the most
popular network protocols into the middle of the 1990’s associated with the open systems

interconnect (OSI) model. They became old and antiquated as the hardware, and new protocols
had to be introduced to match the capability and speed of the new components being deployed.
The old models also implemented the carrier sense multiple access/collision detect (CMSD),
along with the two aforementioned protocols to alleviate some of the collision process from
occurring frequently. Developers knew something had to be done and developed the transfer
control protocol/internet protocol (TCP/IP) to address this issue. This protocol integrated
“physical” and “data link” layers together under what is called the “Ethernet”. Theses layers
monitor the hardware and wiring along the route including the hardware components. CMSA/CD
is still part of this newer structure. It still monitors line usage for each computer before sending
a packet. Once a packet is off this layer it is transferred to the network layer or the internet
protocol/exchange (IP and IPX) layer. This is where the logical address to your media access
control (MAC), or device, is layered if it is outbound traffic. It’s basically like being in the post
office. You address it, lick it, stick it and send it. But before it can be addressed, the packet must
go through the transport layer. Also known as the transport control protocol (TCP) and service
pack exchange (SPX) layer. The information you are sending is put into encapsulated packet bits
and headers and footers are placed at the end of each packet. Here again, it is like the post office
only you are breaking it down and packing it so it will fit into the box. Lastly, is the
“Application”, Presentation”, and “Session” layer. These three layers combine together and
virtually overlap each other when crossing the network and the Ethernet. Most of the protocols in
this session explain data, file, video, mail, web page, and addressing of files or addressing
assignment. Most notably are post office protocol (POP), simple mail transfer protocol (SMTP),
hypertext transfer protocol (HTTP), file transfer protocol (FTP), and Internet Message Access
Protocol (IMAP). These are just a couple of the many triple upper layer protocols. There are

many others and I could write a full book if I tried to put them all on here. This access method
manages to keep up with today’s standards of 1Gbit performance issues, but the protocols only
go so far. The individual LAN has to have enough adaptation to support that API and other
interfaces. (Fujitsu, Dec 2006, P.1-5)
Network Performance and Over site - 2.5
I was curious and decided to ask the campus administrator about the network
performance and monitoring. I also wanted to know what APIs were on the network and did this
aid in troubleshooting, planning and enhancing the overall network. Mr. Van Pelt laid out the
network in simple terms. (Van Pelt J., {P.I.}, 2014) The campus is interlinked through each of
the schools with 18 switches, 5 Wireless LANs, and is connected by either the (MMF) multi-
mode fiber optic or 1000BaseT/Cat-6 & CAT5e cable wiring. Each independent school on the
campus has 40, 60, or 80 node stack switches to attach Voice over IP (VoIP), computers, printers
or other service. The network is currently segmented into nine segmented areas. Each building
contains its own segment with each node running to stack switches in each of the IDF’s. The
network is monitored through certain hardware applications but ‘Spice Works” has been the best
for monitoring flow of this setup and due to the amount of present traffic and the need for more
service, the present setup is on the verge of an abundance of over collision prospects. To
alleviate this problem, the campus is looking into placing routers into each building to enhance
connectivity and transport while inhibiting the collision potential. The network is also monitored
by a IP Packet sniffing program, which watched all users of the network and can tell when
someone is conducting illicit sessions within the system that could be of risk to security.

Conclusion - 2.6
We looked at the premise of which network architecture should be utilized and examined
to be able to fully describe the full operational needs and provisions. This brought forward the
physical location and the physical topology to better inform the reader how it was set up and
viewable to the mind. Once the physical and logical topology was addressed, we approached the
notion of the advantages and disadvantages of the network. A bus topology and a star topology
in single service had advantages of efficient cost and extendibility. However the topologies also
show they are limited, have massive collision problems and have to be upgraded after short use.
It also has to integrate, not only the hardware point but the software and application interface to
run effectively. We looked at how the system presently runs in the transfer control
protocol/internet protocol format using many different protocols to ride piggy back to senders
and users. One protocol is not efficient to use on all aspects and therefore, the protocols extend
to mail, video, phones, and much more. We looked at the administrator’s role in this network for
monitoring and realizing potential problem areas and needed expansions based on certain
troubled areas utilizing network software. Some are deployed with maintenance software and at
times other companies build the software to better interface as the packaged software isn’t
adequate. This portion only shows the limited setup of what this network has the ability of
processing. The current supports many services but is the TCP/IP model it’s open source
interconnect model? Other models such as (UTF) universal transformation format could also be
in to TCP/IP. We’ll investigate.

Chapter - 3: Network ModelorStacks
Network Model Overview - 3.1
This section of this project takes a look at the different internet and network models and
their stack orientations to properly compile, manipulate and control the flow of information.
These models and/or protocols layers will then segment, prioritize, and execute the information
being sent from the sender to the receiver. After much research and analysis I have realized there
is a big expanse of involvement by many types of protocols running throughout the model stacks.
In the following segments I am going to look at the open systems interconnect (OSI) model,
break it apart and attach each sub-layer protocol to show how it really functions. When I first
started looking at this stacked layer model I was quite uncertain as to how it all tied together. I
guess it can be applied in this type of analogy. Imagine I was going to buy a model car that has
to be glued together. I purchase the model from a the local hobby store with the intent of
figuring out how to put it together so it looks like what is seen on the box. This is how I felt
when I was first looking at this model. So, now I have studied it, started to put the pisses
together, and now it looks kind of like what I’ve seen on the box. Once it is finished, now I get
to write an analogical report on its construction. Once this model is done, I get to put together
another model and follow the same steps I had conducted with the first model. This model is
called the transfer control protocol / internet protocol model (TCP/IP) suite. With the TCP/IP
model I will have to conduct the same process I will have done on the OSI Model. From what I
have seen, it will be pretty much be the same analogy of procedures that I will have used for
dissecting the OSI model. Another way of looking at it is like being on an assembly line at a
major auto maker. In order for the car to run properly, it must be assembled in sections in order
for it to be able to run on the road. Each vehicle starts with the frame. It’s run through the

engine installment and suspension portion. The car then has the body attached, but before its
attached the body has already gone through its own process of being painted and cured. Once
the body is attached the vehicle heads to a different section for electrical, then interior, and so on
until it’s complete. This is the same design of the network models or suites. The OSI suite is the
primary reference model and that is where we will start.
The Open Systems Interconnect OSI Reference Model - 3.2
The Open Systems Inter-connect was originally designed so it would be able to connect
computers and network systems all the way around the entire globe. Utilizing a seven layer
integrated model/suite to take data from one computer and send it to another computer. This
model is indeed a reference model for the very fact that not all components fit into all layers of
this model. The protocols are steps within this model to aid or assist in the process to actually
take the data and get it to its destination. None of the applications have spread spectrums to
encompass all layers. This was my thinking when I started. From my discussion paper I talked
about the history of both the OSI model and the TCP/IP model. I believe it is integral part and I
have placed it in the following paragraphs for the historical refreshment of the reader. Let’s take
a look.
Historyof (OSI) Model - 3.3
In the latter part of the 1970’s, two independent study groups decided it was time to make
a unified architectural format for the purposes of world connectivity over the internet. The
International Telegraph and Telephone Consultative Committee (CCITT) and the International
Standardization Organization (ISO). Both conducted independent studies to develop some sort of
internet language to communicate on the internet. Once the documentation was reviewed by

both parties, a combined realization was formed that the models were nearly parallel in
structured format. In 1983 both parties decided to combine this protocol language through one
single label, known now as the “OSI Reference Model”, or the OSI Protocol Suite. This suite
would be the established protocol suite for interconnect in all other protocols. The oddity of this
protocol was not meant to be just a reference model, but was intended as the industry standard by
which every internet communication would rely on for communications. Unfortunately, this
wasn’t to be the case for the OSI Suite. (Kozierok M., Sec-2/Sub Sec-2/p.1, 2005). Ultimately,
this suite was overtaken by the TCP/IP suite. The OSI suite has layers used within the TCP/IP
layers but the OSI suite wasn’t as functional. The OSI model is made up seven different layers
as seen below in figure 1-1.
OSI Layers Defined - 3.4
As a person looks at the diagram, one would think that the fist layer to be described
would be the “Application Layer”. In everything I have read about the models the authors tend
to start at the “Physical Layer” first. That leads me to believe that the diagram should be flipped
Figure 3-1 (Fujitsu, 2006)

and the layers numbered accordingly starting at the “Physical Layer” being number one. Of
course then I saw it in a different perspective as to how someone would look at a car depending
on whether you stand in front of the car or behind the car. At the back, the passenger side is on
the right, but when standing in the front of the car, the passenger side is on the left. So, it took
some thinking on that one but I figured it out. It’s a cyclic flow and the best place to start is in
the “Physical Layer”. Therefore, onto the first layer we will go with its description. These
layers are described in full OSI format without TCP/IP similarities. This will be conducted when
I explain the TCP/IP portion of this literature.
The Physical Layer 3.4.1
The function of the “Physical Layer” is described by some to be the concrete and mortar
of the network system. Others just describe it as the wire, connectors, routers, switches, bridges
and any other hardware, hooked into the network interface card, as the physical layer. It also is
part of the data-link layer. Some wouldn’t agree, but if we look a little deeper, it is realized that
the cable length is buried into the structural length format and degradation based in the Data-
Link layer. This layer is also responsible for signaling and various encoding operations to
transform data bits into electronic, frequency, or light pulse characters to be transmitted. It is
also lays out the bases for the topology design.
The Data-Link Layer – 3.4.2
This layer is primarily responsible for five areas. It conducts error detection and handling
through what is known as a cyclic redundancy check (CRC). This check ensures that the
receiving or intended computer get correctly assembled information. This layer is responsible
for addressing information being sent to the receiving computer or component. Every device on

the network has its own media access control (MAC) address that the data-link protocol utilizes
to ensure that the intended information can be shuttled to the appropriately intended address. The
DLL is further responsible for the final encapsulation of higher level messages that are being
sent onto the network. Finally, the data link layer (DLL) controls the functions required for the
connection and control of connections on the network from the logic link control (LLC) protocol.
The LLC is viewed as a sub layer of the data link layer, but the logic control interfaces with the
network protocol to ensure seamless connections of technologies that use the IEEE802.2 logic
link protocol. The logic link is basically hiding information in the data link layer so it doesn’t
disrupt other flows from other technologies on wireless. This allows these programs to fluidly
interact with the upper layers.
Network Layer – 3.4.3
This layer seems to be the big daddy of the carrier protocols. I would associate this with
the mail department that makes sure that a package is delivered to its intended owner no matter
what happens. This layer is the lowest one actually concerned about getting information from
one point to another. Weather it is on an interconnect network or it is on a remote network, it is
the network layers pride and responsibility to ensure the success of packet delivery. The network
layer confronts the issue of logical addressing unlike local addressing. Local addressing is an IP
address worked at the data link layer to send information to a physical device or agent. The
logical address is independent to only certain hardware and is unique across the total inter
network. Another task of the network protocol is responsibility for deciding the packet size
based on throughput. You can’t fit a baseball in a garden hose as would be the case. Therefore,
it’s the network protocols job to turn that baseball into a compressed one inch ball, or cut it into
little bits and get it through the garden hose. It performs the opposite procedure on the other end.

Data encapsulation is sometime referred to in this process. If the information is coming from
with a computer or device and is going to be sent, the network layer looks at the data, decides the
size, segments it, places the header address on it, and encapsulate it into data packet units
(DPUs). The final responsibilities of the network layer include error handling, diagnostics and
routing. The errors and diagnostics run within the aforementioned logical portion. It is within
this port of the network that error codes and diagnostics may be run on hardware and line
connectivity. The routing portion catches all packets in the network layer and decides where
each packet is addressed for and sends the information on its way up the pipe to the next layer.
The Transport Layer – 3.4.4
This layer encompasses responsibilities to both the upper level layers and the lower
layers. The transport layer acts as the official intersection police officer. It decides who is
allowed to go and when. In relation the transport layer keeps track of the multi-tasking going on
in the upper levels. When requests for packet delivery are sent to this layer, it’s the transport
layers job to ensure it gets going to the other end. It has to initially look at the request, see what
size it is, figure whether it can go as is, or if it needs to be broken into manageable packet size,
and send it to the lower stacks for encapsulation and so on. The network layer also provides
services for the connection orientated and connectionless services. The network layer sends
return information to the sender if packets have been damaged or lost. On the other hand the
network layer also controls the user datagram protocol (UDP). This protocol sends information
“as is” with no error checking. Protocols using this function are usually, simple network transfer
protocol (SNTP), dynamic name service (DNS), dynamic host control protocol (DHCP), and
routing information protocol. Of all the layers I have seen the network layer is the pivoting
factor for all the layers to work. Believe it or not the network layer also addresses individual

software programs, conducts multiplexing and duplexing, and complete, monitor, and disengage
when needed. The network layer is truly an impressive layer in its own right.
The SessionLayer -3.4.5
In this layer all the addressing, headers and footers, and all other packet encapsulations
have been removed. This layer mainly deals with the software applications issues and the
longevity of their interface connections. In relation, a person could theorize it as making a phone
call to another person and staying on the phone for a while to talk. Hence, some would call this a
gab session. The session is characterized in the layer as the time used to connect on program to
the other for the duration of the process being performed. The programs inter relating with each
other are commonly called application program interfaces (APIs). The job of these application
program interfaces (API’s) is to set up, manage, and disengage dialogs or sessions. In laymen’s
terms, it is represented as a user dialoging on an application that connects to the network.
Ok…simple enough.
The Presentation Layer – 3.4.6
The presentation layer is pretty much specific in its responsibilities. It presents data from
one application to the other. In some instance the presentation layer may have to translate the
data received. The layer also has optional functions of compression and data encryption under
alternative responsibilities. You could almost call it the ghost protocol layer as most of the
function that are in this portion may also be done in the application layer.
The Application Layer – 3.4.7
This layer deals with the fine art of actual internet programs the users are utilizing to send
message, watch video, make phone calls, and diagnose issues and everything user related within

and on the network. This will include the hypertext markup language (HTML), hypertext
transfer protocol (HTTP), post office protocol (POP), simple mail transfer protocol (SMTP) and
various other internet related application protocols. All in all the seven layers of the OSI model
slide and interrelate with each other in common and uncommon ways (Kozierok, M, Sec-2 Sub
Sec 5, p.1-13, 2005). It has been a long investigation into the OSI model and what it really
envelopes, but let’s take a look now at the TCP/IP model stack and see how it relates to the OSI
reference model.
TCP/IP Internet Suite 3.5 (Fujitsu, p.p. 1-12, 2006)
TCP/IP Layers Overview 3.5.1
The transfer control protocol, as everyone knows in the computer world, operates all the
information on the internet, creating a well streamlined, flying network running at impeccable
speeds. As we can see here, the designed architecture of the TCP/IP suite removes the
presentation and the session layer, and then conducts all the upper layer activity within the
application layer. This envelopes the procedure of taking the user program (application),
turning it into binary code with encryption, compression and encoding (presentation), and then
addressing it for travel to and from computers through packet sequencing (session). (Fujitsu,
2006) Figure 3-2 (Fujitsu, p. 1-4, 2006)

The lower three levels define the operations and protocols (to include the transport layer,
internet, and Network access layer), define the means of transport, utilizing the data link, and the
network access to encapsulate and transport the various forms of information to the suggested
receiver. There are now sub-layer protocols built in to these area and the upper levels to
eliminate the stringent style of the OSI model. I will look at some of these within each area. I
also think a little history for TCP/IP is needed to address why this suite won out the OSI model.
History of TCP/IP 3.5.2
While the OSI model was being achieved other alternative approaches were also being
researched and reviewed during this time. The military’s Advanced Research Projects Agency
(ARPA) was developing an internet communications protocol for transmission of classified
information across its own systems. In 1973 they began research on the Transmission Control
Program (TCP). This didn’t have the internet protocol attached to it at this point as this was
research of the Transport Control Protocol/ Internet Protocol in its infant stage. They found the
TCP just wasn’t doing what they needed to transport the needed information. The single
program was trying to accomplish too much. In March of 1977 one of the key engineers of the
modern day internet related that layer 3 (Network) and layer 4 (Transport) needed to be
separated in order to accomplish a higher fluency of data transmissions. In 1978 they were
officially broken down into the network layers (internet protocol / IP) and the transport upper
level layers as seen in figure 3-2 above. (Kozierok, M, Sec-2 Sub. Sec. 5, p.1-13, 2005)

The TCP/IP Suite Network Example 3.6
The Application Layer 3.6.1
In this portion I am going to take a look at the TCP/IP model in its different
layers. I am starting at the uppermost layer, as it seems to be a little simpler at this stage and we
will work our way down the stack. The “Application Layer” is reference at the top of the stack it
also incorporates the “Presentation” and “Session” layers into its domain. Gone is the encryption
and translation of the presentation. The session layer, which opens a port, maintains connectivity
and initiates the end of session protocol are also all gone. These are all now incorporated into
the application layer. The application layer now receives information from the user interface
application and sends it directly to the network layer. In the OSI model the network layer was
below the transport layer. With this, one can analyze that the application is now jumping three
layers. These applications have a couple of little secrets. They are considered part of the
application layer domain and have certain protocols already written into them to bypass the
presentation, session, and transport layers. They send information directly to the intended
receiver on the network. In a way the analogy might be seen as the protocols of the layers have
been handed off to the individual programs so they can speak for themselves. Those that speak
for themselves include Simple Mail Transfer Protocol (SMTP), Post Office Protocol Version 3
(POP3), Internet Message Access Protocol (IMAP), Hypertext Transfer Protocol (HTTP) and a
few other programs protocols controlled programs. We often see these protocols staring straight
at us when we configure mail, send a message on a Facebook or Twitter, or even go surf the web.
The Transport Layer 3.6.2
The next layer in the TCP/IP suite deals with the “Transport Layer”. The transport layer
has been slimmed down in some ways and strengthened in other ways. Primarily, it operates two

transport entities with its protocol. These are called the Transfer control protocol (TCP) and the
unit datagram protocol (UDP). The UDP is considered an unreliable source of data transmission
and rightly so. This protocol will take a predefined data packet from the application layer,
encapsulate with the minimum packet structure and pipe the information right to the lower layers
without error checking and correction. The data pack may resemble what is seen below in figure
3-3.
1 15 16 31
Source Port -The sending
application. (Optional field)
Destination Port -The target
application at the receiving end.
Length -The length of the entire
packet.
Checksum - basic error correction on
packet. (Optional Field)
Data – Self explanatory
The transport layer is also responsible for maintaining the session layer of the OSI model over
the internet. Interestingly enough, this same session operation is supposedly sub-layered into
some of the applications of the application layer portion. Who knew? The other primary core
protocol running within the transport layer is known as the “Transport Control Protocol” (TCP).
The TCP protocol has its own duties to attend to. TCP ensures that once a connection is made
there will be no disconnects until TCP says so. This makes TCP more reliable when sending
time sensitive and precious information. There are a few other reliability factors that TCP
conducts that the UDP protocol could care less about. TCP actively monitors the throttle control
of packets being sent or received. It monitors the line for defective or duplicated packets and
discards them as needed. Then it sends feedback messages asking for replacement of damaged
packages. Finally, the TCP is responsible for making sure the packets are error free and orderly
upon sending and receiving. The Transport Protocol layer definitely has simpler. Below is a
diagram of a basic TCP packet Figure 3-4.

Programs to most likely use the layers benefits of transfer control protocol include Secure Shell
(SSH), Simple Mail Transfer Protocol (SMTP), Interactive Mail Access Protocol (IMAP), and
other web based programs relying on data reliability.
The Internet Layer 3.6.3
This layer coincides with the layer 3 network layer established within the OSI model.
Once it’s analyzed a person may see that this layer of the TCP/IP practically mirrors the
responsibilities of the network layer in the OSI model reference. Both layers are involved in the
reliability of packet content from host to receiver. They both monitor routing, switching, and
information flow problems. They both translate physical addresses from logical addresses when
needed. The internet layer also predicates the ability for addressing through classful and,
classless addressing. Classful addressing is segmented into three sections. The IP Class, the host,
and the network number. Because of the increase in needed Ip addresses there is a need for the
addressing to go classless. At present the classful protocol is rigid and can only handle so many
addresses within its parameters. The classless protocol, dubbed the classless internet domain
routing (CDIR), is designed to go to infinity and beyond under its new structural protocol design.
Figure 3-4, (Fujitsu p. 1-12, 2006)

It isn’t limited by the 32 bit structure any more. Instead, the CDIR still uses the IP protocol of the
classful but it has an additional 13 to 27 extra bits of information to further direct the routing to
specific points. One other note of the CDIR is its use in private networks. The classless scheme
would allow private networks to be encapsulated within an internet address from the router and
placed on the internet for streaming. Finally, we know that his portion is being run through the
almighty router. The router is also known for the gateway to the internet. I guess that is why one
of its protocols is the Interior Gateway Routing Protocol (IGRP). The most important portion
associated with the internet protocol is being able to translate information with the Network
access layer. This is where the address resolution protocol (ARP) steps in. This protocol is
buried in the routers internal cache and represents all addresses within its network. If an address
comes in the router doesn’t recognize, the router will send out an all-points bulletin in order to
find the illusive computer. If the illusive computer recognizes the address it will send its media
access code (MAC) back to the router, tell the router where it is, so the information can be sent.
Thus, the problem is solved.
The Network Access Layer 3.6.4
The network layer runs both the data-link and physical layers. This layer defines the
instruction for interfacing with the network hardware and grabbing a hold of the transmission
information packets. The network layer primarily has two sub-layers orientated to its design. One
is the media access control (MAC) protocol and the other is the physical control characterized by
the hardware component itself. Namely, the network interface card (NIC) or Ethernet card. Both
these sub-layers work hand-in hand. The MAC preps the data for sending and the Physical
protocol encodes the data and physically sends it to the recipient at the other end of the media

expanse. The last portion of the network layer uses actual protocols to physically send the
information on the media lines. I could go over each one independently but the amount of
information dedicated to each of the access protocols is extremely in depth and I doubt my
fingers could type that much. Therefore, I will just name them and realize these protocols
conduct the actual trafficking across the open internet media. There are Point-to-Point Protocol
(PPP), Ethernet, Point-to-Point over Ethernet (PPoE), Wireless Fidelity (Wi-Fi), Worldwide
Interoperability for Microwave Access (WiMAX), Frame Relay, and Asynchronous Transfer
Mode (ATM). All these network access protocols influence the transmission of information in
some way through packet sizing, throughput, disassembly/reassembly and more. The bottom
line is they all are used at the network access layer to transmit and receive data across the
physical layer just like in the OSI model.
Layer Intercommunications 3.7
We have discussed the OSI and TCP/IP model and how each layer functions in its
required responsibility to send and receive information. But how does each layer communicate
with the next layer to ensure proper dissemination of the issued command at the application
layer. It’s really quite simple in its structure. Once the user issues the command to the
application layer this quite literally sets off a chain of events between layers. As it goes to the
stack pre-information has already flown to the receiver that it will be receiving a packet. This
flows through the application stack to the transport stack where the protocol here says “thanks
for the packet” and starts to segmentation. At this point the packet has a choice of unit datagram
protocol (UDP) or transfer control protocol (TCP) packeting. This is still in the application,
process and Session layers. They are working together at this point. Now the transport protocol
takes the hand-off from the upper three layers. The transfer control protocol looks at the packet

and sees if it is TCP or UDP. If it is UDP, it’s off to the races and next layer but if it is TCP, the
transfer protocol then goes through its process. It conducts a three-way hand shake with the
receiver, gets an acknowledgement, and synchronizes for packet acknowledgement. The TCP
finally sends it to the internet protocol (IP) layer. The IP layer then formulates both types into
the IP datagrams. Here the IP addresses, further header and footer constructions, and the
sequencing rebuild are all executed in the layer. This is so the receiving end can adjust incase
the packet is too big for delivery. Once the transport layer is done chewing the packet all up for
delivery, it is sent to the data-link layer where another header is attached indicating cyclic
redundancy for the packet. The data-link checks the packet for errors as it travels over the
network media. Once this is conducted the transport layer wings it over to the physical layer.
The physical layer grabs the packet and flies the packet to the sender with the appropriate
information and addressing. From here, the layer protocol is reversed and sent to the receiver.
Below is an example of the process.
Figure 3-5, (Oracle, Vol.3, Ch. 4, Sec 2, p.1)

Conclusion 3.8
My review of both models showed a sequence of individual, similar and variant contrasts.
The OSI model appears as a more structured and fixed set of protocols to deliver information
from one point to the other. These layers do interconnect with each other in performing some
pre-note operations that provides seamless communication for quick delivery. The same came
be said for the TCP/IP model but this model seems to have a more flexible set of conditional
factors and protocols to manipulate and transfer data just as efficiently. However, the areas that
have taken over some of the responsibilities are also structured with sub-layers to assist within
the enhanced layer process. AS I completed this and realized the total function of the model
references, I realized that the amount of operation going on in a split second from all the
protocols initiating and completing their assigned functions must be like being in a star ship
going at warp 20 to get to its destination. To imagine all those packets being check, analyzed,
error corrected, encapsulated, sent, un-encapsulated, headers ripped, computer found, application
presented to user, in a split milli-second is mind blowing. This has all been thought up and
deployed in the last 40 years and each day brings more with protocols and models. My question
is where will we be in another 40 years, and will faster models be dumping terra bytes per
second instead of Gigabytes? Enquiring minds want to know.

Chapter - 4: Network Protocols
Introduction 4.1
As we have already learned throughout this journal, the class, and individual research;
network protocols are a specified digital language that stipulates what rules go into effect when
passing information back and forth across the net, to and from computer to computer. In my
case scenario of the local school I am going to look at all the protocols utilized for sending
information from one computer to another and how they also have to use the extranet to gather
certain information. Oh yes, I found out recently that the schools has a couple of off base sites
controlling certain information for the schools. We will look at this as well. I will be looking at
how the application protocols are used for using the hardware components within the schools. I
talked about the hardware back in chapter two as being Cisco Systems, which was pretty much
the backbone of the schools architecture. I also want to see how the phone system is integrated
into the network using a virtual local area network 99 within its spectrum. What protocols might
be needed to run this setup? When I conducted my interview it was revealed that there are four
primary protocols being utilized throughout the network structure. They are the transfer control
protocol /internet protocol (TCP/IP), dynamic host control protocol (DHCP), Voice over internet
protocol / virtual local area network 99 (VoIP/VLAN99), and software defined networking
(SDN) network protocols. We’ll break each one down through the schools structure and define
its responsibilities with the systems. On to each individual protocol to see what each one
actually does.

Individual Protocol Responsibilities 4.2
TCP/IP in Campus Network 4.2.1
As was discussed in chapter 3 of the journal, the TCP/IP protocol is basically the heavy
duty backbone for sending information from user to receiver. The schools main protocols all run
across the TCP/IP Suite. In the following graph we will see of the protocols that run through the
protocol stack. We will also use the OSI model as a reference within this stack.
OSI Stack TCP/IP Stack
Layer - 7 / Application Application / Session
Transport
FTP
File
Trans
Protocol
SMTP
Simple
mail
transfer
protocol
DNS
Dynamic
Naming
Service
SNMP
Simple
network
Mgmt.
Protocol
RTP
Real
Time
Protocol
Layer - 6 / Presentation
Layer - 5 / Session
Layer - 4 / Transport Transport / Host-to-Host UDP (VoIP) TCP
Layer - 3 / Network Internet
______________________
Network Interface Layer
IGMP ICMP
Layer - 2 / Data Link IP/IPX
ARP
Layer - 1 / Physical Ethernet Token
Ring
Frame
Relay
ATM
Although I’m just showing some of the more major portions related to everyday operations of
the network there is always more that seems to pop up. Now, let’s see how each of these
protocols interacts with each of the components within the network. As was described in
Chapter 2, this system has a perimeter firewall, VoIP router switch controller, surveillance
switch router controller, 17 stop and go switch controller panels (48 socket), an 8 stack server, 7
virtual private network wireless switch controllers, 154 IP phones, and 254 nodes for computer
attachments. I think there is a partridge and a pair tree there too, but I am not sure where.

Switch
Router
The Router 4.2.2
This piece of equipment is hooked directly to the network interface layer known as the
data-link and physical layer in the OSI model. The particular router running at the school is a
Cisco multi-vector router. It uses a proprietary protocol known as the internet group routing
protocol (IGRP). This protocol sends a band message across the network every 90 seconds and
can tell if the network has changed due to this all-band message. It integrates with the internet
protocol (IP), internet packet exchange (IPX), and connectionless network system (CLNS) to
allow the exchange of packets over the network, wireless network and internet. With these
protocols, the router monitors the direction of packets to their intended addresses through the use
of four other protocols. Dynamic host control protocol (DHCP), static routing, unit datagram
protocol (UDP) and transfer control protocol. Static routing is utilized for the servers, printers
and the component controllers within the school. Since these items are always working and never
moved they are allowed the static addresses The DHCP is utilized for the phones, computers and
wireless connection devices such as phones, laptops and tablets. With DHCP the agent
component can be assigned an address when it is signed in. Routers also use the transport layer
to communicate with other routers and switches to set up their directional sending and receiving
tables. So what does the switch really do?
The Multi-Layer Switch 4.2.3
This components’ primary responsibility within the school is to send packets from one
point to another within the network. The multi-layer switch primarily does all of its functions
between the internet and transport layers using various protocols at various layers. The
switching components may utilize packet content anywhere from the internet layer all the way up

to the application layer. These switches may be known as web switches, content switches,
application switches, or content service switches. These switches, even though they are different
titled do basically the same thing. They equalize the load being sent across the media transport.
Everything form hypertext threading protocol to destination network translation to network
content delivery is has a switching protocol attached to it. The switches have their fingers in
almost every aspect of the internet layer to the application layer.
The Firewall 4.2.4
The local school utilizes the Cisco firewall as its line of defense to the internet world.
This firewall in integrated with what is called a stateful packet inspection (SPI) protocol. The
firewall analyzes the packet all the way into the application layer information. Generally, the
firewall shakes hands all the way to the network layer providing continuous information of
packets received. However, if it finds TCP or UDP packets that are not in sequence, out of
cycle, have different headers, or doesn’t match the network addressing translation (NAT), the
firewall will shoot off a message to the application layer of its finding. The application layer will
respond just as quick letting the firewall know to discard the packet if it’s not part of the
sequence or has the wrong header or footer. (Stoddard, A., 2012) The firewall also has methods
of access for the wireless side. (Wireless Controller)
Wireless nodes patch in through Lightweight Access Point Protocol (LWAPP)
Controllers. These access point controllers relay the input information to the Wireless LAN
Controllers (WLCs) positioned before the firewall in the school. These controllers use the
wireless protected access / pre-shared key-2 (WPA/PSK2) security encryption; before allowing
the user to access through the access point, and perimeter firewall. The wireless feature runs the

same layer gambit as the regular firewall. (Van Pelt J. 08 Jan, 2014). From these components
information is now switched the servers.
The Client / Servers 4.2.5
The campus has eight servers located in the basement of the elementary school. These
servers are all Cisco based and keep data on hand for four areas. The library has one server
dedicated; the student information is dedicated to another server, one is dedicated to security of
the firewall, individual nodes and wireless and the last five are dedicated to data retention and
delivery of the campus. All information runs from the servers to individual stations using all
layers of the TCP/IP stack. Students have computer classes and have to save information, go on
the internet and even construct systems and partitions on the computers. The teachers and
administrative personnel are also using the servers for grades, e-books, music and a myriad of
other documentation that is saved on the servers. They also utilize intranet mail, use the web
from research and can send quick notes to each other via the network. This activity among all
the alumni, teachers, and faculty staff can pretty much narrow down the fact that the servers run
the whole gambit of the network stack issuing UDP and TCP packets, completing check sums,
encapsulating and using every protocol within every stack. It even can goes to the internet as the
library is web based and to get into the servers form the web there is a demilitarized zone (DMZ)
built in so the students may access the library from home. They must first access the school web
site, which is clouded through the google school account. This site then administers a password
protocol before allowing access to school library servers. I asked John Van Pelt if this was a
form of extranet and he said “yes but no”. (Van Pelt, J. 2014). Apparently it runs to the server
through the internet and is on an external entry but the access method would be the same as the

kids accessing the network if they were sitting in the class rooms. All I know is the servers can
be on the internet with packets.
VoIP Controller 4.2.6
The voice over internet protocol (VoIP) system is backboned into the regular system on
the school campus. It connects directly into the switches inside the firewall areas at the
elementary school. From there the system is patched into the needed areas where phones go but
is plugged into the same RJ-45 plugs as the regular Cat 5e cables. The difference here is that the
cable is a Cat-6 with a twisted 8 pair cable with one set being a little thicker for power
connectivity. The VoIP system runs on a sub-layer of the network to keep it from colliding with
regular transmissions from computers and printers on the network. When someone makes a call
through this system the VoIP phone takes the callers voice and cuts it into packets, which are
encapsulated into unit datagram protocol packets (UDP). This protocol runs at the transport
layer with the real time protocol (RTP) for VoIP. The RT protocol is replacing transfer control
protocol (TCP) in this area. Once the packet is ready, it is sent to the intended called on the other
line, torn down, re-sequenced, and turned back into analog sound. This system can be used
within the network or can go out onto the internet via internet protocol and connect to regular
analog phones. (Balchunas A., 2007) There are many more settings and run protocols to this
system but this is the basic configuration. Within the network it will also use the peer-to-peer
protocol over Ethernet (PPPoE) for its connection. When the phones are used for outside calls
the plain old telephone system (POTS) is utilized.

Computers 4.2.7
As we all know the computer is the user interface when working on the network. Its how
we are able to attain the information needed to prepare reports, send emails, make power points,
watch videos, listen to music and so on. From our study in the TCP/IP stacks we also know that
the computer is where the application layer, presentation layer, session layer all start to make the
issuances creating orders to make UDP and TCP packets, for transport and shooting it down to
the transport layer for request and delivery. We also know that the application layer is
responsible for formats and certain encryptions.
Management Agents for the Network 4.3
The network uses a multitude of programs and protocols to notify the administrator of
problems occurring within and around the network. The primary program utilized by the
network management is the Windows Based Management System (WBMS). This program runs
off of a DCOM (Distributed Component Object Model) and the hypertext transfer protocol
(HTTP) to issue commands to the individual components, set parameters, permissions and
completes necessary diagnostics when needed. It is known as an active directory within the
network. The WBMS covers almost every component of the network. (Snover J., 2012)
However, it doesn’t work with management of daily software and network operational user
issues. The school administrator uses “Spice Works” as a network management tool to monitor
the network, find trouble spots, and actually can see when anyone is doing something they are
not supposed to be doing while working on the network. It can also lock out different sites
using a hostile environments word base typically associated with pirating, malicious software
distribution and vulgar sites. It is a very powerful program and is HTTP user based. Everything

is run through internet explorer. This program was devised by two IT engineers to help IT pros
manage networks with ease. It also has life cycle requirements set on every piece of equipment,
can schedule trouble tickets and has the whole gambit at your fingertips for working the network.
I was amazed when I saw it and tried it in my own home. It works to the maximum expectations.
The administrator’s last tool in his arsenal is a program called Net-Scan. This tool has the ability
to watch every IP address being utilized across the network. I also use this tool in my own
home to watch for dubious net jumpers onto my WLAN. The school uses it in case they get a
student who attempts a rogue IP jump onto the web to those naughty places where students
should not be going. This is a windows application based program with strong IP characteristics
for monitoring illicit activity. We would hope this would help in keeping the system up to date
and keeping it locked down but there are still security issues past what they have in the arsenal.
Security Concerns 4.4
Even though Windows Operating Systems purport the news that the operating system is
getting tighter, hackers are still trying their best to use tactics like distributed denial of service
(DDoS), and password cracks to gain access to the network. Kids want to change grades or do
some damage to this system, if possible. It has been noted that the system has a bad tendency of
scripting system logs when they shouldn’t be occurring. These logs have the potential of being
read by system users, savvy enough to understand their potential for harm. The network
management is currently trying to find ways to limit this scope of information, the computers can
publish on the network, through stronger net management protocols, but the potential for script
busters still exists. Programs like Java are still wreaking havoc on the overall stability of the
system due to improper scripting of some web based protocols using this function. Java is a
needed application to run certain items like windows OS media on the web, but the java platform

continues to open holes for potential hackers to open back doors within the system. Application
updates are another needed source to help repair the ailing security of this network. The school
administrator has diligently been making efforts to correct all the antiquated software from the
system but relays it will take a couple more years to fully update the whole network to full
operational security status with needed software programming. Further, some new applications
are being deployed and recognized as incapable of integrating with proper security barriers after
deployment. This is leaving the network with possible back door opportunities and attacks from
hackers.
Conclusion 4.5
The scenario network comes with many protocols to run a given network. They are forever
interconnecting to ensure expedient response of information from and to the user. Without these
protocols each component would be a brick hooked to a copper cable doing nothing more than
collecting lint. Every second these components run they make the users life easier. Luckily
there is one individual who is continually watching this orchestration of 1’and 0s as they zip
along the media lines and through the components. The network manager has an avid and highly
responsible job and needs the tools to keep the network running like a well-oiled machine. If
they don’t have these resources, it would be like heavy traffic driving at high rates of speed, with
no signals to manage the flow. Soon there would be collisions and chaos. The manager of the
network is the flow control manager using the tools necessary to keep the traffic flowing
smoothly. It’s not without the downtime due to security and mechanical deficiencies. The
network is always in needs repair and reinforcement of security. We will continually have to
look for ways to shore up the network to keep it from prying eyes and devious minds. Weather it

is with password protection, firewalls, or software and hardware upgrades. The cost of these is
far less expensive than the damage of a lone hacker can cause.
Security is an important step in
keeping the network running. If
you, as the manager, don’t
diligently stay on it, this little
green guy is bound to be
knocking at YOUR back door.
They multiply, given very small
amounts of time and are hard to
get rid of. Once in, they are
ferocious eaters of data and party
animals of destruction and theft.
If you should see one of these
slimy creatures, call you nearest
IT Professional for immediate
extermination measures.
WE TAKE NO PRISONERS!!!
Designed by: Mark Simon

Chapter - 5: Network Security
Introduction 5.1
As a network administrator, many tasks have to be completed within the given day, when
running and monitoring the network system. Weather the individual is running a home network
or an enterprise network; it can appear like there is no end to the continual barrage of tasks that
can pop up. A daily task that is paramount is the performance of keeping the network system
soundly secure is security itself. If the network system is valuable enough it its information, has
confidential information, or new developmental research data, there are potentials for damage to
the system from all types of hacker activities. Through this section we will be looking at the
ways that hardware, software, and deliberate mistakes and errors caused by users that can cause
potential and actual penetrations and damage to a network system. What the possible damages
can be, if these types of situations are permissible in their occurrence, and the administrator’s
response in having to initiate repairs to the networks. I know as long as I have been working on
computers there never seems to be a day that I have not dealt with some sort of malware
attacking someone’s system, someone attempting to put some sort of marketing spyware onto my
own personal computer, or someone getting a hijacker packet on their computer and the system
having to be rebuilt due to these factors. I want to look at the biggest culprits of computer
espionage and damage. The big three are human knowledge deficiencies, viruses and spybots,
and updating the systems.
Cyber Attack Awareness 5.2
All too often I would see people not paying attention to what they are doing with their
work computers when I was in the military. After a while, when computers became a major part

of everyday mission essentials, the fact became well known that the military had to start training
personnel on the proper use and handling of information on the government network. This
introduced computer security (COMPUSEC) and what they were required to do to secure that
classified information under information security (INFOSEC). My daily job was in security and I
was in the training section. Because I had a knack for computers I was gladly volunteered to
become the trainer for these two areas. Most people had no idea what they were not allowed to
do when using these components. Most thought computers were an open play store to do
everything on. They thought they could shop on-line, look at their personnel e-mail accounts,
down load games and music, and let others use their desk to work on the computer when they
were logged on. Some even thought it was all right to make simple passwords like (1, 2, 3, and
4). What they didn’t realize was this was all was giving infiltrators the opportunity for
introducing malware of all types onto the Federal system known as the Non-classified internet
protocol routing net (NIPRNET). Some started to wonder why their computers were running
slow and then why a whole squadron had computers doing slow responses and files were being
altered or deleted. This was all because someone thought it was no big deal to open an e-mail on
their personnel site instead of using the designated on-site server email program. After this
happened, the classes commenced, with everyone getting knowledge overload. Everyone
learned about e-mails not being allowed, unauthorized media not being authorized, building
effective passwords, not downloading games and music from authorized site, and a whole
myriad of other no-no’s on network systems. People’s mouths were swinging like an open gate
when they found that they were doing the damage to the system. Some even got judicial
punishment for their shenanigans. The bottom line in this area is before a person is allowed onto
your network; ensure they know the dos and don’ts of computer security. In addition, a

disgruntled user can cripple a whole network faster than any hacker, by virtue of their internal
position. If anyone on the network notices someone with drinking problems, financial problems,
extremely curious to sensitive information, or a dislike for a company, in any way; their
privileges should be revoked until investigations are done to find out their status. These are the
indicators I learned years ago when teaching this course. The best practice for proper network
system functions by students, employees, and users is to ensure proper education BEFORE they
get behind the screen. It costs millions each year due to the naivety of personnel now knowing
proper security standards for file protection, e-mail responsibilities, and web browsing and so on.
It costs much less to train them before making sure they are authorized and handed a password to
start their tasks. What else can wreak havoc on a system? I would say the number 2 spot should
go to malware.
Malware 5.3
Besides human recklessness on computers, malware can be a crippling factor on the
performance and daily operation of a network. Malware is basically malicious software
programs designed to inflict damage and other unwanted actions on a computer or network
utilizing viruses, Trojans, worms, packet viruses, hi-jackers, and spyware. Plain viruses can be
delivered through an infected media source including a thumb drive, compact disk, or e-mail. It
also comes from social media sites like Facebook. My number one reason for having to
reconfigure computers is because people just love to play those games from Facebook. They
don’t realize that half those games are infected to the hilt with malware. The virus attaches to any
file, hops over to your system, than deletes individual files and destroys directory information.

Spyware can be loaded from an innocent program. At least, this is how they try to find
their way to my computer most of the time. I remember installing “Real Player” and then
finding out my system was starting to open a port and it didn’t even go to a Real Networks
website. There was no reason it should want to be accessing the internet in the first place. I
found it had an embedded spybot and was attempting to send information about my system and
my web activities to a marketing server. Luckily, I was not putting personal information on at
the time, or it would have scalped that too. All too often software vendors allow marketing
hounds to attach spyware to vendor programs. I have seen it on Adobe, Chrome, and even Java
RTE. At least they are not as sneaky as the next little piece of malware.
Trojans are the sneaky viruses of the computer bug world. These little buggers come in
as a form of legitimate software or file. Once in they expand, they make a back door to the
system for a hacker to enter by and gather information. They can also cause damage the same
way a virus can. Even worse, if these two are placed into the packet or blended threat they tend
to do twice the damage as before. Now, you add a hi-jacker to the packet and talk about a
volatile combination. There was a packet virus going around with this very nasty FBI virus on
board. The packet would hi-jack the computer, cut a back door, and then lay in a trip switch if
$400.00 wasn’t sent to a PO Box in Haiti. The packet virus ended up killing five customer’s
computers anyhow. Come to find out, there was a built-in kill timer within the packet. These
hackers had no intention of letting the victim’s computer survive. Even after they said they
would pay the money to the extortionists. The packet stripped the operating system activation
keys right off their systems.
The worm is a virus designed to replicate and flourish. It doesn’t care what it attaches to
as long as it can get from one place or another. Its main programed belief is “I will survive and

eat, get there and survive for another computer”. I have had quite a few of these worms on
customer’s computers and they had replicated all the space on gigabyte size hard drives, with no
room left. The customers couldn’t understand why their computers were telling them they had
no memory left. After I was able to get access to the temp files I found billions of temp files
with nothing in them except some little script. (webopedia.com, Jan 2104) What was funny
about almost every one of these computers was that absolutely none of them had appropriate
firewalls or security software to impede the progression of any of these malwares. Surprisingly,
there is something called Microsoft Security Essentials on the internet and is freely accessible for
any computer user to have and operate. This program is not the best at getting most malware but
it is efficient enough to keep out the highly noted ones. With this, it brings up another thought
and that is, when to update a computer.
Computer Updates 5.4
This simple little task is a big problem in a lot of single computers and computers on the
networks. Computers run at top proficiency when all the right software is applied to the
computers and network infrastructure. At times it might be a program requesting an update and
at other times it might be that a driver for a specific piece of hardware, that is out of date due to
irregularities in script, or to synchronize with some other piece of hardware. All too often some
administrators and individual users totally forget to do this operation or don’t even realize they
were supposed to do it in the first place. There are consequences to these actions. Weather it is a
network or a home computer, the system will start to see a leg in performance, the screens start
flickering, or the computers just lock up because they just don’t have the software it takes to
complete the operations. It is also an invitation, because updated security software hasn’t been
installed for potential threats from malware agents to step up and start knocking at the back door.

After I get done working on a reconfigured computer, I make a system image, which is saved to
a backup thumb drive and then finish this backup with a system recovery disk. This is a sure fire
way to ensure the individual system is protected. Then I sit down with the customer and go over
the importance of updates, how to configure auto updates and taking time to show them how to
put files to external storage devices. I don’t know how much information has been lost due to
these types of operations, but when the damage is done, it is done. Customers lose oodles of data
due to not properly backing up their priceless life memories. To a hacker, it is funnier than all
get out, but I would hate to see what my customers would do if they ever caught one those folks.
I’ve seen entire photo albums, important family papers and entire music volumes wiped out due
to improper storage of their precious memories. Then I get these puppy dog eyes and the words
“Can’t you get it back” emitting from their lips. I think we all know the response to that
comment. I also take some time with the customer to go over the importance of having their
patches done on their digital subscriber line (DSL) box. They don’t even realize that little box is
a router and it also has a firewall built into its infrastructure. This is where they realize that a
firewall is in place and that they can actually use it as a layered affect to thwart suspicious
information. As a volunteer at the school, I am always helping Jon to ghost and reconfigure
computers for the class rooms. Most of the time the updates are done automatically through the
network servers and time initiated batch files that are in place in the office. If a new piece of
software is brought in, it’s our responsibility to make sure it is deployed and working effectively
throughout the campus. It is first run in the IT office in a virtual lab environment to ensure its
compliance with other component software and hardware technologies. Once verified, the
security software is deployed to the regular network. The school administrator is always
conducting diagnostics on the individual pieces of equipment. This is due to extensive collisions

on the network. This causes performance issues when this occurs. By gathering this data we
have been able to ascertain the problematic areas. We have learned that each school needs its
own sub-layer network with independent routers to limit collisions. This should help enhance
effectiveness of the overall network traffic. It also helps to increase the layered security affect as
the increase of routers includes more checks on stray packets. If it is malware orientated it will
be chocked at these points. In the last couple of years the system has been massively upgraded
but still has a ways to go before it is to tip top proficiency. Along with the sub-layers a firewall
will be introduced to each of these layers increasing the defense-in-depth approach. That is a
term we used in the military when setting up posts or base installations from terrorist and enemy
activities. Finally, security suite software is deployed to each individual user component. With
that much wall breaking and sniffing, I doubt if any dubious script kiddies and hackers are going
to try any hacking of the school campus anytime soon.
Conclusion 5.5
We have learned what malware is described as. Any software or script, which can
damage hardware or software and leave a network disabled or damaged. Malware comes in
viruses, spybots, packets, Trojans and various other designs. Ultimately, it is the users
responsibility to preserve the safety and security of all the information that is being transmitted
across the network, World Wide Web, and their personnel desk top too. If not properly trained,
the user can do more damage than a hacker could, by virtue of their position and lack of proper
knowledge in operating the systems. They need to know what can and can’t be placed on a
computer systems and networks. Music, games and inappropriate media can bring in malware
without ever knowing it was on their personnel media. Finally, the importance of updates and

security ware are the final steps in keeping a network secure. Without these, the network and
home system components are dead in the water or are running at drag-bag performance.
Chapter - 6: Network Management
Introduction 6.1
Now that the network has an architectural design, there is a logical and physical topology
assessment, it has its needs assessment met, all the programs are up and running and the manager
has everything running like clockwork, what is it going to take to keep this network running
smoothly? Will it take just looking at a few screens, or just keeping a screw driver in your back
pocket for emergencies? Maybe the system will just run until it’s time to upgrade again. Then
IT personnel can come back in form home and do the process all over again. That would be a
nice thought but managing a network is a lot more than just kicking back, looking at a screen and
waiting for it to collapse so the manager can rebuild it again. Managers are continuously doing
many things to ensure progression of efficiency within their network systems. Upgrades,
software, hardware, media and security are your daily objectives and certain tools and task need
to be accomplished in order to make sure all this happens. Base lines need to be conducted of
all the hardware and software also needs to back itself up to ensure layer efficiency. Disaster
recovery also needs to be addressed as you might have one of these sometime in your career as a
manager. What steps will you take to make an effective, expedient recovery of the system?
There are many steps to conducting one of these recoveries. In the following paragraphs I will
delve into the aspects of what the IT manager does and what he/she needs to make it all happen.
It’s just not sitting around drinking coffee and donuts.

IT Manager Tools 6.2
When an employee steps into an IT manager position it feels like you’re grabbing a hold
of a running elephant. However, if you are that manager, there are a few things that should
always be within your reach for the daily grind. Tools of your trade should include an avid
supply of software and a few small essential items for checking lines, placing end caps on wires,
and ohm meters and a couples screw drivers. This is most usually used when you are in your
office but a little doctor bag doesn’t hurt when stepping out to work on someone’s computer. I
usually carry a couple universal serial bus (USB) drives with me when I go on a call. For some
reason people think I should have a tool chest like a plumber, but then I show them my needed
USB drive and the responses can be funny. Most of the time you won’t need any hardware
brought along as the component will be taken to the IT lab if its inner components are messed up
past a little configuration or two. When dealing with the network the tools become a little more
as cables may go down, a protocol may malfunction, or a piece of script may get a halt command
and become stuck in loop. This is where toners testers, cable testers and hardware loopback
devices come in handy. If the manager has “Spice Works”, Wire Shark, “Secuna Update”, and
“BitCricket” for starters they can easily tracks response times, component responses, and even
watch for malware potentials. Other software tools include hard drive and memory diagnostics
applications to quickly examine internal computer faults. The best tool of all when dealing with
any type of problem is the brain. There is nothing like knowledge, experience and a love for the
profession to get the manager through any better.

Base Lining 6.3
Once you have gotten those needed tools, the next task for your network is to set up a
baseline performance of the whole system. There are built-in tools within windows to complete
this process as well as hardware applications that can reasonably give the same responses to your
data gathering. These are used to get a baseline for your servers, media components, application
throughput, network utilization and other assorted values. Whatever the tools might be, it is
necessary to ensure this step for your network. If this is not conducted, you may have someone
stepping in saying something is not running correctly and you won’t have a jump point to start
from. Get your data and baseline. Once the baseline is set for the network, I look at needs to be
done to ensure system assurance and reliability. This prepares the manager for backup
compliance.
Back IT UP! 6.4
The necessity of backing up documents, video, photos, music, and an array of other events is
paramount. I don’t have enough toes, fingers and limbs to count the number of users, who have
lost data due to the negligence on their parts, to save that precious data some place safe. There
are multiple ways to ensure that all-to-precious data maintains integrity and reliability. In the
simple sense I have explained to users that an external backup device is preferable to placing
data on the operating system (OS) portion of a hard drive. Major response is “Deer in the
headlights look”. This is usually the response I often get and so it is my responsibility to “edu-
ma-cate” the poor “deer” user of the potential pitfalls of the OS sector saving habits. It starts by
telling them about the external drive being purchased and utilized due to what has just occurred
with the hard drive on the personal computer. It has crashed. There also runs the potential of

data being stolen right off their computer if they don’t have proper security applications and
saving habits in place. That’s received with another “deer-in the-headlights” look with the
question attached (“Security?”, “What security”?). That’s another portion but we are on backups
for the moment. I tell them the rest of the pitfalls and we get them set up with externals for data
saving and recovery. Users are also amazed that a whole mirror image of their system can be
placed on the external in case their operating system (OS) decides to take a dive in the future.
Likewise, this little experience in home repair and backup also applies to the network at the
school. There are a total of 8 servers at the campus network. These servers are set in RAID
formation and are either striping a cross section of another drive or mirroring another drive
within the stack. They are also running in a virtual environment utilizing full complementation
of the whole drive system array. Makes for some interesting configurations but we know that it
is reliable and assured. The network manager does complete diagnostics of each independent
drive utilizing the check disk environment. It has to be done after hours to ensure non-
interference of daily operations in the school. The campus also backs up grades, student records,
and library inventories to the cloud base through Google Schools. This cloud has been set up
through Google to help establish databanks for schools without financial support in their
networks for backup capacity. It is another avenue for schools to consider if they should need
the support. The servers are not the only components being backed up. Since there are actual
computers attached at various workstations throughout the campus, they are backed up through
management software as well. It can be configured accordingly based on instructions posted
within the application to monitor a particular work station. If it is a dumb terminal, than there is
no backup needed due to the workstation having very limited saving abilities. I am often asked
why I need to back up all this data and images by customers and users. I explain to them that it

Mark Simon IT 245 Introduction to Network Management

Mark Simon IT 245 Introduction to Network Management

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Mark Simon IT 245 Introduction to Network Management

Similar to Mark Simon IT 245 Introduction to Network Management (20)

More from Mark Simon

More from Mark Simon (13)

Recently uploaded

Recently uploaded (20)

Mark Simon IT 245 Introduction to Network Management