Frame Relay
Video Activity
Frame Relay In this lesson we cover Frame Relay. Frame Relay is the third encapsulation type that is also non-broadcast multi-access technology. You'll learn why this is important to know, what it supports, what OSI model layers are not supported and why. You'll also observe from our diagram what a customer edge router is, how it connects to other ...
Join over 3 million cybersecurity professionals advancing their career
Sign up with
Required fields are marked with an *
or
Already have an account? Sign In »
Time
29 hours 18 minutes
Difficulty
Intermediate
Video Description
Frame Relay In this lesson we cover Frame Relay. Frame Relay is the third encapsulation type that is also non-broadcast multi-access technology. You'll learn why this is important to know, what it supports, what OSI model layers are not supported and why. You'll also observe from our diagram what a customer edge router is, how it connects to other switch resources, the function of the Provider Edge Router how they interact to become a Permanent Virtual Circuit (PVC) and what a Hub and Spoke topology's purpose it.
Video Transcription
00:04
the next topic of discussion
00:06
is your third wide area or serial encapsulation type or framed really.
00:12
Now frame really is a non broadcast, multi access technology.
00:17
Or
00:20
and
00:21
the
00:23
and a
00:26
so friend really is a non broadcast monthly access topology technology as opposed to Ethernet, which is a broadcast multi access technology.
00:37
Now multi Axis simply means that no more than two devices can be on the network at the same time.
00:43
Frame relay supports more than two devices being on the network at the same time, just like Internet.
00:49
However, unlike Internet, there is no layer to frame relay
00:54
destination
00:56
broadcast address. An Ethernet,
00:59
a destination broadcast address is all lefts
01:02
in frame. Really, there is no where you could send a broadcast from one device to all devices, using one address as the destination address in the frame
01:11
to explain frame. Really, I've drawn out this topology on the board.
01:15
You see the D C router on the left hand side,
01:21
connected to around a router that says F F stands for frame, really,
01:26
and the D C router is connected to the frame relay router.
01:30
The sea on top stands for Custom Reg. So this D. C. Router is your customer edge router. The rest of your network, your enterprise network lays behind the D C router, the be router
01:44
or the first frame relay switch, which actually is a router with special configurations. On it
01:51
is your first be router or the provider edge router,
01:55
the provider edge of self explanatory. It's the last router on the provider side that connects through the customer edge.
02:02
Then you have the friend really cloud, which is this collection of frame relay switches that the service provider has laid out throughout the world and doesn't done the groundwork already connected to each other in a full mash or an almost full mesh. On the other side, you have
02:21
the two provider edge routers, one connecting to your remote side in Paris
02:27
or the customer edge router in Paris and the other one connecting to the remote side in London or the customer edge in London.
02:34
Now, let's say, at the D. C end,
02:38
you wanted a circuit
02:39
to the Paris router,
02:43
and you had another branch for off your company in Paris.
02:46
You could
02:47
trying to lay your own line between D. C. And Paris and go broke in the process. Or you could call up a service for lighter and ask them
02:57
to lease out a circuit,
02:59
the cost of which you will pay per month
03:01
between the D. C and Paris site.
03:05
Now, once you call them, call your service for lighter. They might build you a circuit
03:14
between all these frame relay switches, which again are just routers with certain configurations on them
03:21
between the D. C
03:23
and the Paris router.
03:25
In frame relay terminology, this circuit between two remote sites is called a permanent virtual circuit
03:37
or a P V C.
03:39
Next, let's imagine that we have 1/3 sight come up in London. We have doing prosperously. So third side comes up in London and we need a circuit between D. C and London also.
03:51
So the service for lighter build us another circuit
03:55
between D. C. And London,
03:59
and this circuit again
04:00
is called a permanent
04:03
virtual circuit.
04:05
Now, if you look at this apology,
04:09
Paris and London don't have a direct connection between each other. So all traffic between London and Paris must pass through the D. C end.
04:18
This kind of apology is called ah Hub and spoke topology
04:24
Instead of paying for an extra circuit between London and Paris
04:28
and paying a monthly fee for it,
04:30
this company decided that they were gonna pass traffic between London and Paris through D. C.
04:36
This type of a set up is called a hub and spoke topology, the D C and being the hub and the Paris and London end and being the spokes.
04:47
Now, if you see the d C end is terminating two circuits, one circuit, one part permanent virtual circuit is going to Paris on the other permanent virtual circuit is going to London.
05:00
So the engineer sitting at the D. C router how does he separate the circuit going to Paris from the circuit going to London.
05:09
That is done.
05:11
Bye.
05:12
You're
05:13
data link connection. Identify or I D
05:18
or your DLC.
05:20
Now, when you call up your service for lighter, your service provider will let you know. For example, the Del C 100
05:30
is going to Paris and L C 200
05:33
is going to London. You can think off a DLC
05:38
as
05:39
your Mac address for
05:43
frame relay,
05:45
so Mac addresses are two Ethernet. What Adele see is to frame really del sea is basically your lair to address for frame, really to identify
05:57
or two separate PVCs from each other.
06:00
So in this scenario, if I take the circuit
06:02
with the DLC number 100 I end up in Paris from D. C.
06:08
And if I take the circuit, or you could think of it as a train 200
06:13
from D. C. I end up in London. Now these del seas are locally significant, which means these Del sees
06:21
have these values of 102 100 just between the customer and A D. C. And the first provider
06:30
router, which is your P.
06:33
So, for example, going to Paris. The DLC is 100 between the D. C
06:40
and the first frame relay a router
06:42
or the sea and the P E ej.
06:45
After that, it might change through 1 50
06:49
301
06:50
five or two
06:54
5 13 etcetera, etcetera. So the DLC or the PVC, the circuit coming back from Paris to D. C will not have the same identify, will not have the same data link connection I d.
07:09
That
07:10
could very well be
07:14
600.
07:15
So the DLC coming back from London to D. C. will not be 200. It will be another number. Let's make it 2 22 when I go change my encapsulation type on my customer edge router or the D C router. Let's suppose this interference is cereal zero
07:34
00
07:36
and instead of p p p r S t l c I changed encapsulation type to frame. Really? The d C router start sending and receiving what are called lm eyes or local management interface.
07:50
So you're l am I the word l am. I stands for local
07:58
management interface Alum Eyes are used for two purposes
08:03
The first purposes when she changed encapsulation too
08:07
Frame really on your edge on your customer edge and you start receiving Elem eyes from the provider EJ The alum eyes announced all your del sees to you.
08:18
Now the Alum eyes will just announce all you'd Elsie's to you. You still will have to call the service provider to find out which Del Sea is taking you. To what location? The second purpose of the L. A. My is to report the end
08:33
to end circuit health.
08:35
So if if at any time, anywhere in the middle of the circuit fails
08:41
you will find out that the PVC is down
08:46
or the DLC is inactive.
08:48
True, The reception off Ella Mayes.
08:52
Now Alum eyes by default are sent every 10 seconds between the provider edge and the customer edge. So the customer had sends and receives atomized every 10 seconds. Now that we have changed encapsulation to frame really And we have learned all our del sees from the provider edge.
09:11
And now we're sending and receiving Elem eyes.
09:15
If you assign an i p address to this serial 000 interface, lets
09:20
pretend that we're going to assign 1 51 01 45.1 to this side
09:28
and the other side is already configured as 1 51 a 1 45.2 We can make this slash
09:37
24
09:39
for all we care for now, just for this example.
09:43
Now, as soon as we
09:46
set an I P address on the serial 000 interface
09:50
and in worse, our request is sent down the circuit
09:56
sent down the PVC
09:58
to retrieve
10:00
or resolve the I P address
10:03
off the other end of the circuit.
10:05
Now it is called inverse are because let's look at art.
10:11
What does our BDU
10:13
and our resolve remote I p or the destination I p or the I p at the other end of the link
10:20
two
10:20
The Mac address also associated with that I p, which is also at the other end of the link.
10:26
An inverse are resolves. Ah, locally received Elsie because remember, Del C 100 is being received by the D. C end sent from the frame relay network by the provider and so locally received Elsie
10:43
to the remote I p at the other end.
10:46
In fact, basically, I'm saying
10:50
if I bind LC 100
10:52
to the remote I p, which is 1 51 01 45 got to
10:58
I am basically saying if I take the LC 100 or go down del C 100 I can get to the I p 1 51 01 45 2 which is
11:09
the other site in Paris.
11:13
So once again, one shoe
11:16
Ah, sign an i p address to an interface
11:20
an inverse our request to send down
11:22
to resolved i p address at the other end.
11:26
So this is ah, layer to layer three mapping just like art does,
11:31
except it's called inverse are because in this case you are mapping
11:35
a locally received Elsie toe, a remote I P and Self a remote I p to its remote Mac.
11:43
There are two types of frame really interfaces,
11:46
multi point frame relay and point to point framed. Really.
11:50
Main interface is like as 000
11:54
are always multi point interfaces
11:58
and multi point interfaces always sent out in verse. Our requests, unless inverse artist turned off
12:05
so multi point into fish is always sent out in verse on requests
12:09
by default, unless you turn off in verse are
12:13
the other type of infer interfaces for him really can have our your sub interfaces.
12:18
Now you can have a multi point someone defaced or a point to point sub interface.
12:24
Some interfaces do not send out inverse our request By default, you will have to do something manually to make it work,
12:33
and we will see that happen in our lab.
12:35
At this point, we're done with the frame relay lecture, so let's hop onto our lab and see how this works
Up Next
Instructed By
Similar Content
