Cisco Certified Network Associate - Day 2.

This is Imran Rafai, your trainer for this

0:06
entire series. Welcome back everybody for the second day in our training series, as
0:09
you already know this is a FREE training on YouTube for all the people who are interested
0:19
to start a career in networking. In our last video we learnt about Network Fundamentals.
0:25
Today we would be dealing with the OSI Model and the TCP/IP Model. When I say TCP/IP Models
0:34
or OSI Model, it is nothing but a set of rules... its a set of standards. Now you might ask
0:43
why we need a set of rules or set of standards in the computer industry! To understand that
0:50
we need to learn a little about the history of the computer industry. Not long ago, there
0:56
was a fierce battle between IBM and Digital Equipment Corporation (DEC) for being the
1:02
leading computer manufacturer. But there was a problem. Both these manufacturers manufactured
1:08
devices which were not compatible with each other. So if you bought a computer from IBM
1:14
you had to buy a monitor, printer and every thing from IBM. Similarly if you bought a
1:21
device from DEC then you had to buy all the accessories and other devices from DEC so
1:31
that you could actually use it. There were many companies which bought equipments from
1:35
both equipment manufacturers such that the accounts department had IBM computers and
1:41
devices and the marketing department had Digital Equipment Corporation computer. But the problem
1:47
is they could not communicate with each other or they could not even share information with
1:51
each other. Now that was not the right way forward. That was about the time when international
1:57
organization for standards or more commonly known as ISO thought that there was a need
2:03
for a standard. ISO developed OSI which was an acronym for Open System Interconnect which
2:12
is more commonly known as OSI reference model. At about the same time, a competing standard

2:19
known as the TCP/IP model which was promoted by the department of defence came into being.
2:26
The TCP/IP model is more like a stripped down version of the OSI Model and because it was
2:32
more relevant it went onto become the industry standard. To understand little bit more about
2:39
the models, we need to understand about layers approaches. To understand that let us talk
2:45
about this office that is on the screen. Every office has different employees and employee
2:51
levels. So you might have a CEO, you might have a Senior office staff, you might have
2:56
payroll manager, an account manager, maintenance manager, you have maintenance staff, you have
3:01
junior office staff, and you have different staffs. The reason every companies have different
3:06
employees with different designations, is because all those people have different roles
3:11
and responsibilities. So when you know that something is not done, or some task is not
3:18
accomplished, you know who is responsible. For instance if salary is not credited on
3:25
time, you know the responsibility has to be with the payroll manager, whether the bank
3:30
is involved or not... that is secondary, but the payroll is your first point of contact.
3:35
You will need to go and speak to the payroll manager. If you come to the office one fine
3:38
day and you see that your office is really dirty, it is not cleaned, you know the janitor
3:43
is responsible or the maintenance department is responsible. So you know where the responsibility
3:48
lies. Similarly we learn about the OSI Model and the TCP/IP model because in learning about
3:57
the computer network or tomorrow when we are trouble shooting computer networks, we need
4:01
to know what works at what layer. So if something isn't working, instead of troubleshooting
4:08
all the eqipments, we know exactly where the problem is! That is why we have a layer approach.
4:15

Alright, knowing what we know now, lets get into the Models! Lets understand how models
4:24
work, what are the layers involved and lets compare TCP/IP and the OSI Model. What you
4:33
see on the left is the OSI Model. What you see on the right is the TCP/IP model. Let
4:39
me take a highlighter so that I can highlight as I talk! Alright, for the moment, dont worry
4:45
about the colors. I have color coded it to compare between the OSI Model and the TCP/IP
4:51
Model. So lets start discussing from the left, from OSI Model. Before we go any further,
4:57
I need to stress on this point that as a student of networking, all of you should know the
5:04
layers by-heart! So when I say that, you need to know exactly the sequences of the layers.
5:11
You need to know the layer 7 is the Application Layer, Layer 6 is Presentation Layer, Layer
5:16
5 is Sessions layer. You need to know where the layers are! One way of remembering the
5:21
sequences of the layers is by having MNEMONICS. One of the most popular mnemonics to remember
5:28
the OSI model is the one given here. So if you remember, "Please Do Not Throw Sausage
5:36
Pizza Away", you can remember the first letter of the layers from bottom up! So "Please Do
5:45
Not Throw Sausage Pizza Away" is PDNTSPA! Similarly some people like to remember it
5:55
from top to bottom, which is perfectly fine. So if you want to remember it from top to
6:00
bottom, then you have another MNEMONICS, which says "All People Seem To Need Data Processing".
6:05
Well it is upto you. You can do it the way you like it, as long as you remember that
6:11
physical layer is layer 1 and application layer is layer 7. Some people get confused
6:17
when they remember it from top to bottom, that Application is layer 1.... NO.... Application
6:23
is layer 7 and Physical is layer 1! Alright and if you wan to remember TCPIP model, then
6:31
you could remember by just remembering this MNEMONICS, which is "TCP/IP comes in a TIN".

6:37
Well it does not mean anything, but you can just remember - ATIN .... that is Application
6:43
Transport Internet and Network Interface! Like I said, if you have a better way of remembering,
6:50
please use it.... as long as you remember the sequence of these layers, it should be
6:55
perfectly fine! Alrght, lets start with the Application layer. Application layer is the
7:04
point of contact for all Network Aware applications. Let me repeat that, it is a point of contact
7:12
for all Network Aware Applications. A lot of authors, I have heard them say/write that
7:22
all applications on your computer resides on this application layer, which is not true.
7:30
Application layer ..... firstly deals with only application that is network aware and
7:36
secondly all the application on your computer has nothing do with the application layer,
7:40
if they do not communicate on the network! To understand that a little bit more, let
7:47
us assume that you have uninstalled all the drivers from your PC, your wireless interface
7:55
card, your ethernet interface card and all network interface cards, you uninstall. Uninstall
8:02
the driver or physically remove if you can. Now if you fire up microsoft word for instance,
8:09
microsoft word will not communicate with the application layer or for that matter it will
8:14
not communicate with any of these layers. That is because microsoft cannot access your
8:21
network because because your Operating system does not even have a network interface card!
8:28
Similarly, on a normal system, if you fire up your web browser, maybe chrome, internet
8:35
explorer, safari, any of the webbrowsers and if you type www.cnn.com, that web browser
8:44
creates an http request and it communicates with your application layer. The application
8:49
layer gives that data to the presentation layer. The presentation layer does what it
8:53

has to do, gives it to the sessions layer. Sessions layer does the same thing and it
8:57
gives to transport and it keeps passing it to the next layer until it reaches the physical
9:02
layer! So this is how it works! So if an application communicates with the networks, that is the
9:09
only time the application layer is invoked! Some of the protocols that work at this layer
9:16
are FTP, TFTP, SNMP, DNS, HTTP and there are quite a few. So you can just do a GOOGLE...
9:25
you will get the entire list of all the protocols that work at this layer! Next we will deal
9:31
with the presentation layer. The presentation layer is the layer which GENERIFIES data.
9:38
When I say GENERIFIES data, it is the layer which takes the data coming out of sessions
9:44
layer on the way back, converts it into presentable form and gives it to the application layer.
9:50
So if you have raw data coming from sessions layer, to the presentation layer, this is
9:54
where data is converted. So if it is an image, it creates an image. If its a word document,
10:00
it creates a word document. So presentation layer is where all data conversion happens.
10:05
Also all encryption services like TLS, SSL all that are taken care of at this layer!
10:14
Next we have the sessions layer. Sessions layer is the layer which creates and maintains
10:20
session. When I say that, lets assume your computer has two applications. You have yout
10:26
telnet program and you have your web browsing application, maybe internet explorer! Now
10:34
both of these applications are accessing the network. So this layer is the layer that create
10:40
2 different sessions and maintains them! So when your web browser session is terminated,
10:47
your telnet session will also not get termnated because they are separate sessions! So it
10:51
maintains different sessions! Now I have color coded the top three layers in blue, and the
10:57
reason I have done that is because as a network engineer, and especially as a Cisco Network

11:04
Engineer, there is very little that we need to deal with layer 5,6,7. That is because
11:09
most of the cisco devices will not look beyond layer 4. So layer 1, 2, 3 &4 are very critical
11:17
for Cisco Engineer. But 5,6,7 are not so critical. You just need to know how it works and you
11:26
know as a rough idea, you know what it does, that should be perfectly fine because layer
11:31
5,6,7 are taken care of by the operating system. But layer 4,3,2,1 is where as a network engineer,
11:42
you have to know exactly how they work! Next we learn about the transport layer. Transport
11:50
layer is also one of the critical layers for a network engineer. When the information coming
11:56
from the upper layers comes to the transport layers, transport layer breaks them into manageable
12:03
segments. Each segment, the transport layer adds its own header to create encapsulation.
12:10
Two critical decisions the transport layer takes is:1) Whether to use Reliable Communication
12:16
or Unreliable Communication. 2) Create Port Numbers. When applications need a reliable
12:24
communication, they use TCP which is nothing but an acronym for Transmission Control Protocol.
12:32
If it wants an unreliable communication, it uses UDP, which is an acronym for User Datagram
12:40
Protocol. When I say 'Reliable', it doesnt mean it is better than 'Unreliable' in that,
12:47
the only difference is that the reliable communication has to get an acknowledgement for every packet
12:55
that is sent! In unreliable, there is not acknowledgement that is received for every
13:03
segment transmission. So unreliable is actually faster because of the less overhead. So if
13:12
it is realtime applications, they will use UDP, because it is faster and it is realtime.
13:22
So most of the time, if you have tried watching an online transmission or a live feed, there
13:29
are times when we see those green pixels on the screen. This is nothing but the information
13:37

for that pixel has not been received and the receiving device has no way of telling the
13:43
sending device that it did not receive that pixel. Similarly another function that is
13:52
taken care of by the transport layer is to create port numbers. Port number is a number
13:59
that is attached with the IP Address, to identify which application this information is coming
14:07
from. The transport layer, 1)Creates a random port source port number and attaches the port
14:17
number for the destination. So if your traffic is going to a webserver, the webserver has
14:24
a standard port number of 80! So if you are going to an IP Address of 10.10.10.10 for
14:31
instance as an example, it takes 10.10.10.10 and adds a port number for 80. So it creates
14:41
a socket.... socket is nothing but an ip address and port number. It creates a socket and send
14:47
down to the network layer. It also adds a source port number. Why does it require source
14:53
port number? The reason it creates a source port number is because if there are 2 applications
14:59
running on your computer and it is going to the same IP address, when the reply comes
15:06
ack the transport layer needs to know which data goes to which application. And it will
15:11
identify that by actually having our source port number. Next we will learn about the
15:19
Network Layer. When the network layer gets a segment from the transport layer, it adds
15:24
a network layer header. When a network layer header is added, that information is called
15:30
as a Packet! So one of the critcal functions of the Network Layer is of IP Address or also
15:37
known as Logical Addressing. We will learn about IP addressing in the next video, DAY3.
15:44
But just know that this is where the IPAddress is added. It also finds the best path. So
15:50
when I say best path, it compares the IPaddresses and it checks if the destination ip address
15:56
is in the local subnet. If it is not on the local subnet, it will find the best path to

16:02
the destination. Next we have the DataLink Layer. When the packet comes from the Network
16:13
layer to the data link layer,the data link layer will add data link header to it. And
16:19
that information is called a FRAME. The data link layer is responsible for MAC ADDRESSING.
16:28
MAC is nothing but an acronym for Media Access Control, and MAC address is a hardware address.
16:36
That means every network interface card of your computer, has its own MAC address. MAC
16:43
Address is also known as Burn-In-Address and its a address that cannot be changed. Yes
16:51
there are ways of spoofing the address, but it cannot be changed physically. This is a
16:58
layer where Error Checking happens. So when information coming from the physical layer
17:03
to the data link layer, the data link layer has the ability to check if there were error
17:11
that were induced during transmission. So it could use Cyclic Redundancy Check (CRC)
17:18
or it could use Parity Check or any other error checking mechanism that Data Link Layer
17:23
uses to check for errors. Next is the physical layer and physical layer is where the actually
17:31
data transfer happen. This is the layer that deals with wires, cables and hardware ports/connectors
17:40
and all similar things that happen at this layer. As a computer engineer or as a network
17:46
engineer, when somebody tells you that the internet doesnt work, as an engineer you will
17:52
start working or troubleshooting from Physical Layer. First you will check the cables to
17:57
see if it works. If the cables are fine, next you will check for Layer 2 problem. Then you
18:03
will go to Layer 3, Layer 4.... so you will trouble shoot by layers and that is why we
18:09
have to learn about the models. Also any change in one of the layers will not affect the adjacent
18:18
layers as long as the standard is followed. So if a physical layer, instead of the ethernet
18:24

cable I choose to use Wireless. It should not matter because the change is happening
18:29
on the physical layer only. So datalink layer, as long as it gets the information the way
18:34
it is expecting to get, it does not matter how physical layer gets those information.
18:40
Similarly the Network Layer - We are in the midst of transition phase of going from IPv4
18:48
to IPv6, so that change is only to layer 3. Layer 4 and Layer 2 will not be affected as
18:55
long as the standard is followed and it is receiving the data as it was receiving earlier.
19:04
So that is the beauty of the layered approach. Now if you compare the left and the right
19:10
we can see that the layer 5,6,7 is comparable to Layer 4 in the TCP/IP model. Transport
19:19
Layer and Transport Layer in TCP/IP, they have comparable functions. Similarly the Network
19:27
Layer and the Internet Layer. The layer 1 and layer 2 of OSI Model is comparable to
19:33
Layer 1 of the TCP/IP model. Next we will just see the OSI Model working. Let us assume
19:42
that the guy on the left wants to send some to the guy on the right. So he creates a data.
19:47
Like we mentioned the top 3 layers are generally known as the upper layers and upper layer
19:54
we really do not deal much. So lets assume the data goes to the transport layer. What
20:00
the transport layer does is, it takes the data, it segments it and adds its own header.
20:09
So if you see, you have a transport header here. Next lets assume we are dealing with
20:17
UDP here, so it does not wait for acknowledgements. It will send segment 1 to the network layer.
20:26
The network layer as we know will add a network header to the segment and it becomes a packet
20:31
now. Network layer will give the segment 1 or the packet to the datalink layer. The data
20:41
link layer takes that and adds a Data Link header. And if you can see the segment 2 also
20:47
goes through the same process. Next the segment 1 goes to the physical link layer and the

20:53
physical link layer as we know will convert it into 0s and 1s. So our segment 1 got converted.
21:00
Next segment 2 also will get converted. By that time the physical layer of the destination
21:06
device would have taken those physical bits and converted it into segment with the appropriate
21:18
headers. What the receiving layers will do is, it will strip the headers of the corresponding
21:25
layers from the source. So the data link layer will strip the datalink header and give that
21:30
information to the network layer. So if you see there was a datalink header to segment
21:35
1 which the data link layer stripped, and gave that information to network layer. Similarly
21:41
it will happen to Segment 2 as well. So for segment 1 when it goes to transport layer,
21:46
this network header will get removed. So if you see there, the network header got removed
21:54
and it reached the transport layer. Next the transport layer will wait until it gets all
22:01
the segment. That is what the transport layer will do. So transport layer waits until segment
22:07
2 comes there. Now transport layer will strip all the transport layer headers and combine
22:13
that information and give it to the upper layers. So the transport layer combines it
22:23
and the receiving guy receives the same data. And this is how a very basic representation
22:29
of how a data network works. I think thats about all the information that we had to learn
22:38
in this day 2 video. Please go through this entire cloud map and I am sure you understand
22:45
all the topics here. But if you do not, please feel free to write into me at 'imran.rafai@nwking.org'.
22:56
Please dont forget to share our videos, like our videos, and please subscribe to our YouTube
23:05
channel. You love and your respect is what motivates us to create free contents. Thank
23:11
you so much.